Hi, jumping into the discussion. I'm a colleague of Jop.
What's this line meant to be doing?
"ip route 10.10.20.0 255.255.255.0 vlan 1"
- This ip route has been deleted. This was pure for testing purposes
Does the Modem have a route to 10.10.20.0?
What does it point to?
- Modem is a Palo Alto P200, which accepts ALL traffic from ANY ip subnet. It's used as default gateway troughout our (current) LAN network reachable under ip 172.16.1.2 (on DEFAULT_VLAN , vlan 1). modem is conected to port 33 untagged.
- So my understanding was that the modem doesn't need to have a route for the 10.10.20.0 range.
- Furthermore, we can't even ping across subnets, so that issues needs to be resolved first.
What is the configured default GW address on the devices in VLAN20?
- 10.10.20.1
What is the configured default GW address on the devices in VLAN1?
- 172.16.1.2
I started thinking that there might be a problem with using the gateway 172.16.1.2 on the default vlan 1 as gateway routing for the vlan's. One thing is for sure. Traffic from the vlan's is not getting routed back.
From vlan 1 (DEFAULT_VLAN) we can ping the 172.16.1.2 interface of the Palo Alto, so that's something that we ofcourse are trying to accomplish from the other vlan's.
The configuration posted above by Jop is from our Core switch. All the other switches also have all vlan's configured, without ip address assignment. The vlan's are tagged over the Trunk connections going to the Core switch.
For now we are only testing on this HP Procurve 6600 core switch.