Not pinging Netgate Vlan's
-
@stephenw10 Which Switch: pfSense or Cisco?
-
@afcarvalho The 1100, pfSense.
-
@jarhead Yes, I did.
-
The Cisco switch has an IP in the LAN subnet so it can ping other devices in that subnet like the 1100. But if it doesn't have a gateway/default route set it won't be able to ping anything outside that subnet like the VLAN interfaces. It doesn't itself have an IP in the VLAN subnets.
-
@stephenw10 said in Not pinging Netgate Vlan's:
The Cisco switch has an IP in the LAN subnet so it can ping other devices in that subnet like the 1100. But if it doesn't have a gateway/default route set it won't be able to ping anything outside that subnet like the VLAN interfaces. It doesn't itself have an IP in the VLAN subnets.
True, but when he plugged a pc directly into the 1100 he couldn't ping any of the vlans either.
Something has to be wrong in the 1100 switch. -
@afcarvalho Show a pic of the internallan interface page.
-
-
Well guys, I do appreciate your effort in trying to help me but I need to rest for today.
I'll continue tomorrow the chalenge...
See you!
A -
@afcarvalho What type of nic do you have in the pc you're using?
Can you add a vlan tag to it? Check in nic properties/configure/advanced.If you can tag a vlan, make it 30. Then plug directly into the router and see what you get for an IP.
-
The Cisco switch won't even try if it doesn't have a default route. Like any host.
The Windows client connected to it should be able to of course. Whether or not the switch can. But only if DHCP works, which it isn't!Yes, being able to test from a tagged VLAN at the client directly would prove it.
An access port on VLAN1 on the switch should work though. Was that tested?
-
@stephenw10 said in Not pinging Netgate Vlan's:
The Cisco switch won't even try if it doesn't have a default route. Like any host.
The Windows client connected to it should be able to of course. Whether or not the switch can. But only if DHCP works, which it isn't!Actually it is on the LAN which is what he'd get plugging directly in as it's the untagged traffic, and it failed to ping the other interfaces.
Yes, being able to test from a tagged VLAN at the client directly would prove it.
An access port on VLAN1 on the switch should work though. Was that tested?
I asked him to but I don't think he did.
-
@jarhead Configuring the Vlan 30 on the adapter and connecting directly do the Netgate Lan port, works.
A
-
@afcarvalho Hmm, so then the problem is actually the cisco switch. Might wanna post all the pertinent config from it.
-
Yup, must be the Cisco switch.
You could test the other VLANs connected directly to the 1100 but since they are configured identically I have no doubt they would also work.
Unfortunately you're at the edge of my Cisco switch knowledge here.
Steve
-
@stephenw10 Thank you very much Steve.
Your patience thershold is a must.
And you helped a lot.Adriano
-
@jarhead Thank you very much for your resilience.
I'm gonna look for expertise in Cisco Switchs.Adriano
-
@afcarvalho
Try this on the g1/0/1switchport trunk encapsulation dot1q
-
@jarhead I'll try and return to you.
A -
@afcarvalho The Cisco Switch doesn't recognize the command.
-
@afcarvalho problem solved
dhcp in cisco switch configures as relayA
