Powerline adapters screw with network IP routing
Discussion
I've got a FTTP modem, which feeds into a 16 port Ubiquiti Switch. From the Switch I have a various Ubiquiti APs, network ports etc, as well as a couple of PowerLine adapters (which send signals to sheds).
In the event of a power cut, it seems that the Powerline adapters boot up quicker, and take over some of the IP routing, and hence screws up my whole internet connection. I have to power everything off, and restart with only the fibre modem and the Switch turned on. Then once that is up and running (about 3minutes) then I turn the powerline adapters back on and all hunky dory.
Not sure why this happens, but it is a ballache, as powercuts are not uncommon in our village.
Is there any setup that can eliminate this issue? Alternatively perhaps a smart socket will have a feature which delays the pass through of power for 3mins after it receives power?
In the event of a power cut, it seems that the Powerline adapters boot up quicker, and take over some of the IP routing, and hence screws up my whole internet connection. I have to power everything off, and restart with only the fibre modem and the Switch turned on. Then once that is up and running (about 3minutes) then I turn the powerline adapters back on and all hunky dory.
Not sure why this happens, but it is a ballache, as powercuts are not uncommon in our village.
Is there any setup that can eliminate this issue? Alternatively perhaps a smart socket will have a feature which delays the pass through of power for 3mins after it receives power?
QuartzDad said:
UPS for the switch? I got one for £100 that will run the router/switches for about an hour if the power goes off.
Hmm thats a good idea. Would need to power both the modem and the switch tho i guess. I'm not fully clear on what it is that the powerlines are doing that is causing the issue.
I wondered whether there might be some DHCP issue going on, so went looking and found this: https://community.tp-link.com/en/home/forum/topic/...
Worth trying to configure the adaptors with static addresses, or update firmware if they're not already up to date? That might stop them offering a DHCP server before the device you actually want to do the job.
Worth trying to configure the adaptors with static addresses, or update firmware if they're not already up to date? That might stop them offering a DHCP server before the device you actually want to do the job.
xeny said:
This seems really odd - is it they're taking over routing, or giving out DHCP addresses? Can you share the model of adapter?
I think you've spotted that I dont fully know what I'm saying. So forget the IP routing comment - its just that the adapters do 'something' to screw it all up.I have a TP Link TL-WPA8630P
kryten22uk said:
I think you've spotted that I dont fully know what I'm saying. So forget the IP routing comment - its just that the adapters do 'something' to screw it all up.
I have a TP Link TL-WPA8630P
https://community.tp-link.com/en/home/forum/topic/207438 would backup the comment above, though it references the V2 of this model.I have a TP Link TL-WPA8630P
You can test if this is happening by running "ipconfig /all" on a PC after a powercut. If the DHCP server is listed as the IP address of one of the TP-Link PL devices, you've most likely found the issue. From the first post in this thread, it also looks like the presence of the DHCP server shows up in the System Log in the management UI for the TP-Links.
Thanks all. Reading those threads, it definitiely seems like my issue is the inherent TPLink DCHP server issue. I've switched to static IP, but from most posts that doesnt fix it. I'll just bin the adapters if not fixed and get another brand which hopefully doesnt have hidden DHP server features.
From what I can see there’s no capacity for these adapters to issue IP addresses through DHCP. I’d reset them to factory settings & make sure the firmware is up to date. In automatic mode they will get their IP settings, inc the default gateway from your router. Make sure you only have one DHCP server on your network.
You could try switching on the guest network feature on the powerline adapter. This will give you a dedicated LAN segment that won’t interfere with the rest of your network but still provide internet access.
Edit: just seen the link provided above, pretty rubbish if it has a bug in its firmware which enables a rogue DHCP server to fire up! I’d still try the guest network as that may give you access to a dedicated IP address range and SSID.
You could try switching on the guest network feature on the powerline adapter. This will give you a dedicated LAN segment that won’t interfere with the rest of your network but still provide internet access.
Edit: just seen the link provided above, pretty rubbish if it has a bug in its firmware which enables a rogue DHCP server to fire up! I’d still try the guest network as that may give you access to a dedicated IP address range and SSID.
Edited by anonymous-user on Tuesday 1st June 20:59
buggalugs said:
Assume the adapters try dhcp for their management ip on boot and if it fails they default to a static one that conflicts with your router. Setting static ips on the adapters that don’t conflict with anything should sort.
I've tried this, although not tested it yet. But from the other linked threads it seems that setting to static doesn't solve it.kryten22uk said:
buggalugs said:
Assume the adapters try dhcp for their management ip on boot and if it fails they default to a static one that conflicts with your router. Setting static ips on the adapters that don’t conflict with anything should sort.
I've tried this, although not tested it yet. But from the other linked threads it seems that setting to static doesn't solve it.Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff