Devices wired to one router can't see wifi devices on another router

dtw · 2016-09-15 20:49:43

I'm totally baffled.

I have two routers connected via Powerline Ethernet. "Andy" (192.168.1.254) is connected to the fibre modem and is the DHCP server. "Basil" (192.168.1.253) has the DHCP server disabled. Both routers have Wifi running with different SSIDs.

The problem:
Devices wired to Andy can't see devices attached to Basil by Wifi
Devices attached by Wifi to Andy can't see devices wired to Basil

Even stranger:
On a device wired to Basil, I can SSH to a device "Carmen" connected to Andy with both wireless and cable, via the wireless interface, BUT when I disconnect the cable between Andy and Carmen I can't connect to Carmen via the wireless interface any more.

I suspect the issue actually lies with Carmen. Traceroute from Carmen to various parts of the network (device connected to Andy and Basil) works fine on eth0 but doesn't work at all on wlan0 but I can ping just fine on wlan0.

I've tried so many things I've totally lost track.

Other oddities:
A device wired to Basil can't traceroute to other devices wired to Basil but can to devices wired and wified to Andy

Carmen:

$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0 eth0
0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 wlan0
$  ip route list
default via 192.168.1.254 dev eth0  src 192.168.1.17  metric 202
default via 192.168.1.254 dev wlan0  src 192.168.1.173  metric 303
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.17  metric 202
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.173  metric 303
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether b8:27:eb:91:06:26 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.17/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba27:ebff:fe91:626/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f4:f2:6d:14:98:65 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.173/24 brd 192.168.1.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::f6f2:6dff:fe14:9865/64 scope link
       valid_lft forever preferred_lft forever

Buddlespit · 2016-09-16 01:33:36

Do you have Andy connected to Basil's 'Internet' port, the one that you would connect to a modem, or to an ethernet port, the client port?

ewaller · 2016-09-16 02:16:21

Yeah, I would go about it a little differently.

Basil's upstream port should be attached to one of the downstream ports on Andy. Turn on Basil's DHCP server, but make Basil serve a different subnet; like 192.168.2.0/24. Make Basil to the 192.168.2.1 address on his network. It will also have a 192.168.1.xx/24 address on Andy's network. This way you will have two networks (which you have anyway). The devices on 192.168.2.0 (those using Basil's SSID) will use Basil as their internet gateway (192.168.2.1). Basil (and all of its clients) will use Andy for its gateway

dtw · 2016-09-16 08:20:52

Reconfigured Basil as suggested by eWaller, then realised...

Buddlespit wrote:

Do you have Andy connected to Basil's 'Internet' port, the one that you would connect to a modem, or to an ethernet port, the client port?

Basil doesn't have a CAT45 upstream port...

So, is this a NAT issue? Would putting one of the routers in bridge mode help? Andy is a sagemcom 2704n and Basil is a Technicolor tg582n.

Actually, just reading a bit more about Basil and it can be used with fibre, and ethernet port 4 is the "upstream" port. That's the one I have been using.

Last edited by dtw (2016-09-16 14:00:07)

ewaller · 2016-09-16 16:08:43

So that we all remain on the same page... Basil has port 4 attached via the powerline bridge to a downstream port of Andy. Basil uses port 4 as the upstream port in the absence of fibre. Basil has its DHCP server enabled, and is configured to serve 192.168.2.0/24. And is still serving 192.168.1.0/24.

Is Basil is providing Andy an address to use for his upstream port? You can check by going into Andie's web GUI.

Edit: I'm convinced the problem is multipath caused on the power line bridge caused by the UK's silly ring circuit wiring

Last edited by ewaller (2016-09-16 16:10:44)

dtw · 2016-09-16 17:02:08

ewaller wrote:

So that we all remain on the same page... Basil has port 4 attached via the powerline bridge to a downstream port of Andy. Basil uses port 4 as the upstream port in the absence of fibre.

That's the status quo

ewaller wrote:

Basil has its DHCP server enabled, and is configured to serve 192.168.2.0/24.

I tried that and didn't have Internet access from devices connected to Basil so I went back to the status quo (for now)

ewaller wrote:

Andy is still serving 192.168.1.0/24.

Andy is still serving .1. - yes, that's correct

ewaller wrote:

Is Basil is providing Andy an address to use for his upstream port? You can check by going into Andie's web GUI.

I think not and that is the (current) issue. Basil's standard config is not as a fibre router so he's just treating port 4 as a downstream port. I think I can change the config as shown here to change that to an upstream port

ewaller wrote:

Edit: I'm convinced the problem is multipath caused on the power line bridge caused by the UK's silly ring circuit wiring

I stalked you on Google and, based on your experience, you're probably right!

Buddlespit · 2016-09-16 20:30:09

Just to satisfy my curiosity, could you connect Andy to one of Basil's ethernet ports and then see if Basil can be seen by Andy? I ask because one of my routers wouldn't let me use it as a bridge and the only way I could get it to server wifi to my main router was to connect it to one of the client ports.

dtw · 2016-09-17 07:05:36

dtw wrote:

ewaller wrote:
Is Basil is providing Andy an address to use for his upstream port? You can check by going into Andie's web GUI.
I think not and that is the (current) issue. Basil's standard config is not as a fibre router so he's just treating port 4 as a downstream port. I think I can change the config as shown here to change that to an upstream port

Uh, no. That's for slightly different model. I was looking at firmware packages here and mine doesn't have USB port, so have to assumed it's not FTTC compatible.

So, no option for upstream ethernet port on Basil.

Arch Linux

#1 2016-09-15 20:49:43

Devices wired to one router can't see wifi devices on another router

#2 2016-09-16 01:33:36

Re: Devices wired to one router can't see wifi devices on another router

#3 2016-09-16 02:16:21

Re: Devices wired to one router can't see wifi devices on another router

#4 2016-09-16 08:20:52

Re: Devices wired to one router can't see wifi devices on another router

#5 2016-09-16 16:08:43

Re: Devices wired to one router can't see wifi devices on another router

#6 2016-09-16 17:02:08

Re: Devices wired to one router can't see wifi devices on another router

#7 2016-09-16 20:30:09

Re: Devices wired to one router can't see wifi devices on another router

#8 2016-09-17 07:05:36

Re: Devices wired to one router can't see wifi devices on another router

Board footer