Page 1 of 2

Firmware v1.2.0rc9 bug reports and comments

Posted: Fri Apr 17, 2015 7:10 pm
by sirhc
Please post comments and bug reports for v1.2.0rc8 in this thread.

Mike99 beat the crap out of v1.2.0rc8 so here is the fruits of his labor! - Thanks Mike99 :thumbsup:


FIXES
- Fixed DHCP setting default gateway and DNS
- Fixed VLAN configuration with CLI
- Fixed changing password with CLI

KNOWN ISSUES
- None

Released - 4/17/2015

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Fri Apr 17, 2015 9:15 pm
by lligetfa
Installed rc9 on both MINI and WS24 without issues.

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Sat Apr 18, 2015 4:15 pm
by mike99
Is DHCP snooping fix ? I can't test it right not.

I confirm that vlan configuration seem now fine with default configuration for port beeing exclude instead of untag.
Password change via CLI is also fix.
Capital letter only in VLAN config also fix. Tab after U,T,E fix (retrun nothing).
IP address and netmask configuration on VLANs fixed.

Great job Eric, you fix those fast.

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Sat Apr 18, 2015 4:24 pm
by mike99
Some thing that could make CLI better.
First, you can only get ip address of the management VLAN via cmdline or "show config". It should be add to "show vlans" like other IP address.
Second, after changing config via CLI, config is still on a single line (show config).

Also, iptables seem to not like the vlan id change on management VLAN:
Code: Select all
Netonix Switch(vlan 1)# name test
Netonix Switch(vlan 1)# id 3000
Netonix Switch(vlan 3000)# exit
Netonix Switch(config)# exit
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: Bad rule (does a matching rule exist in that chain?)
iptables: Bad rule (does a matching rule exist in that chain?)
iptables: No chain/target/match by that name
iptables: Bad rule (does a matching rule exist in that chain?)
iptables: Bad rule (does a matching rule exist in that chain?)
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
killall: ntpclient: no process killed
Netonix Switch# show vlans
ID Enable Description 1 2 3 4 5 6 7 8
---- ------ ----------- -- -- -- -- -- -- -- --
3000 true test U U U U U U U U
100 true VLAN 100 T E E E E E E E
 
VLAN 100 IPv4 Address: 192.168.100.20/255.255.255.0

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Mon Apr 20, 2015 2:48 pm
by mike99
Still the same problem for DHCP snooping. As a reminder, I activated DS for port 9 to 12, plugged a edgerouter
port 9 = path to dhcp server
port 10 = edgerouter eth1 configured as dhcp client
port 11 = edgerouter eth0=192.168.1.1 to access it
port 12 = edgerouter eth2 configured as dhcp client

eth1 and eth2 as both received a lease from my server on a other network on port 9.

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Mon Apr 20, 2015 4:56 pm
by sirhc
Hi Mike,

I passed this info on to Eric and requested that he look into this and respond to your testing.

I also suggested that we take your advice on the VLAN range config for the CLI.

Thanks,
Chris

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Mon Apr 20, 2015 5:02 pm
by Eric Stern
mike99 wrote:Still the same problem for DHCP snooping. As a reminder, I activated DS for port 9 to 12, plugged a edgerouter
port 9 = path to dhcp server
port 10 = edgerouter eth1 configured as dhcp client
port 11 = edgerouter eth0=192.168.1.1 to access it
port 12 = edgerouter eth2 configured as dhcp client

eth1 and eth2 as both received a lease from my server on a other network on port 9.


DHCP snooping works perfectly on my test network.

If you could do a wireshark capture of the DHCP traffic on any of those ports I might be able to figure out why its not working for you.

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Mon Apr 20, 2015 8:25 pm
by mike99
I will mirror the ports and capture traffic tomorrow.

If I understand well, every device connected to a port where DHCP snooping is enabled should be able to receive lease but not give those, right ?

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Mon Apr 20, 2015 9:17 pm
by sirhc
I tested DHCP snooping in my LAB today and it does appear to work for me.

I used a WS-8-250-AC - v1.2.0rc9

Port 1 - My network with DHCP server/router
Port 2 - My laptop

With no DCHP snooping on any ports I was able to release and renew IP's.

I enabled DHCP Snooping on port 2 and I was still able to release and renew.

I disable DHCP Snooping on port 2 and enabled on port 1 and was no longer able to get a DHCP address.

Re: Firmware v1.2.0rc9 bug reports and comments

Posted: Tue Apr 21, 2015 9:59 am
by mike99
My setup:

ERL as dhcp server - Edgeswitch 24 ports - Toughswitch - WS-12-250-A - second ERL for testing DHCP snooping

I will try a DHCP server connected directly to the WS-12-250-A instead of via 2 other switch.