ne, zadnou zaludnost tam nevidim (krome flame na realtek ovladace obecne na netu)
prikladam vypis z logu pri DHCP nastaveni
ifconfig
eth0 Link encap:Ethernet HWadr 14:da:e9:df:be:f2
inet6-adr: fe80::16da:e9ff:fedf:bef2/64 Rozsah:Linka
AKTIVOVÁNO VŠESMĚROVÉ_VYSÍLÁNÍ BĚŽÍ MULTICAST MTU:1500 Metrika:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
kolizí:0 délka odchozí fronty:1000
RX bytes:7634 (7.4 KiB) TX bytes:7143 (6.9 KiB)
dmesg|grep eth
[ 0.711115] r8169 0000:03:00.0 eth0: RTL8168e/8111e at 0xffffc900018ea000, 14:da:e9:df:be:f2, XID 0c200000 IRQ 46
[ 0.711119] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 0.887570] e1000e 0000:01:00.0 eth1: (PCI Express:2.5GT/s:Width x4) 00:15:17:b8:42:22
[ 0.887573] e1000e 0000:01:00.0 eth1: Intel(R) PRO/1000 Network Connection
[ 0.887651] e1000e 0000:01:00.0 eth1: MAC: 0, PHY: 4, PBA No: D50228-005
[ 1.059743] e1000e 0000:01:00.1 eth2: (PCI Express:2.5GT/s:Width x4) 00:15:17:b8:42:23
[ 1.059747] e1000e 0000:01:00.1 eth2: Intel(R) PRO/1000 Network Connection
[ 1.059821] e1000e 0000:01:00.1 eth2: MAC: 0, PHY: 4, PBA No: D50228-005
[ 2.151282] r8169 0000:03:00.0 eth0: link down
[ 2.151304] r8169 0000:03:00.0 eth0: link down
[ 2.151319] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.071304] r8169 0000:03:00.0 eth0: link up
[ 5.071316] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 8.278249] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
lsmod|grep r8196
r8169 68262 0
mii 12675 1 r8169
journalctl | grep eth0:
led 27 17:15:23 server kernel: r8169 0000:03:00.0 eth0: RTL8168e/8111e at 0xffffc900018ea000, 14:da:e9:df:be:f2, XID 0c200000 IRQ 46
led 27 17:15:23 server kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
led 27 17:15:23 server kernel: r8169 0000:03:00.0 eth0: link down
led 27 17:15:23 server kernel: r8169 0000:03:00.0 eth0: link down
led 27 17:15:23 server kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
led 27 17:15:24 server dhclient[465]: Listening on LPF/eth0/14:da:e9:df:be:f2
led 27 17:15:24 server dhclient[465]: Sending on LPF/eth0/14:da:e9:df:be:f2
led 27 17:15:24 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
led 27 17:15:24 server ifup[451]: Listening on LPF/eth0/14:da:e9:df:be:f2
led 27 17:15:24 server ifup[451]: Sending on LPF/eth0/14:da:e9:df:be:f2
led 27 17:15:24 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
led 27 17:15:26 server kernel: r8169 0000:03:00.0 eth0: link up
led 27 17:15:26 server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
led 27 17:15:27 server avahi-daemon[508]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::16da:e9ff:fedf:bef2.
led 27 17:15:27 server avahi-daemon[508]: New relevant interface eth0.IPv6 for mDNS.
led 27 17:15:27 server avahi-daemon[508]: Registering new address record for fe80::16da:e9ff:fedf:bef2 on eth0.*.
led 27 17:15:31 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
led 27 17:15:31 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
led 27 17:15:42 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
led 27 17:15:42 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
led 27 17:15:59 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
led 27 17:15:59 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
led 27 17:16:06 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:16:06 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:16:15 server dhclient[465]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:16:15 server ifup[451]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:20:11 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
led 27 17:20:16 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
led 27 17:20:27 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
led 27 17:20:45 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
led 27 17:20:52 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
led 27 17:21:03 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:28:11 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
led 27 17:28:17 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
led 27 17:28:23 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
led 27 17:28:32 server dhclient[1056]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
...
Za jiné situace bych řekl, že ta síť je blokovaná, nebo problém jinde, ale v jiném portu, nebo pod Win funguje. Nevím...