v1.3.6 FINAL bug reports and comments

DOWNLOAD THE LATEST FIRMWARE HERE
Topic locked
User avatar
rgunderson
Member
 
Posts: 30
Joined: Tue Dec 30, 2014 1:43 am
Has thanked: 11 times
Been thanked: 3 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 2:06 pm

PING TO 1ST SWITCH:

Pinging 10.10.15.15 with 32 bytes of data:
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=20ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=59ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=9ms TTL=62
Reply from 10.10.15.15: bytes=32 time=10ms TTL=62
Reply from 10.10.15.15: bytes=32 time=9ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=7ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=10ms TTL=62
Reply from 10.10.15.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=7ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=105ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=2ms TTL=62
Reply from 10.10.15.15: bytes=32 time=2ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=2ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=7ms TTL=62
Reply from 10.10.15.15: bytes=32 time=9ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=14ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.15.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: bytes=32 time=2ms TTL=62
Reply from 10.10.15.15: bytes=32 time=10ms TTL=62
Reply from 10.10.15.15: bytes=32 time=19ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: bytes=32 time=3ms TTL=62
Request timed out.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.
Reply from 10.10.28.15: Destination port unreachable.

Ping statistics for 10.10.15.15:
Packets: Sent = 268, Received = 267, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 105ms, Average = 5ms
Control-C
Top
User avatar
rgunderson
Member
 
Posts: 30
Joined: Tue Dec 30, 2014 1:43 am
Has thanked: 11 times
Been thanked: 3 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 2:06 pm

PING TO 2nd SWITCH:

Pinging 10.10.28.15 with 32 bytes of data:
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=11ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=11ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=9ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=11ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=8ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=21ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=59ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=9ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=10ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.15.15: Destination port unreachable.
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=6ms TTL=62
Reply from 10.10.28.15: bytes=32 time=8ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=8ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=4ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=2ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=7ms TTL=62
Reply from 10.10.28.15: bytes=32 time=3ms TTL=62
Reply from 10.10.28.15: bytes=32 time=5ms TTL=62

Ping statistics for 10.10.28.15:
Packets: Sent = 271, Received = 271, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 59ms, Average = 4ms
Control-C
Top
User avatar
sirhc
Employee
Employee
 
Posts: 7416
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 2:09 pm

rgunderson wrote:I take it back, a couple of my WS-8-250-AC units starting acting up after my last post. I think it's unrelated to the firmware as one of the boxes is a unit I have previously RMA's twice. The logs say they are detecting a bridge loop but after spending a long night without sleep I have determined there are none. The suspect switch and the other one (victim?) are strangely taking turns dropping pings. Ive got a screen capture in both video and image showing this and it is easily reproduced. I'd upload it but the forum doesnt like it Pirate4


Some network devices bleed BPDU packets which are used to find loops out on your network. If you are getting FALSE Loop Detects then Disable Loop Protection under the Device/Configuration Tab.

If you Disable Loop Protection I would Enable RSTP instead.

Please read this Post: viewtopic.php?f=17&t=768&p=8284&hilit=BPDU#p8284
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Top
User avatar
rgunderson
Member
 
Posts: 30
Joined: Tue Dec 30, 2014 1:43 am
Has thanked: 11 times
Been thanked: 3 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 2:42 pm

Chris, Thanks for the quick reply! I'll try it again during maintenance hours tonight. All of my towers are exactly the same - 100% UBNT radios and Netonix switch at the tower. The backhauls run back to a Mikrotik (MaxxWave X86) at the NOC in a simple star topology. Unfortunatley, all towers are still bridged and I'm working on getting them routed but thats easier said than done. However, I'm careful and am the only one who touches my network and Ive never had any issues. Which leads me to the question: Do you think it's coincidence that the switch giving me a problem is the one that has acted strangely since I put it into operation?
Top
User avatar
sirhc
Employee
Employee
 
Posts: 7416
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 2:48 pm

rgunderson wrote:Chris, Thanks for the quick reply! I'll try it again during maintenance hours tonight. All of my towers are exactly the same - 100% UBNT radios and Netonix switch at the tower. The backhauls run back to a Mikrotik (MaxxWave X86) at the NOC in a simple star topology. Unfortunatley, all towers are still bridged and I'm working on getting them routed but thats easier said than done. However, I'm careful and am the only one who touches my network and Ive never had any issues. Which leads me to the question: Do you think it's coincidence that the switch giving me a problem is the one that has acted strangely since I put it into operation?


Not sure?
In the logs do you See Loop Protection warning disabling Port X for 90 seconds?
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Top
User avatar
AdamB
Member
 
