OC200 (Beta) : wan failure after update
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.OC200 (Beta) : wan failure after update
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I too earferly tested the new beta firmware controller, but it ended on me having to reset everything on the network and starting again from the scratch,
How's my setup?
- Single WAN, it has a fiber SFU ONU plugged into the SFP port of er7206 v1.0 working flawlessly since installation.
- The fiber ISP uses PPPoE for subscriber authentication
before upgrade:
- Everything was working, could configure the connection paramters, the correct vlan..etc
after upgrade
- Internet down, after visting the wan configuration section.. all the VLAN parameters either missing or (after device hard reset)
the "internet vlan" checkbox is greyed out (wth?
) I tried everything, removing configuration, starting over, hard reset of er7206, ended with downgrading controller, resetting everything on the network to get back on track.
It seems to be that the act of "adding a name" to the sfp connection, triggered a save new configuration event that screwed everything up.
I could of course untag the internet vlan on the stick and pretend I have a dumb consumer device but I do not wish to wake up the daemons of the sfp module's firmware which is let's say capricious and obscure.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@DREEMus I have a backup this time for the old controller version that doesn't exhibit this problem..I also have another SFP device which I configured to untag the internet vlan without he router assistance in case something blows up but I rather not to as the device firmware's is also a hit and miss.
- Copy Link
- Report Inappropriate Content
Hello @crrodriguez,
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230429891, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@crrodriguez This is occurring to me as well. In the end, how did you resolve this?
- Copy Link
- Report Inappropriate Content
@mkzwicker This particular issue was fixed a while ago in one of the router's beta firmwares.
I did however permanently changed the way the fiber SFP is configured so the sfp device itself untags the vlan and presents itself to the router as a dumb non-vlan aware device. This solved all the issues I was having.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1470
Replies: 15
Voters 0
No one has voted for it yet.