Hello!
Im running a Edgecore ECS2100 switch, and have 3 vlans on it, vlan10, vlan20 and vlan100. Got a DHCP server running behind vlans 10 and 20 (on a trunk port), got a router on vlan 100 for internet.
Vlans 10 and 20 have svi's configured as 10.10.10.1 and 10.10.20.1, vlan 100 is 10.10.100.2, and the router behind it runs 10.10.100.1. That routers other interface runs 192.168.0.1 (fake IP obviously) to connect to the internet.
PC A (example) is connected on vlan10, gets IP 10.10.10.249, default gateway 10.10.10.1. It can ping all the 3 SVIs (so inter-vlan routing should be working ok), AND can ping 10.10.100.1 (so the switch is forwarding data to the router).
Trace routing to 10.10.100.1 gives me 10.10.0.1 -> 10.10.100.1
Trace routing to 192.168.0.1 gives me 10.10.0.1 -> 10.10.0.254 (vlan 10 DHCP's ip) -> 192.168.0.1
Tracerouting anything behind that is a no-go (obviously)
The switch routing table is the following (interface, destination, mask, next hop, metric, protocol):
VLAN 100 0.0.0.0 0.0.0.0 10.10.100.1 0 Static
VLAN 10 10.10.0.0 255.255.255.0 -- 0 Local
VLAN 20 10.10.20.0 255.255.255.0 -- 0 Local
VLAN 100 10.10.100.0 255.255.255.0 -- 0 Local
Switch's default gateways's set to 10.10.100.1 (via CLI, web interfaces got nowhere to config that)
Can't find much info or community for that switch, and cant figure out why its forwarding for a totally stupid IP, instead of to the default route on the routing table - anyone can shed me some light in that?
No comments:
Post a Comment