VLAN cannot ping is gateway!
-
So from my edited example... Your saying you can ping from some 192.168.1.x device you can ping 192.168.1.1, 192.168.5.1 but not 192.168.9.1
And what exactly is the mask on this device in your lan? lets for example see the output of ipconfig on this device in your lan. And lets see the interface you setup on vlan 5 on pfsense.
example here is my lan device
What specific interface do you have these setup on? This is on a switch port I take it on your 7100 - lets see that config.
-
@johnpoz In your example :
From my LAN ping :
192.168.1.1 = OK, Hosts = OK
192.168.9.1 = OK, Hosts = Failed (no access to anything on this VLAN)
192.168.5.1 = OK, Hosts = OK -
@snoopyski All of this works before I changed the old Sonicwall for a Netgate 7100-U1
-
This post is deleted! -
@snoopyski said in VLAN cannot ping is gateway!:
192.168.9.1 = OK, Hosts = Failed (no access to anything on this VLAN)
So you can ping pfsense IP on vlan 9 from lan.. But you can not ping hosts on this vlan.
So sniff on vlan 9 interface.. Get a running ping going from your lan to 192.168.9.x do you see the ping go out??
This is 10 second test...
Can pfsense ping this 192.168.9.x IP from the ping in the gui?
edit:
why do you have all your interfaces assigned to lagg0 ? This is the uplink of the soc.. You should not have interfaces assigned to that.. -
@johnpoz No pfsense cannot ping 192.168.9.1 and other hosts
-
@snoopyski see my edit... Why do you have interfaces assigned to your lagg which only contains the uplink to the soc..
That sure doesn't seem right to me.. Calling @stephenw10
-
@snoopyski said in VLAN cannot ping is gateway!:
No pfsense cannot ping 192.168.9.1 and other hosts
But your saying devices from lan can ping 9.1?
But pfsense both from cmd line and from gui can not ping its own IP address?
-
@johnpoz said in VLAN cannot ping is gateway!:
@snoopyski said in VLAN cannot ping is gateway!:
No pfsense cannot ping 192.168.9.1 and other hosts
But your saying devices from lan can ping 9.1?
No devices on LAN cannot ping hosts on 9.1
But pfsense both from cmd line and from gui can not ping its own IP address?
From the cmd (shell) I can ping its own IP 192.168.9.1 but not from GUI if the source is LAN, if the source is WAN I can ping 192.168.9.1
-
@johnpoz said in VLAN cannot ping is gateway!:
@snoopyski see my edit... Why do you have interfaces assigned to your lagg which only contains the uplink to the soc..
That sure doesn't seem right to me.. Calling @stephenw10
It's the Netgate default setup out of the box! What's wrong?
-
@snoopyski said in VLAN cannot ping is gateway!:
but not from GUI if the source is LAN, if the source is WAN I can ping 192.168.9.1
That makes no sense at all.. Other than a mask issue..
Can you post your routing table please.
-
@johnpoz Don't put WAN IP for security reasons ;-) :
All WAN route addresses is on lagg0.4090
-
@snoopyski said in VLAN cannot ping is gateway!:
Hello everyone,
I have 2 VLAN :
VLAN9 and VLAN5
Same settings, VLAN9 in the Netgate "Diagnostics ping" section cannot ping itself the VLAN9 gateway from VLAN9 source BUT works fine for the VLAN5 for itself
So the result is :
LAN cannot reach VLAN9 devices and VLAN9 cannot reach LAN devices
PS : Of course, my rules ares open for my test
Any Idea ? The device is Netgate 7100U
Best regards
In that VLAN, did you create something in the "System/Routing/Gateways" menu?
When I was starting with Pfsense, I went through a similar error, but my mistake was that I didn't need to create a gateway for each vlan, because the IP you define in it will be your gateway.
If you created it, just go and disable the Gateway from the vlan and everything will work.