Routing between Interfaces
-
"DMZ server can ping 192.168.13.1 (its gateway) but it cannot ping 192.168.1.1 (LAN Gateway)"
Well that makes no sense unless its not pointing to 192.168.13.1 as its gateway, or its mask on its own IP 192.168.13.? is wrong.
Can you post the clients network config. You say for example that lan can ping dmz pfsense IP. This is good, but can not ping something say 192.168.13.42 – couple things that come to mind here, the dmz client does not have its gateway set to point to pfsense, or its mask is wrong. Or it has a firewall preventing ping.
The fact that you have a dmz rules as any any and can not ping the lan pfsense IP, I have to think the clients gateway is not set to point to pfsense, or mask is off.
Your rules are correct.. Other thing that comes to mind is if your saying you did not create that outbound nat rule where you were natting traffic from dmz to lan to the wan IP? It was there from automatic settings, when you turned on manual. That is a problem!! And would cause your issues.
So I see your outbound nat rules are clean and on automatic - if you switch to manual you see the dmz to lan rule??
edit:
See here on my outbound nat rules (switch to manual so you could see them) - they only have source of my lan,wlan and dmz segments, and my openvpn segments - and they all say auto created. While yours below that -- doesn't have comment - so looks to me like you manually created that rule?? That rule would be BAD!Also just to be sure - you don't have any rules in your floating tab?
Also bottom pic is ipconfig from a 192.168.1.0/24 box - and traceroute to IP on my 192.168.2.0/24 segment.. Can we see this from your dmz segment client.
-
No windows firewall enabled on any server, windows firewall is turned off. No other firewalls installed.
DMZ Server
LAN Server
Nat Set to Manual
-
Ok that rule is gone now! I showed a picture of your outbound rules showing that rule I was talking about 1st rule on the list.
This second posting of your nat outbound looks fine. So when you try and ping pfsense lan IP 192.168.1.1 from your dmz machine what does the firewall log in pfsense say? If anything if it blocked it it would be logged, unless you turned that off? By default anything blocked by default block rules are logged.
And your floating tab shows what? Have you rebooted pfsense after all the cleanup, reseting, etc.
There should be no reason why you can not ping the pfsense lan IP from dmz box, if your pointing that traffic to pfsense from the rules you have shown. If pfsense was blocking it - it should be logged.
And unless you have some specific routes on your dmz client that looks fine. Tracert would validate your talking to pfsense to get to the lan from the dmz. And post up your pfsense routes
Here is mine for example
-
Nothing is set in floating.
I turned on logging and saw this. Not sure how to explain this or investigate this
LAN Server
DMZ Server
Nothing shows in the log when I did the ping on the DMZ Server
Routing Tables
-
So what does the traceroute from dmz to 192.168.1.1 look like?
Can you post that dmz box routes.. So example see attached.
So clearly pfsense is sending on the packets to your dmz box 13.10, that your not seeing and answer points to your dmz box having the problem. But very odd that it can ping pfsense IP 192.168.13.1
Are you SURE the IP address for 192.168.13.1 is your pfsense mac?? Maybe you have something else on your 13 network that has IP of pfsense dmz IP?
Or you have a weird routing issue and traffic is not being sent to 13.1 for 192.168.1.0/24 networks… Does this dmz box get internet or access to wan network 10.x.x.x
You can view your mac table with arp -a
So for example you can see below my client on my lan network see my pfsense lan IP mac, and that matches up with my pfsense actual mac.. I would validate this on your dmz client.
edit: and from looking at mine, I have to do something with my dvr, they keep showing up with apipa addresses those 168.254 -- even though they are clearly on my network with the 192.168.1.97 and .98 addresses - notice the same macs.. Odd..
-
Well it seems to have been the DMZ server. I should of known to at least do a route -f to flush the routes to just remove that from being an issue. Once I did a route -f everything started to work. Thanks for helping me along the way. Much appreciated. I will probably be back with more questions as I start to set this up to mimic a real network.
-
So you had a static route setup? Happy to help - and glad you got it sorted.
-
No, I expect it had to be that it was a template that got deployed and it had some old routing information in there from when it was a vm before a template.
I might not be 100% done yet though, as I can now ping everything from DMZ, but I cannot get out to the internet. I added DNS and I can ping google.com, but when I open up IE and try to go to google.com, it just sits and spins. Tracert from the VM gives me this
-
Well that is odd as shit.. according to that output google.com is 74.125.225.73.. And you hit it on your 2nd hop?? But you continue on?
What does a trace look like from box in the lan segment? There is no difference to pfsense between lan and dmz other than what you might put on the firewall rules.. They are just 2 segments to pfsense that are not WAN connections that is all. So what does lan client traceroute look like?
-
Client DNS IP should point to the gateway address as well, this in turn pfsense will have dns forwarders to resolve the FQDN.
Set auto outbound NAT and disable/remove all nat mappings, also remove static route entry. Make backups of the current config before trying.
I have similar setups set on auto nat, no nat mappings, no static routes, only WAN has gateway. On each LAN interface firewall rules are to allow all traffic generating from the LAN subnet to any destination, tcp and udp, any port.
