Web and Unmanaged
cancel
Showing results for 
Search instead for 
Did you mean: 

1810G doesn't want to route VLAN

 
WimBE
Occasional Visitor

1810G doesn't want to route VLAN

Hello,

Our new 1810g switch doesn't want to route its VLAN correctly. I made a test setup with a juniper firewall. On this firewall I configured one physical interface with these VLANs are sub interface:

Interface 0/4.1 VLAN 11: 10.0.14.1 / 27
Interface 0/4.2 VLAN 12: 10.0.14.33 / 27
Interface 0/4.3 VLAN 13: 10.0.14.33 / 27
Interface 0/4.4 VLAN 14: 10.0.14.65 / 27
Interface 0/4.5 VLAN 15: 10.0.14.97 / 27
Interface 0/4.6 VLAN 16: 10.0.14.129 / 27
Interface 0/4.7 VLAN 17: 10.0.14.161 / 27
Interface 0/4.8 VLAN 18: 10.0.14.193 / 27
Interface 0/4.9 VLAN 19: 10.0.14.225 / 27

On the switch the same VLANids are configured. The switch has IP 10.0.14.35 / SN: 255.255.255.224 / GW: 10.0.14.33 in VLAN 12.
I also installed a laptop with IP 10.0.14.34 / SN: 255.255.255.224 / GW: 10.0.14.33 in VLAN 12, and a server with IP 10.0.14.2 / SN: 255.255.255.224 / GW: 10.0.14.1 in VLAN 11.

Port 24 of the switch is connected to the physical port of the firewall. I enabled a static trunk on this interface and TAGGED all VLANs on port 24. For the ports where the hosts are connected on the switch I have set them UNTAGGED in the VLAN where they belong to, EXCLUDED for the rest.

- ping from 10.0.14.2 (VLAN 11) to the gateway on the FW in VLAN 12: 10.0.14.33 works fine. This host can also ping its own gateway 10.0.14.1 (= FW).

- ping from 10.0.14.34 (VLAN 12) to the gateway on the FW in VLAN 11: 10.0.14.1 works fine. This host can also ping its own gateway 10.0.14.33 (= FW).

- on the switch I can ping both the 10.0.14.1 (GW of VLAN 11) and 10.0.14.33 (GW of VLAN 12).

On the FW I can NOT ping the HOSTS in any VLAN (10.0.14.34 and 10.0.14.2), the same thing is true for on the switch, unable to ping the hosts. The problem seems to be located on the switch. I have no possibility to assign routes on the switch and the configuration options are limited. Still I doubt that this "standard" setup is unable to work on this type of switch.

In previous setups I enabled IP routing on the procurve and then it worked. The 1810g doesn't seems to have this option.

Any ideas?

 

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to Web and Unmanaged. -HP Forum Moderator

 

2 REPLIES
DSV12
Frequent Advisor

Re: 1810G doesn't want to route VLAN

> In previous setups I enabled IP routing on
> the procurve and then it worked. The 1810g
> doesn't seems to have this option.

> Any ideas?

1810G L2 switch only and does not route IP.
WimBE
Occasional Visitor

Re: 1810G doesn't want to route VLAN

I just found out what the errors was. The windows firewall blocked the traffic. Problem is solved. Thanks.