I switched to Bridge Mode in the AP settings and can’t connect anymore.
What do I do?
Bridge mode APs are typically used to extend existing networks - to add HaLow for example. It’s likely the device is now a DHCP client and is trying to find a DHCP server to get an IP address from.
If you know the mac address, you should be able to ping the all router or all node ipv6 address and access it that way.
Try running
ping ff02::1%eth0
where eth0 should be replaced with the actual name of the interface attached to the device.
If you get a reply from the device, you should be able to ssh into it using the same address format for the ping command above. Try get ssh access with IPv6 and share the output of
cat /etc/config/network
Rann ping ff02::1%<MY_NETWORK_ADAPTER>
using ifconfig to find it.
The command worked initially, but then a few minutes later tried it again and didn’t work. Unplugged and replugged the ethernet cable and it started working again.
Can you share the ping output?
64 bytes from fe80::da3a:ddff:fe20:ab79%enp0s31f6: icmp_seq=229 ttl=64 time=0.356 ms
64 bytes from fe80::7aae:860e:75f3:82d0%enp0s31f6: icmp_seq=230 ttl=64 time=0.063 ms
64 bytes from fe80::da3a:ddff:fe20:ab79%enp0s31f6: icmp_seq=230 ttl=64 time=0.382 ms
64 bytes from fe80::7aae:860e:75f3:82d0%enp0s31f6: icmp_seq=231 ttl=64 time=0.057 ms
64 bytes from fe80::da3a:ddff:fe20:ab79%enp0s31f6: icmp_seq=231 ttl=64 time=0.354 ms
64 bytes from fe80::7aae:860e:75f3:82d0%enp0s31f6: icmp_seq=232 ttl=64 time=0.060 ms
64 bytes from fe80::da3a:ddff:fe20:ab79%enp0s31f6: icmp_seq=232 ttl=64 time=0.363 ms
64 bytes from fe80::7aae:860e:75f3:82d0%enp0s31f6: icmp_seq=233 ttl=64 time=0.054 ms
64 bytes from fe80::da3a:ddff:fe20:ab79%enp0s31f6: icmp_seq=233 ttl=64 time=0.318 ms
There’s two responses here, so you’ll need to identify which is your device.
ssh into one of them with
ssh root@fe80::7aae:860e:75f3:82d0%enp0s31f6
Another approach would be to run a DHCP server on your laptop, but when you do things like that you should be quite careful not to expose it to the wider network.
Personally, I run a router on my desk so I have a DHCP server I control easily available. It makes it a lot easier to test these things.
Ok an option works however I see the connected PCI Ethernet drop on my laptop drop out after a while. Seems up for now but it has happened twice.
Actually, it happened again, the ssh connection would last less than 30s and drop out
Also what is the default /etc/config/network settings to revert from bridge?
This is probably happening because you have your laptop set to use a DHCP client connection, and when DHCP fails it gives up on the ethernet port in some manner.
In terms of ‘reverting from the bridge’, if you don’t have access to the web UI the easiest thing to do is to run firstboot -y && reboot to get back to the original state. This will wipe any changes you’ve made. I don’t want to say ‘these are the default settings’ because that’s subject to change!
But if you want to get into the weeds, the problem is not that there’s a bridge but that the network interface is set to DHCP client. You could just change the protocol on the network interface to static (instead of DHCP), make sure there’s an IP on the interface, and if you want a DHCP server look at /etc/config/dhcp (you’ll probably need to remove an ‘ignore 1’ line from the interface you switched to static).
If you have access to the Web UI, just use the wizard.
1 Like
the web wizard wasn’t available, but the reset command did work thanks
Just be aware that the wizard will change more than just /etc/config/network, so just editing that won’t be sufficient to revert.
Btw, there’s a trick with the wizard: if you’re ever interested in what it’s actually done, load the page with ‘?debug=1’ attached to the URL, and it will stage the changes instead of applying them. You can then view the changes in the UI (top right).
EDIT: ah, I didn’t realise you were on old releases. Most of what I said above only applies to later versions.
1 Like