[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 02/02/2021 15:54, Eion MacDonald wrote:
On 01/02/2021 22:47, Simon Waters wrote:On Monday, 1 February 2021 17:52:53 GMT Sebastian wrote:It seems as though 192.168.1.107 is for the Ethernet, and 192.168.1.99 is for the wireless interface. The 192.168.1.71 (Ethernet) address is listed with a prefix length of 32 instead of the usual 24; maybe this is the difference? As for the wireless interface, I can only see one IP address so maybe there were only three in total. Thanks for your continuing help :)Rereading the output for the ethernet interface does look odd. It also lacks a "Dynamic" flag for the extra IP (inet 192.168.1.71/32) address on that interface, so presumably configured manually or by some software you've installed, rather than querying the BT router.This (BT Home Hub 3 router/switch, )is a 'slightly' old BT Router. Are you still getting BT updates to router? On my BT Hub 6, there is severe interaction when using some specific software with more than 2 ethernet connections to same software /site. Specifically Zoom free edition. With machines 2 m apart. When one machine (Windows only, not mine) but I use for tutoring a group is on ethernet and other (Linux) is on WiFi (about 2 metre apart) there is no problem. Or other way about, one machine Linux on ethernet, Windows on WiFi there is no problem. There is no problem with any other different machines, 2 m apart when using openSUSE Linux on ethernet or on WiFi. I deduce 'clash' is a specific software and BT Hub dynamic allocation problem. (PS Only fixed IP is printer on ethernet which serves all computers in house)
That sounds like a very peculiar NAT error.... -- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq