F5F Stay Refreshed Power Users Networks Issue with LAN not connected to internet Network problems preventing internet access.

Issue with LAN not connected to internet Network problems preventing internet access.

Issue with LAN not connected to internet Network problems preventing internet access.

K
Kamikaze_007
Senior Member
Find
625
08-23-2016, 09:24 AM
#1
Hello, I'm trying to understand how my server works with two network interfaces. I've installed VMware Workstation 14 on a VM running PFSense. The network adapter connected to the bridge network uses the physical card em0 with IP 192.168.1.44/24, while em1 is on the LAN with IP 10.0.0.1/8 and DHCP range 10.0.0.2 to 10.0.0.240. I have a router at 192.168.1.44 connected to PFSense via a bridge interface. On the server, the second network card is eth0 at 10.0.0.2 and eth1 doesn't assign any IP address but appears active when I connect a LAN port to the PC. When I connect the LAN cable to the server's LAN port and connect the PC, I can't access the internet and the PC receives an IP like 169.48.72/x. After reconnecting the cable to the modem, internet access returns and the PC gets its DHCP address from the LAN on PFSense (e.g., 10.0.0.10). All hosts branch through the router, changing their IPs accordingly. I've tested blocking the PC from accessing the internet using firewall rules, but it seems to work. I'm confused because normally I get the same IP when connecting via LAN directly on the server. I hope someone can clarify this and help me understand how PFSense functions through the router.
Reply
Reply
K
Kamikaze_007
08-23-2016, 09:24 AM #1

Hello, I'm trying to understand how my server works with two network interfaces. I've installed VMware Workstation 14 on a VM running PFSense. The network adapter connected to the bridge network uses the physical card em0 with IP 192.168.1.44/24, while em1 is on the LAN with IP 10.0.0.1/8 and DHCP range 10.0.0.2 to 10.0.0.240. I have a router at 192.168.1.44 connected to PFSense via a bridge interface. On the server, the second network card is eth0 at 10.0.0.2 and eth1 doesn't assign any IP address but appears active when I connect a LAN port to the PC. When I connect the LAN cable to the server's LAN port and connect the PC, I can't access the internet and the PC receives an IP like 169.48.72/x. After reconnecting the cable to the modem, internet access returns and the PC gets its DHCP address from the LAN on PFSense (e.g., 10.0.0.10). All hosts branch through the router, changing their IPs accordingly. I've tested blocking the PC from accessing the internet using firewall rules, but it seems to work. I'm confused because normally I get the same IP when connecting via LAN directly on the server. I hope someone can clarify this and help me understand how PFSense functions through the router.

Reply
Reply
C
coolness2001
Member
Find
224
08-23-2016, 11:14 AM
#2
You must route hosts through NAT on pfSense or configure a route for 10/8 using the 192.168 interface as the next hop. Otherwise, your router won’t know how to reach those IP addresses. A DHCP server on the 10.0.0.0/8 network is also necessary for automatic addressing. The current DHCP range only covers 192.168.1.x and doesn’t extend beyond the routed layer 3 through pfSense.
Reply
Reply
C
coolness2001
08-23-2016, 11:14 AM #2

You must route hosts through NAT on pfSense or configure a route for 10/8 using the 192.168 interface as the next hop. Otherwise, your router won’t know how to reach those IP addresses. A DHCP server on the 10.0.0.0/8 network is also necessary for automatic addressing. The current DHCP range only covers 192.168.1.x and doesn’t extend beyond the routed layer 3 through pfSense.

Reply
Reply