orbi RBE371 seems to be munging IP traffic from wifi to ethernet?

willb_1968

Aspirant

Dec 04, 2025

yes, I'm currently double routing (the modem is an xfinity gateway in router mode).

I realize this isn't a common configuration, I'm not necessarily opposed to putting the gateway into bridge mode and leaving the orbi in router mode, but I am currently using multiple ethernet ports on the gateway (one for the orbi, a couple for other devices I don't really need on the orbi network), so I'd have to move those devices behind the Orbi if I do go in that direction (this will be a small one-time annoyance).

The thing is, I don't understand why double routing would produce this observation. The raspbery pi shouldn't think my ssh connection is coming from the 10.0.0.111 address, I expect to see 192.168.0.50, which is the address my laptop has. This weekend I can experiment a bit with putting the gateway into bridge mode, and I also can try leaving the gateway in router mode and putting the Orbi into AP mode (this would be my least favored permanent configuration option, though).

I'll try it out and report back.

StephenB

Guru - Experienced User

Dec 04, 2025

willb_1968 wrote:
I don't understand why double routing would produce this observation. The raspbery pi shouldn't think my ssh connection is coming from the 10.0.0.111 address, I expect to see 192.168.0.50, which is the address my laptop has.

Is the pi connected to the gateway network (either via ethernet or wifi)?

willb_1968

Aspirant

Dec 04, 2025

No, it's only connected to the orbi, the wifi is on the regular (non-guest/non-iot) orbi wifi network and the ethernet is connected to a switch that is connected to the orbi.

there's another pi that is only connected via ethernet (through the same switch), and a 3rd pi that is only connected via wifi (to the same regular wifi network on the orbi only). None of them are connected to the gateway.

here's a view where from the same laptop I have ssh'd to both the ethernet and the wifi:

$ w
 06:51:49 up  6:52,  2 users,  load average: 0.05, 0.07, 0.08
USER     TTY      FROM             LOGIN@   IDLE   JCPU   PCPU  WHAT
user               192.168.0.50     06:51    6:52m  0.00s  0.10s sshd: user [priv
user               10.0.0.111       06:21    6:52m  0.00s  0.10s sshd: user [priv

here's the ifconfig from that pi:

$ ifconfig -a
br-aa29e18e95ac: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.30.9.1  netmask 255.255.255.0  broadcast 172.30.9.255
        inet6 fe80::b808:dff:fe5d:2685  prefixlen 64  scopeid 0x20<link>
        ether ba:08:0d:5d:26:85  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether aa:05:26:77:7a:c9  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.4  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fda8:d24d:b2be::1c2  prefixlen 128  scopeid 0x0<global>
        inet6 fda8:d24d:b2be:0:dea6:32ff:fed9:14dc  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::dea6:32ff:fed9:14dc  prefixlen 64  scopeid 0x20<link>
        ether dc:a6:32:d9:14:dc  txqueuelen 1000  (Ethernet)
        RX packets 133658  bytes 20604270 (20.6 MB)
        RX errors 0  dropped 1  overruns 0  frame 0
        TX packets 461496  bytes 32713016 (32.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 24  bytes 3602 (3.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 3602 (3.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth8ca7352: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::3c3b:52ff:fee8:84f  prefixlen 64  scopeid 0x20<link>
        ether 3e:3b:52:e8:08:4f  txqueuelen 0  (Ethernet)
        RX packets 32177  bytes 4418121 (4.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 28574  bytes 3763866 (3.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethe6bbbff: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::5c6e:1ff:fe8f:1645  prefixlen 64  scopeid 0x20<link>
        ether 5e:6e:01:8f:16:45  txqueuelen 0  (Ethernet)
        RX packets 18660  bytes 2548135 (2.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19035  bytes 3581595 (3.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.156  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fda8:d24d:b2be:0:dea6:32ff:fed9:14dd  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::dea6:32ff:fed9:14dd  prefixlen 64  scopeid 0x20<link>
        inet6 fda8:d24d:b2be::2db  prefixlen 128  scopeid 0x0<global>
        ether dc:a6:32:d9:14:dd  txqueuelen 1000  (Ethernet)
        RX packets 1162  bytes 77016 (77.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 327  bytes 28761 (28.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Forum Discussion

orbi RBE371 seems to be munging IP traffic from wifi to ethernet?