Soldato
Hi people,
So this is my topology of my home network:
I have this weird issue, which i think is down to the Ethernet over Powerline converters, where if I am connected to the WiFi of the Sky router, for some reason I cannot access the HTTP management page for the AV500 WiFi extender, nor can I connect to the Raspberry Pi. If I am connected to the WiFi of the extender, then I am usually able to connect to the Pi.
I know the EoP devices tend to have annoying power saving modes that can cause drop outs, so I have got the Raspberry Pi pinging the Sky Router and the AV500 WiFi device ever minute to try and stop that power saving from kicking in.
The Sky Router acts as a DHCP for the network, and when I am connected to it, it spits the following config out for IP:
Wireless LAN adapter WiFi:
Connection-specific DNS Suffix . : Home
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
The Sky router is on 192.168.0.1 and the Wifi Extender is on 192.168.0.2.
I think it is down to the Sky router just not knowing where things are on the network, so it doesn't know where to route packets.
Should I just use a DHCP server running on my Pi to be able to get more control over the IP config that devices get?
So this is my topology of my home network:
I have this weird issue, which i think is down to the Ethernet over Powerline converters, where if I am connected to the WiFi of the Sky router, for some reason I cannot access the HTTP management page for the AV500 WiFi extender, nor can I connect to the Raspberry Pi. If I am connected to the WiFi of the extender, then I am usually able to connect to the Pi.
I know the EoP devices tend to have annoying power saving modes that can cause drop outs, so I have got the Raspberry Pi pinging the Sky Router and the AV500 WiFi device ever minute to try and stop that power saving from kicking in.
The Sky Router acts as a DHCP for the network, and when I am connected to it, it spits the following config out for IP:
Wireless LAN adapter WiFi:
Connection-specific DNS Suffix . : Home
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
The Sky router is on 192.168.0.1 and the Wifi Extender is on 192.168.0.2.
I think it is down to the Sky router just not knowing where things are on the network, so it doesn't know where to route packets.
Should I just use a DHCP server running on my Pi to be able to get more control over the IP config that devices get?