Firmware v1.2.0rc9 bug reports and comments

[mike99]

on the ERL that I test DHCP client, I added VLAN 100

eth0 192.168.1.1/24 (port 11 untagged VLAN 1 DS enabled, use for management access)
eth0.100 192.168.10.1/24 with dhcp server (port 11 tagged DS enabled)
eth1 dhcp client 192.168.10.100/24 (port 10 untag vlan 100 DS enabled)
eth2 dhcp client 192.168.10.101/24 (port 12 untag vlan 100) DS enabled)

DS not working on WS-12-250A or not working on VLAN ? I will continue to check this out.

[sirhc]

I am thinking this is related to the VLAN being there, I sent a Skype to Eric about it.

[mike99]

No, I think it answer himself without passing through the switch. I will try with 2 ERL.

[mike99]

Sorry, was really dumb to test it on the same device for DHCP server and DHCP client. I need red bull this morning LOL.

ER-PoE as dhcp server - WS-12-150 A - ERL as dhcp client. DS is working fine in this scenario. DCHP server and DHCP clients untagged on VLAN 100. I will try to add a TSPro between the DHCP server and Netonix to check if issue I add was related to this.

Edit:
DS also work fine in this scenario :
ER-PoE as DHCP Server - TSPro - WS-12-250A - ERL as dhcp client
So, it's seem like it's edgeswitch that make DS on the WS let pass DHCP lease on a DS enabled port. DS is disabled on the edgeswitch. I would like to test more but we only have a single edgeswitch and it's in production for our office LAN so I will not play with configuration to do some test.

[mike99]

It was working, now it's not. DS is enabled on every port and still receiving DHCP. Can't attach pcap file on post (the extension pcap is not allowed), I will e-mail it to Eric.

P.S. : Rebooted the switch and now DS work. Had the same problem with STP on a other switch after 1.2.0rc9 upgrade (switch linked to this one via both SFP ports). On the second switch, every ports was always at forwarding until I rebooted it. It was not estetic, I was having loop problem and was loosing access to device until I unplug one of the 2 ports that was causing loop. I think the DS problem begin after the loop problem so maybe it affected the swich. Same with STP, it was not enabled first (after reseting the switch) and I enabled STP after I add loop problem.

[mike99]

Not sure if it's a bug or limitation but port isolation won't work between two switch.

[sirhc]

Not sure if it's a bug or limitation but port isolation won't work between two switch.

Please explain how you are implementing it and what the behavior is.

[mike99]

Isolate port 9 on switch 1 and port 12 on switch 2, both port untagged on VLAN 1. The 2 switch are connected via SFP port 13 on both switch in "trunk" port mode. Device on switch 1 port 9 can still ping device on switch 2 port 12.

[sirhc]

Isolate port 9 on switch 1 and port 12 on switch 2, both port untagged on VLAN 1. The 2 switch are connected via SFP port 13 on both switch in "trunk" port mode. Device on switch 1 port 9 can still ping device on switch 2 port 12.

That is not a bug, that is a limitation of port isolation. Port isolation is limited to the switch it is on.

Ports isolated can not talk to other ports on the SAME switch that are also isolated but the 2 switches do not talk to each other and span port isolation.

[sirhc]

However Mike you will see I posted up rc11 which has your requested CLI VLAN config options!!!