@Clive_A 

A new build has been released on controller beta firmware section, but i cannot update because it thinks im already on this version - (i think controller only checks the version number, not the build date?)

Can you get us the file so we can update to this?

Hi @GRL 

Thanks for posting in our business forum.

GRL wrote

  @Clive_A 

A new build has been released on controller beta firmware section, but i cannot update because it thinks im already on this version - (i think controller only checks the version number, not the build date?)

Can you get us the file so we can update to this?

 

Wait for some time before the system starts to work properly. Maybe the controller/cloud team has not set it right.

I cannot access any other files except for the beta that the dev sent to me.

Or you wait for the official website update about the downlink for it.

It's the procedure.

  @MR.S 

i know, but the point is the controller should let us do it

I did the roll_back then upgrade via controller

Nice to see the temperature reporting to controller is once again where it should be and not 8-9c higher than it reports in standalone

Everything works as expected with my existing configuration, havent checked to see if the routing issues i had on the first 1.3.0 are fixed yet or not, that will have to wait.

  @Clive_A 

After a lot of testing this morning, i feel pretty confident to say the the new april build of 1.3.0 has resolved the static routing issues i reported.  I can now route from the gateway to any SVI i wish and traffic flows normally, just like i could on 1.2.3 and earlier firmware

  @Sathiya 

enable SSH on the site

use a SSH program to connect to the IP of your router, the username and password are whatever you set "device account" to be in site settings

once connected in SSH, type

en [enter]

roll-back [enter]

it will reboot and be back on 1.2.3

be careful though - before you do this make sure you have disabled any features in the controller that are 1.3.0 specific (virtual wans, DNS ovveride, gateway ACLs using !network etc) otherwise it will lock up.  Ask me how i know this......

Hi @avpopov1977 

avpopov1977 wrote

Hello @Clive_A 

 

few days ago I've tried to use SFP Base-1000T modules and found that SFP/SFP+ ports are not capable for 10/100M connection.

this 2 cooper WAN ports have about 80 meters lengths and connected to different 100M providers.

the purpose of using SPF modules was anti-lighting protection, to keep safe WAN4/WAN5 cooper ports.

here the modules I've used:

They perfectly works at 1G speed. But FT module have an incorrect Online detection (Link is always UP even cable disconnected)

Does anybody tried SFP Cooper ports at 100M? Probably it is a module incompatibility bug?

We do not provide a compatibility guarantee, list, or fix support.

We only recommend TP-Link modules.

And if you have any basic questions about the module or fiber interface: Common Questions About SFP Module and Media Converter