Replied in the rooWatch thread…
Best DrCWO
I might be the only one complaining, doesn’t mean rooExtend is not misbehaving on the network. If you would do a packet capture (using the below setup), you will observe the issue.
When the wired network interface happens to be on the same subnet (10.0.0.0/24) as the statically configured ip of the wireless hotspot of rooExtend (10.0.0.5/24), then the statically configured IP address will leak via ARP.
So it really doesn’t make sense to start up the wireless hotspot when the device is already plugged in via ethernet.
I can only guess as to why people do not notice it. For one, they may be using the device via wireless instead of wired. Another reason might be that their home network is not on the same subnet as the statically configured IP of the hotspot.
1 Like
Most use 192.168.xxx.xxx at home and with this there’s no collision.
I will see what I can do…
Best DrCWO
Chiming in to this topic as a new user with 10.0.0.x addresses at home, who intends to set up a wired configuration.