Netgate SG-3100 LAN ports cannot go through LAN Gateway.
-
I also found a very strange thing that when I connect Win10 computer to WirelessNetwork port, it gets correct IP address and gateway
login-to-view
But it also can ping LAN 192.168.1.1
login-to-view
Even I have this rule in WirelessNetwork
login-to-view
Also when I tried to get route from 192.168.30.52 to 192.168.1.1 in Win10 computer
login-to-view
It seems like it access 192.168.1.1 directly not through it's gateway 192.168.30.1
Can anyone help to explain these weird phenomenon? Maybe by fixing this will fix the LAN ports can't reach LAN gateway problem. Thanks. -
Not necessarily.
192.168.1.1 is still only one hop away since that address exists on the same hop you reach at 192.168.30.1. It is free to respond to a traceroute using that address.
-
@Derelict Thank you very much for trace-route. But why can I ping 192.168.1.1 from WirelessNetwork. I think anything from WirelessNetwork net to LAN net should be blocked by default.
-
Well, if you want to BLOCK traffic on from Wireless network to LAN net then BLOCK it. Don't block traffic with a pass rule.
Add a rule above what you have that blocks traffic to destination LAN net above what you have and see if the behavior changes.
-
@Derelict Great, thank you. I created a BLOCK rule and it's working.
Now I am backing LAN ports can't reach LAN gateway problem. Looks like fixing problems with WirelessNetwork doesn't fix LAN net. -
@stephenw10 I connect one of the Win10 computer to LAN1 port and Switch setting is here:
It's getting correct IP address from LAN DHCP 192.168.1.115, but is't offline
login-to-viewI started Packet capture on LAN interface for IPv4 only.
login-to-view
Looks like LAN can receive from Win10 computer but never reply. -
Ok that is good info, now lets see your actual switch config.
-
@johnpoz Sorry I am new to pfSense. What is actual switch config and how to view it? Thanks.
-
@mmajian said in Netgate SG-3100 LAN ports cannot go through LAN Gateway.:
@Derelict Great, thank you. I created a BLOCK rule and it's working.
Now I am backing LAN ports can't reach LAN gateway problem. Looks like fixing problems with WirelessNetwork doesn't fix LAN net.Yet another victim.
Someday people will listen.
-
johnpoz LAYER 8 Global Moderatorlast edited by johnpoz Oct 14, 2019, 11:39 PM Oct 14, 2019, 11:36 PM
See that tab you showing the ports - hit the vlan tab.. lets make sure nothing messed up there
That is the default settings, from one of my 3100s
You don't have any rules in in your floating tab do you? And for good measure lets see the routes.. under diag..
-
@johnpoz Yes, my VLANs setting are same as yours. And I don't have rules in floating tab. And here is the routes:
login-to-view -
johnpoz LAYER 8 Global Moderatorlast edited by johnpoz Oct 15, 2019, 12:28 AM Oct 15, 2019, 12:27 AM
Have you tried reloading the firewall rules? Or I take it you have tried rebooting it? ;)
Try changing the IP to say 192.168.2.1/24 on the lan interface?Everything looks right..
Are you seeing any errors on the interface, in the interface status?
LAN Interface (lan, igb0) Status up MAC Address 00:08:a2:0c:e6:24 - ADI Engineering IPv4 Address 192.168.9.253 Subnet mask IPv4 255.255.255.0 IPv6 Link Local fe80::208:a2ff:fe0c:e624%igb0 IPv6 Address 2001:470:snipped::253 Subnet mask IPv6 64 MTU 1500 Media 1000baseT <full-duplex> In/out packets 461831409/992950006 (321.12 GiB/1.27 TiB) In/out packets (pass) 461831409/992950006 (321.12 GiB/1.27 TiB) In/out packets (block) 8743/0 (506 KiB/0 B) In/out errors 0/0 Collisions 0
You tried a different port?
-
Looks like you have pfBlocker installed. Let's see the floating firewall rules. You maybe need to edit them to see all the info.
That can block and not log traffic in LAN if it;s not configured correctly.
Steve
-
johnpoz LAYER 8 Global Moderatorlast edited by johnpoz Oct 15, 2019, 12:29 AM Oct 15, 2019, 12:28 AM
He stated he has no rules on floating.
You didn't setup any port forward rules did you?
I would like to see the full output of the rules to be honest
https://docs.netgate.com/pfsense/en/latest/firewall/viewing-the-full-pf-ruleset.html -
@johnpoz No, zero errors on LAN interface and I did tried different ports. And I did tried change LAN IP to 192.168.10.1/24, still not working.
-
@stephenw10 I disabled pfBlocker but no luck.
-
@johnpoz No port forward rules. No errors on LAN interface:
login-to-view
Here are all rules
login-to-view
login-to-view -
@mmajian said in Netgate SG-3100 LAN ports cannot go through LAN Gateway.:
Yes, my VLANs setting are same as yours.
Please post them.
It's not rules (though it looks like you are still using a
!
LAN net rule for some inexplicable reason.) -
@Derelict Sure, here is my VLAN:
login-to-view
Here are ports:
login-to-view
And I disabled all firewall rule here:
login-to-view
I uninstalled pfBlocker and disabled OpenVPN. Then reboot the firewall but still no luck.
Next thing I am going to try is reset to factory default.
But if that still not working I think it might be the hardware problem. -
Disabling pf will, as it says there, disable NAT so you will be unable to connect to any public IPs from any internal interface.
You should still be able to connect to LAN though...It seems unlikely to be a hardware issue since clients on LAN are still able to pull a DHCP address, traffic is able to flow both ways for that to happen.
Do you see the connected LAN client in the ARP table? (Diag > ARP)
Steve