v1.4.3rcX Bug Reports and Comments

[diegoms77]

Hello, my English is not good, use google translator.
Brief detail the problem and put images, to see if you understand best:
Currently: Firm v1.4.2rc6
By putting Firm v1.4.2 FINAL: Connection is lost with all ports, the port works only 24 and I get to see.
By putting Firm v1.4.3rcX: the same thing happens with v1.4.2 FINAL.

Tests done with v1.4.3rc4 Firm today:
* I do not have access to any device that are connected port 1 to 23.
* 2 hot I disconnect devices are in port 19 and 20 (UBNT AirGrid Firm.v5.6.6 M5 HP xw), 3-5 seconds and then everything starts and traffic normally.
* Again I connect 1 only UBNT AirGrid Firm.v5.6.6 HP xw M5, and everything falls back.
Finally I step back: the Firm v1.4.2rc6, and everything works normally.
If something is not understood, I apologize for translation and consult me.
regards
Diego

[sirhc]

So you are saying as long as you do not connect the air Grids in port 19 & 20 everything works?

If you connect either device in port 19 and 20 traffic stops but when you remove the device the traffic starts again?

What does the log say?

Do you have SMTP enabled, if so please disable it.

Do you have any Discovery protocol enabled, if so disable it.

[diegoms77]

So you are saying as long as you do not connect the air Grids in port 19 & 20 everything works?

Yes, I be lacking try plugging in another port ..... the AGM5

If you connect either device in port 19 and 20 traffic stops but when you remove the device the traffic starts again?

Yes.
AGM5 disconnected, 3-5 seconds and then starts running everything.
I reconnect only 1 AGM5, p19 or p20 in. And everything falls again to turn the UBNT Lan.

What does the log say?

I did not see something strange in the registry.

Do you have SMTP enabled, if so please disable it.

Yes, I have SMTP enabled at all times

Do you have any Discovery protocol enabled, if so disable it.

Discovery protocol I had disabled at all times
another test is needed? I can make a screenshot with video
or you can enter through teamviewer, I have another additional homelike connection so your teamviewer not cut.

Saludos

[Eric Stern]

Please try 1.4.3rc5.

firmware/wispswitch-1.4.3rc5.bin

[diegoms77]

Please try 1.4.3rc5.

firmware/wispswitch-1.4.3rc5.bin

Yes now.
The traffic is normal with 1.4.3rc5.
With SMTP, Pause Frame, Discovery, Flow Control (all enabled)

[diegoms77]

In the last 3 months is 60 seconds.

[sirhc]

In the last 3 months is 60 seconds.

Captura.JPG

If you are using routing protocols such as OSPF it may take longer than 30 seconds as the OSPF adjacencies have to come up.

If you do it on a bench the switch is down approximately 30 seconds.

Depending on your computer you may have to do an "apr -d *" or it could take longer depending on your arp table.

[diegoms77]

In the last 3 months is 60 seconds.

Captura.JPG

If you are using routing protocols such as OSPF it may take longer than 30 seconds as the OSPF adjacencies have to come up.

If you do it on a bench the switch is down approximately 30 seconds.

Depending on your computer you may have to do an "apr -d *" or it could take longer depending on your arp table.

Thank you
I use OSPF

[lligetfa]

If you do it on a bench the switch is down approximately 30 seconds...

I see two short bounces.

Aug 10 14:40:49 Port: link state changed to 'down' on port 1
Aug 10 14:41:09 Port: link state changed to 'up' (1G) on port 1
Aug 10 14:41:35 Port: link state changed to 'down' on port 1
Aug 10 14:41:37 Port: link state changed to 'up' (1G) on port 1

[lligetfa]

BTW, that log was from a MINI powered by the WS-24 as it was getting the RC5 update. The MINI was already on RC5.