Posts: 11
Joined: Sat Feb 14, 2015 6:00 pm
Location: East Bay, CA
Has thanked: 1 time
Been thanked: 2 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 4:56 pm

Just to clarify, if a switch detects a cold boot and shuts off PoE, does it remain off, or will PoE be re-enabled on all ports (including the first PoE port) after the switch comes back up?

Is it possible to have the first PoE port not come back up on a normal cold boot (such as after a power failure)?
Top
User avatar
sirhc
Employee
Employee
 
Posts: 7416
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 5:07 pm

AdamB wrote:Just to clarify, if a switch detects a cold boot and shuts off PoE, does it remain off, or will PoE be re-enabled on all ports (including the first PoE port) after the switch comes back up?

Is it possible to have the first PoE port not come back up on a normal cold boot (such as after a power failure)?


No it shuts off the POE on the first POE port and requires you to turn it back on. THis will happen everytime you reboot the switch if you have a WS-6-MINI, WS-8-250-AC, or WS-8-250-DC model.

Here is an RC version that does not if you wish to try it

Click HERE to download v1.3.7rc2 - RELEASE CANDIDATE

We are still working on further improvements but this fixes the reboot issue for the WS-6-MINI, WS-8-250-AC and WS-8-250-DC
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Top
User avatar
rgunderson
Member
 
Posts: 30
Joined: Tue Dec 30, 2014 1:43 am
Has thanked: 11 times
Been thanked: 3 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 9:39 pm

sirhc wrote:
rgunderson wrote:Chris, Thanks for the quick reply! I'll try it again during maintenance hours tonight. All of my towers are exactly the same - 100% UBNT radios and Netonix switch at the tower. The backhauls run back to a Mikrotik (MaxxWave X86) at the NOC in a simple star topology. Unfortunatley, all towers are still bridged and I'm working on getting them routed but thats easier said than done. However, I'm careful and am the only one who touches my network and Ive never had any issues. Which leads me to the question: Do you think it's coincidence that the switch giving me a problem is the one that has acted strangely since I put it into operation?


Not sure?
In the logs do you See Loop Protection warning disabling Port X for 90 seconds?


Yes, "Loop protection: detected loop from port 1 to port 1, disabling port 1 for 180 seconds" which is the uplink port to an AirFiber. After I saw that I knew to start looking for real loops but found none. So, I turned off loop protection and contacted you. As I previously mentioned, the two switches in question both act the same way so it's hard to tell which one or both is the problem. Like I said, the others do not do it at all. Oh, another thing these things do is they show drop down message in light read for a second saying "attempting to communicate" but I dont loose the connection and the customers all seem to work fine. I think I'll order another and start swapping! :working:
Top
User avatar
sirhc
Employee
Employee
 
Posts: 7416
Joined: Tue Apr 08, 2014 3:48 pm
Location: Lancaster, PA
Has thanked: 1608 times
Been thanked: 1325 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 9:50 pm

rgunderson wrote:Yes, "Loop protection: detected loop from port 1 to port 1, disabling port 1 for 180 seconds" which is the uplink port to an AirFiber. After I saw that I knew to start looking for real loops but found none. So, I turned off loop protection and contacted you. As I previously mentioned, the two switches in question both act the same way so it's hard to tell which one or both is the problem. Like I said, the others do not do it at all. Oh, another thing these things do is they show drop down message in light read for a second saying "attempting to communicate" but I dont loose the connection and the customers all seem to work fine. I think I'll order another and start swapping! :working:


You need to stop thinking of Loop Protection as STP/RSTP. A customer end point radio or router could be bouncing or leaking this BPDU packet back at the port it came from, you could have a leaky VLAN on any piece of equipment.

I do not think the switches are bad, what you need to do is run a network analyzer to try and track down the leak or simply leave Loop Protection OFF and use RSTP instead.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Top
User avatar
rgunderson
Member
 
Posts: 30
Joined: Tue Dec 30, 2014 1:43 am
Has thanked: 11 times
Been thanked: 3 times

Re: v1.3.6 FINAL bug reports and comments

Thu Oct 29, 2015 10:03 pm

I hear ya Chris! A few questions:
My CPE are in router mode - do you think a customer router could still leak through?
I'll run some wire shark tonight. Any tips on looking for BPDU packets?
Thanks!
Top
PreviousNext
Topic locked
Return to Hardware and software issues

Who is online

Users browsing this forum: Google [Bot] and 57 guests