| View previous topic :: View next topic |
| Author |
Message |
Spanik
l33t
Joined: 12 Dec 2003
Posts: 942
Location: Belgium
|
 Posted: Sun Oct 23, 2022 11:10 am Post subject: network issue after update @world (SOLVED) |
 |
|
I ran an "emerge -uvUD @world" 2 days ago and since then I have a few strange network issues. Problem is cannot find where it goes wrong.
Current network config:
- desktop with 2 ethernet interfaces eno0 and eno1
- both interfaces are bonded with 802.3ad and use DHCP
- the DHCP server is the modem of the provider that has IP 192.168.2.1.
- I receive IP 196.168.2.54
Then there is a NAS
- 2 interfaces bonded and set to LACP
- fixed IP of 192.168.2.8
The modem of the provider sits at IP 192.168.2.1
I also have my laptop wich is wired to the switch and gets an IP 192.168.2.35 with DHCP.
This all is connected to a TP-SG2216 switch:
- it has a fixed IP of 192.168.2.3
- ports 5&6 are a LAG group set to LACP --> here the desktop is connected
- ports 7&8 are a LAG group set to LACP --> here the NAS is connected
- laptop sits at port 1
- modem of the provider sits at port 16
- wifi router on port 2 with fixed IP 192.168.2.4
Before the update everything went fine. I could connect to the NAS (NFS), enter the management webpage of the NAS and enter the management webpage of the switch from the desktop.
Since the update I cannot connect anymore to the management webpage of the switch from the desktop. I cannot even ping it anymore. If I try the same from the laptop everything is ok. And that one got the same update. The NAS has disappeared completely from the network.
The strange thing is that it is only from the desktop to the switch that I have this issue. I can connect to the modem, the internet, ping the modem or the laptop etc.
| Code: | kke@daw ~ $ ifconfig
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.2.54 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fd10:3da9:ee3:0:f4ca:5699:7d99:7ddd prefixlen 64 scopeid 0x0<global>
inet6 2a02:a03f:610b:1300:7665:9ac1:d9a3:3e71 prefixlen 64 scopeid 0x0<global>
inet6 fe80::8341:bdab:54f8:d9f0 prefixlen 64 scopeid 0x20<link>
ether 6a:13:f3:25:4b:f8 txqueuelen 1000 (Ethernet)
RX packets 5223 bytes 2263379 (2.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2230 bytes 240841 (235.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eno1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 6a:13:f3:25:4b:f8 txqueuelen 1000 (Ethernet)
RX packets 2566 bytes 251151 (245.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 57 bytes 7068 (6.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xef800000-ef87ffff
eno2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 6a:13:f3:25:4b:f8 txqueuelen 1000 (Ethernet)
RX packets 2657 bytes 2012228 (1.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2173 bytes 233773 (228.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xef700000-ef77ffff
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 27 bytes 2508 (2.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 27 bytes 2508 (2.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ikke@daw ~ $ ping 192.168.2.3
PING 192.168.2.3 (192.168.2.3) 56(84) bytes of data.
^C
--- 192.168.2.3 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4116ms
ikke@daw ~ $ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.624 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.594 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.688 ms
^C
--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2035ms
rtt min/avg/max/mdev = 0.594/0.635/0.688/0.039 ms
ikke@daw ~ $ ping 192.168.2.35
PING 192.168.2.35 (192.168.2.35) 56(84) bytes of data.
64 bytes from 192.168.2.35: icmp_seq=1 ttl=64 time=0.233 ms
64 bytes from 192.168.2.35: icmp_seq=2 ttl=64 time=0.248 ms
64 bytes from 192.168.2.35: icmp_seq=3 ttl=64 time=0.209 ms
64 bytes from 192.168.2.35: icmp_seq=4 ttl=64 time=0.204 ms
^C
--- 192.168.2.35 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3107ms
rtt min/avg/max/mdev = 0.204/0.223/0.248/0.017 ms
ikke@daw ~ $ ping 192.168.2.15
PING 192.168.2.15 (192.168.2.15) 56(84) bytes of data.
From 192.168.2.54 icmp_seq=1 Destination Host Unreachable
From 192.168.2.54 icmp_seq=2 Destination Host Unreachable
^C
--- 192.168.2.15 ping statistics ---
4 packets transmitted, 0 received, +2 errors, 100% packet loss, time 3060ms
pipe 2
ikke@daw ~ $ |
That 192.168.2.15 is an IP address I could not place. It is not the printer, not the WIFI router. I cannot ping it or connect to it from the desktop. The laptop however has no problem. The laptop can ping it and it connects to a webpage of "Supermicro". Which is very strange, this looks like a management interfac of the desktop! The desktop is based on a Supermicro board.
Another strange this is that I cannot ping or connect to the management page of the WIFI router from the desktop. Again no problem from the laptop.
So far I have already rebooted everything in different sequences. But no changes.
_________________
Expert in non-working solutions
Last edited by Spanik on Mon Oct 24, 2022 1:03 pm; edited 1 time in total |
|
| Back to top |
|
 |
Spanik
l33t
Joined: 12 Dec 2003
Posts: 942
Location: Belgium
|
| Posted: Mon Oct 24, 2022 12:48 pm Post subject: |
|
|
I changed the switch to a similar TP-Link SG2008. Made a LAG with port 1&2 and connected the wifi router, modem and laptop as well.
The switch sits at 192.168.2.5 (fixed). Now I can see all other devices on the network. EXCEPT the switch I'm connected to. It does not answer to a ping and I cannot get into the webmanagement page.
If I remove one of the cables of the bond and restart net.bond0 then I can see the switch 192.168.2.5 and all other devices.
What has changed in the bind module so I cannot see the IP I'm connected to anymore?
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
Spanik
l33t
Joined: 12 Dec 2003
Posts: 942
Location: Belgium
|
| Posted: Mon Oct 24, 2022 1:03 pm Post subject: |
|
|
SOLVED: somehow the switch had lost the setting of the LAG. Originally it was set as LACP but it had reverted to "static LAG". So it did not work when connected as a bond but it did work when one of the cables of the bond was removed.
I almost ordered a new switch...
_________________
Expert in non-working solutions |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
