[resolved] pfSense not routing between connected subnets
Been at a problem I've had for quite some time, googled most any combination of words and reading topics.
My problem is simply, pfSense will not route between two connected subnets on LAN: 10.0.10.0/24 and DMZ: 192.168.1.0/24.
pfSense is 10.0.10.1 and 192.168.1.1 respectively. Running version 2.1.
Computers connected to each of these networks ofcourse have the correct default route to the pfsense box. Computers connected to LAN and DMZ can ping the pfSense firewall. Hosts are configured to reply to ICMP. They reply to pings made from the pfsense webGUI.
Computers in LAN can also ping the interface of the pfsense box facing the DMZ network(192.168.1.1). But not anything else in the DMZ network.
Computers in DMZ can also ping the interface of the pfsense box facing the LAN network (10.0.10.1). But not anything else in the LAN network.
I've tried Manual NAT mode, and deleted all rules in that pane, No go. I've tried ticking the "Disable all packet filtering" in System: Advanced: Firewall/NAT, no go.
I've tried different firewall rules for both DMZ and LAN. They're both now configured with Allow source: any, proto: any, dest: any.
I've tried switching NICs for LAN and DMZ, no go.
Both LAN and DMZ can successfully access the Internet with manual NAT Outbound config through the WAN interface. I can configure NAT between LAN and DMZ which works, but I do not want NAT between these networks.
Does anyone have any idea whats going on here?
If you need more info, I will supply it.
Is your WAN on a private IP or a public one? With firewall rules disabled, it should route without any problems.
My WAN is currently in a private adress space.. 10.0.0.0/24.
Yeah that is what I understood about pfSense too, but seems mine does not route, only NAT..
I've tried 2.0.2 and 2.0.3 versions too. Same problem.
I've tried different IP subnets, disconnecting WAN, fresh install but to no avail.
jswj last edited by
on pfsense, all LAN interface must not have gateway IP set. both clients host should point its gateway to its respective LAN IP of the pfsense LAN interface.
create firewall rules on both LAN interface on pfsense to allow any to any traffic, for now. see if client host on both LAN can reach each other.
pfsense WAN, disable blocked private networks, and enable auto outbound NAT.
would that work?
Neither LAN nor DMZ interface on pfSense is configured with a gateway. It is set to "none".
Hosts in DMZ:192.168.1.0/24 have 192.168.1.1 as default gateway. Hosts in LAN:10.0.10.0/24 have 10.0.10.1 as their default gateway.
Both LAN and DMZ have rules that say allow traffic from any to any. Clients can not reach each other.
WAN interface is ofcourse not configured with "block private networks", because the WAN adress space is in such a network.
I will try enabling Auto Outbound NAT later today.. Doubt it will work however, because it did not work with Manual NAT & no rules.
NAT/PATing works wonderful however. Hosts in both LAN and DMZ currently have internet access. They can not reach each other though.
I've successfully tried NATing with source LAN destination DMZ with a NAT rule as pictured in the attachment. Hosts on LAN:10.0.10.0/24 can that way access hosts in DMZ:192.168.1.0/24 but not the other way without manually mapping ports etc. This would probably be fine for a normal DMZ network but not in this case :)
jswj last edited by
Remove all the mappings on the manual NAT configurations. If both LAN and DMZ can ping to its own gateway, they should be able to talk to each other.
It is maybe stupid of me by saying this, but sometime the LAN cable is not where its suppose to be check LAN and DMZ are connected to the correct interface on t pfsense, just maybe.
I have simulate your situation within a virtual environment, all works ok.
I tried removing the NAT configurations. In this scenario both LAN and DMZ can ping to its own gateway, but they can not talk to each other.
Yeah I'm pretty sure about where the cables go. LAN and DMZ hosts rely on DHCP leases so that is another way to know for sure hosts are connected to the correct interface.
What other settings/rules have you configured to manage this in your virtual environment?
I'm starting to think the motherboard simply can not be used for routing.. Tried m0n0wall too, no luck there. Maybe I should start over with some other hardware.
Attached: firewall rules and NAT rules. This is the current setup. If I delete all NAT rules there is no internet access (of course), and hosts in LAN (10.0.10.0/24) can not access DMZ hosts (192.168.1.0/24) at all.
Do you have promiscuous mode turn on for the vswitches in ESX?
This is a physical pfsense box.. hosts are physical aswell :) no vswitches.
Sorry posted in wrong thread. Let me look over the attachment.
I have heard of this only one other time, and it was hardware related then. What type of NICs and hardware are you running?
Its running on a Jetway 7F4K1G5DS-LF motherboard, 1,5 Ghz VIA C7-D embedded processor, with two realtek gigabit NICs onboard with RTL8101SC chip. Third NIC is a generic 100/10 mbit davicom. Booting from 512MB CF-card in a CF-IDE converter.
mikeisfly last edited by
What network is your WAN on? can you post screen shots of your LAN interfaces?
I have not heard of this davicom nic. What chip set is it using? Do you have another NIC, preferably Intel, that you can replace it with for further testing?
My WAN network lies in 10.0.0.0/24. I have tried to replace the davicom PCI card with realtek PCI 100/10 NIC. Still no routing happening. LAN and DMZ is configured on the onboard NICs. I did try to use the third PCI for LAN, still no routing. Realtek 100/10 PCI card is using RL driver. Onboard Realtek NICs is using RE driver.
Attached screens from LAN and DMZ int config page.
With that setup and the correct rules, it should route without issue. Did you say that if you disable the firewall in advanced, it still will not route?
That is correct. It will not route between connected subnets even with firewall disabled.
I will try routing between nets on different vlans in a trunk from the pfsense box later today. If the NICs support vlan/trunking at all :)
The error of my ways has revealed it self. Windows firewall blocks both icmp and IP traffic from an other subnet than that the host resides in. All this time the poor pfSense box was doing its job probably perfectly.
Sorry for wasting your time people, but thanks a bunch for your posts :) really appreciate it.
Good old Windows … At least they are error on somewhat safe now. Good luck.
Hehe yeah. Both hosts were running Win 8 so maybe its something new. I have not heard of this atleast. I figured it out when I put a cisco switch in to the mix, which I could ping from all subnets.
Brutal last edited by
I've been caught by this in the past and now packet capture on each port to see exactly what's going on. Sure saves a lot of time.
madVaX last edited by
I have an almost identical setup with almost identical issues.
One pfSense box (PC Engines APU 1C4, three Realtek RTL8111E NICs), re0 is the WAN interface, connecting to a cable modem which connects to a public IP network of the Internet provider, re1 is the LAN interface connecting a bunch of machines in the 192.168.0.0/24 private subnet and re2 is the OPT1 interface connecting some machine in the 192.168.1.0/24 private subnet.
WAN has filter private and bogons enabled, those settings as well as the upstream route are off for both the LAN and OPT1 configured subnets.
Routing to the Internet works on both subnets, all hosts get their IP from DHCP on their respective interface.
There are any-to-any rules for both local subnetworks configured (OPT1 basically with the LAN rules as template, replacing the relevant interface names).
I have a NAT rule, which allows access from the internet on port 443 to one server on the ~0.0/24 network. I also had NAT reflection enabled ("NAT + proxy") for this NAT rule. The default behaviour is "Disable". This works.
I run Linux boxes, mostly Ubuntu and small SOHO Access Points (Sitecom) on both LANs, but as the original poster, I am unable to ping machines in the ~1.0/24 from the ~0.0/24 subnet and vice versa.
I tried pinging with Ubuntu UFW personal firewall disabled on the client towards the AP in the other subnet, and it does not work.
As with the OP, I can ping the other interface (~1.1/24 from ~0.1/24 and vice versa) but not the machines in the other subnet.
Adding a firewall rule to monitor traffic shows, that packet are passed. Packet capture shows, that nothing comes back if I send pings.
I simply don't understand this (must be a stupid oversight probably an issue with the machine config of the AP I used for testing so far).
If anyone could help here, I would be very gratefull.
madVaX last edited by
Reply to self:
Similar issue as the original poster. The Access Points I used as ping targets are configured not to reply to pings from other subnets. Packets where passed around with no problem by pfSense.
This is the main problem that I see as well. The access points don't allow the ping reply. Please test with something else, like s real computer.