Request: The user should not change the type of the port used for the mesh or the warning must be added.
Today I met a user scenario. It was completely inexperienced.
There is a Keenetic cable mesh system and there was a change of ISP. The user has chosen the ethernet port (Port 1) that be mesh with the cable as a provider. (Actually, it is enough to change the existing provider (port 0) that only PPPOE information.)
After that, problem is occured.
He removed it from the interface, but the mesh did not continue as a cable. When Backhaul activated it, mesh continued via wireless.
When I looked at the Running-Config, there were outputs that were not in the interface but were configuated. And this was integrated with the Wan (Gigabitethernet1) connection. Sağlayıcı 2 is not visible in the interface. Starting with 10.160.xx.yy IP is for IpoE. (ONT without pppoe)
Instead of cleaning the crumbs with the command, I created a provider in the interface again, and I chose the port default. Then I deleted this interface. Mesh was active again via cable. (I removed extender before, so I added it again.)
I'm adding the self-test that I have taken to the next message after I follow these steps. I hope it's not wrong and you can catch the situation.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
KYTECHNGAMING
Request: The user should not change the type of the port used for the mesh or the warning must be added.
Today I met a user scenario. It was completely inexperienced.
There is a Keenetic cable mesh system and there was a change of ISP. The user has chosen the ethernet port (Port 1) that be mesh with the cable as a provider. (Actually, it is enough to change the existing provider (port 0) that only PPPOE information.)
After that, problem is occured.
He removed it from the interface, but the mesh did not continue as a cable. When Backhaul activated it, mesh continued via wireless.
When I looked at the Running-Config, there were outputs that were not in the interface but were configuated. And this was integrated with the Wan (Gigabitethernet1) connection. Sağlayıcı 2 is not visible in the interface. Starting with 10.160.xx.yy IP is for IpoE. (ONT without pppoe)
Instead of cleaning the crumbs with the command, I created a provider in the interface again, and I chose the port default. Then I deleted this interface. Mesh was active again via cable. (I removed extender before, so I added it again.)
I'm adding the self-test that I have taken to the next message after I follow these steps. I hope it's not wrong and you can catch the situation.
@eralde @Le ecureuil
Edited by KYTECHNGAMING0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.