내 서버에서 직접 라우팅하려고 합니다.
- pfSense 도메인에서 관리 및 DMZ 네트워크의 IP를 ping할 수 있습니다.
- 가상 호스트에서 동일한 IP로 핑을 보낼 수 있습니다.
- pfSense는 DMZ 및 관리를 위한 게이트웨이입니다. Centos에서 dmz 또는 관리 GW를 핑할 수 없습니다.
- LAN(외부)에서는 DMZ 및 관리 인터페이스에서 pfSense 게이트웨이를 ping할 수 있습니다.
- pfSense를 사용한 패킷 캡처는 트래픽이 올바른 인터페이스로 라우팅되는 것을 보여줍니다. 그러나 돌아 오는 트래픽이 없습니다.
- LAN에서 관리까지 무엇이든 허용되며 그 반대의 경우도 마찬가지입니다.
- 인터넷이 작동하므로 그게 문제입니다!
[root@workhorse1 docker-configs]# ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vb2 state UP group default qlen 1000
link/ether 00:21:9b:9d:75:07 brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vb1 state UP group default qlen 1000
link/ether 00:21:9b:9d:75:09 brd ff:ff:ff:ff:ff:ff
4: em3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:21:9b:9d:75:0b brd ff:ff:ff:ff:ff:ff
5: em4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:21:9b:9d:75:0d brd ff:ff:ff:ff:ff:ff
10: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:bf:c6:48 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
11: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:bf:c6:48 brd ff:ff:ff:ff:ff:ff
20: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 62:30:db:db:51:bd brd ff:ff:ff:ff:ff:ff
31: vb2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:21:9b:9d:75:07 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.16/24 brd 192.168.1.255 scope global noprefixroute vb2
valid_lft forever preferred_lft forever
inet6 fe80::221:9bff:fe9d:7507/64 scope link noprefixroute
valid_lft forever preferred_lft forever
32: vb1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:21:9b:9d:75:09 brd ff:ff:ff:ff:ff:ff
inet6 fe80::221:9bff:fe9d:7509/64 scope link
valid_lft forever preferred_lft forever
33: vb3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 12:af:3c:dd:a2:72 brd ff:ff:ff:ff:ff:ff
inet 172.16.0.2/24 scope global vb3
valid_lft forever preferred_lft forever
inet6 fe80::7082:e9ff:feed:8e8/64 scope link
valid_lft forever preferred_lft forever
34: vb4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether e2:a9:29:c1:18:6c brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global noprefixroute vb4
valid_lft forever preferred_lft forever
38: vnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vb1 state DOWN group default qlen 1000
link/ether 82:f0:9d:32:79:e4 brd ff:ff:ff:ff:ff:ff
40: vnet2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vb3 state DOWN group default qlen 1000
link/ether 12:af:3c:dd:a2:72 brd ff:ff:ff:ff:ff:ff
44: vnet4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vb1 state UNKNOWN group default qlen 1000
link/ether fe:54:00:f8:58:d1 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fef8:58d1/64 scope link
valid_lft forever preferred_lft forever
45: vnet5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vb2 state UNKNOWN group default qlen 1000
link/ether fe:54:00:16:6f:bc brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe16:6fbc/64 scope link
valid_lft forever preferred_lft forever
46: vnet6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vb3 state UNKNOWN group default qlen 1000
link/ether fe:54:00:de:07:95 brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fede:795/64 scope link
valid_lft forever preferred_lft forever
47: vnet7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vb4 state UNKNOWN group default qlen 1000
link/ether fe:54:00:7e:d9:ac brd ff:ff:ff:ff:ff:ff
inet6 fe80::fc54:ff:fe7e:d9ac/64 scope link
valid_lft forever preferred_lft forever
55: docker_gwbridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:a7:1a:7f:f4 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker_gwbridge
valid_lft forever preferred_lft forever
inet6 fe80::42:a7ff:fe1a:7ff4/64 scope link
valid_lft forever preferred_lft forever
63: vethce24fe8@if62: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker_gwbridge state UP group default
link/ether ca:f8:47:76:e5:95 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::c8f8:47ff:fe76:e595/64 scope link
valid_lft forever preferred_lft forever
65: br-a5bb2d7cbed8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:45:9d:7a:7f brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-a5bb2d7cbed8
valid_lft forever preferred_lft forever
351: vethd87b4f6@if350: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker_gwbridge state UP group default
link/ether 9e:0d:17:67:49:c2 brd ff:ff:ff:ff:ff:ff link-netnsid 4
inet6 fe80::9c0d:17ff:fe67:49c2/64 scope link
valid_lft forever preferred_lft forever
151: vnet3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vb4 state DOWN group default qlen 1000
link/ether e2:a9:29:c1:18:6c brd ff:ff:ff:ff:ff:ff
218: vnet1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vb2 state DOWN group default qlen 1000
link/ether b2:68:ec:7a:1a:8a brd ff:ff:ff:ff:ff:ff
[root@workhorse1 docker-configs]# brctl show
bridge name bridge id STP enabled interfaces
br-a5bb2d7cbed8 8000.0242459d7a7f no
docker_gwbridge 8000.0242a71a7ff4 no veth8f914aa
vethce24fe8
vb1 8000.00219b9d7509 yes em2
vnet0
vnet4
vb2 8000.00219b9d7507 yes em1
vnet1
vnet5
vb3 8000.12af3cdda272 yes vnet2
vnet6
vb4 8000.e2a929c1186c yes vnet3
vnet7
virbr0 8000.525400bfc648 yes virbr0-nic
<interface type='bridge'>
<mac address='52:54:00:f8:58:d1'/>
<source bridge='vb1'/>
<target dev='vnet4'/>
<model type='e1000'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<interface type='bridge'>
<mac address='52:54:00:16:6f:bc'/>
<source bridge='vb2'/>
<target dev='vnet5'/>
<model type='e1000'/>
<alias name='net1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</interface>
<interface type='bridge'>
<mac address='52:54:00:de:07:95'/>
<source bridge='vb3'/>
<target dev='vnet6'/>
<model type='e1000'/>
<alias name='net2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</interface>
<interface type='bridge'>
<mac address='52:54:00:7e:d9:ac'/>
<source bridge='vb4'/>
<target dev='vnet7'/>
<model type='e1000'/>
<alias name='net3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</interface>
[root@workhorse1 docker-configs]# ip route show
default via 192.168.1.100 dev vb2 proto static metric 431
10.0.0.0/24 dev vb4 scope link
172.16.0.0/24 dev vb3 scope link
172.17.0.0/16 dev docker_gwbridge proto kernel scope link src 172.17.0.1
172.19.0.0/16 dev br-a5bb2d7cbed8 proto kernel scope link src 172.19.0.1
192.168.1.0/24 dev vb2 proto kernel scope link src 192.168.1.16 metric 431
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
pfSense를 사용하여 LAN에서 관리 서브넷으로, 그리고 WAN에서 DMZ로 네트워크 연결을 얻으려면 어떻게 해야 합니까?
답변1
여러 인터페이스가 있고 각각 고유한 서브넷이 있는 컴퓨터에서는 각 인터페이스에 고유한 라우팅 테이블이 있어야 합니다. 이는 정책 기반 라우팅을 통해 수행됩니다.
- "NetworkManager-config-routing-rules" 설치 및 활성화
- defroute=yes로 설정해야 하는 인터페이스:
root@workhorse1]# more /etc/sysconfig/network-scripts/ifcfg-vb3
DEVICE=vb3
BOOTPROTO=static
ONBOOT=yes
TYPE=Bridge
STP=no
IPADDR=172.16.0.2
NETMASK=255.255.255.0
PREFIX=24
GATEWAY=172.16.0.1
PROXY_METHOD=none
BROWSER_ONLY=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME="Bridge vb3"
- /etc/iproute2/rt_tables에 새로운 라우팅 테이블을 추가했습니다.
[root@workhorse1]# more /etc/iproute2/rt_tables
#
# reserved values
#
255 local
254 main
253 default
0 unspec
#
# local
#
#1 inr.ruhep
1 lan
2 mgmt
3 dmz
- 기본 경로 추가:
[root@workhorse1]# more /etc/sysconfig/network-scripts/route-vb2
192.168.1.0/24 dev vb2 table lan
default via 192.168.1.100 dev vb2 table lan
[root@workhorse1]# more /etc/sysconfig/network-scripts/route-vb3
172.16.0.0/24 dev vb3 table mgmt
default via 172.16.0.1 dev vb3 table mgmt
[root@workhorse1]# more /etc/sysconfig/network-scripts/route-vb4
10.0.0.0/24 dev vb4 table dmz
default via 10.0.0.1 dev vb4 table dmz
- 라우팅 정책을 추가합니다.
[root@workhorse1]# more /etc/sysconfig/network-scripts/rule-vb2
from 192.168.1.0/24 lookup lan
[root@workhorse1]# more /etc/sysconfig/network-scripts/rule-vb3
from 172.16.0.0/24 lookup mgmt
[root@workhorse1]# more /etc/sysconfig/network-scripts/rule-vb4
from 10.0.0.2/24 lookup dmz
- 기술적으로는 필요하지 않지만 전체 서버를 다시 시작했습니다.
- 경로 확인:
[root@workhorse1 vm]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.100 0.0.0.0 UG 0 0 0 vb2
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 vb4
0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 vb3
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 vb4
172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 0 vb3
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker_gwbridge
172.19.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-a5bb2d7cbed8
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 vb2
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
**문제 해결: tcpdump 및 pfsense를 사용하여 패킷을 캡처하여 트래픽을 확인하세요.
**참고로 pfSense는 호스트에서 다양한 인터페이스로의 핑을 차단합니다. 그래서 이것은 내 실수였습니다.