![]() TX packets:36 errors:0 dropped:0 overruns:0 carrier:0 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 RX packets:357 errors:0 dropped:0 overruns:0 frame:0 TX packets:140 errors:0 dropped:68 overruns:0 carrier:0 RX packets:1388 errors:0 dropped:0 overruns:0 frame:0 ![]() TX packets:34 errors:0 dropped:46 overruns:0 carrier:0 RX packets:191 errors:0 dropped:0 overruns:0 frame:0 TX packets:590 errors:0 dropped:0 overruns:0 carrier:0 RX packets:44357 errors:0 dropped:2143 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 # NOTE: This was when the Windows Client was connected to eth3, eth1/eth2 disconnected the "RUNNING" shows up properly for eth1/eth2 as soon the cable is connected #Įth0 Link encap:Ethernet HWaddr 10:7b:44:a5:ff:42 RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) RTL8111/8168/8411 PCI Express Gigabit Ethernet ControllerĠ7:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Subsystem: Realtek Semiconductor Co., Ltd. Some diagnostics (Note: I changed the public IP address to 42.x.x.x and for MAC adresses the last 4 hex digits were changed): $ lspci -k | grep 'RTL' -A2Ġ6:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. I switched between static IP and DHCP config at the client multiple times to validate this (DHCP=not working, static IP=everything fine). Thus, the NIC at the DHCP server is able to send out packets and the cable/connection is not the issue and the Windows client does actually communicate via this connection. Now sending a ping from the windows client to the DHCP server works (ping reply is received successfully) as long as the cable is connected. ![]() Now the strange thing: I kept everything as it was (DHCP Server having a static IP of 192.168.1.1/24) and configured the windows client to use a fixed IP (192.168.1.2/24). In fact I tried using a Windows machine as a client, where I did not see any DHCP OFFER reply from the server (no packets at all from the DHCP server if I did not overlook any, since the windows machine was just sending a lot if crap out). It looks like the remote device is not receiving the DHCP OFFER. ![]() I see a DHCP DISCOVERY packet coming in, then a DHCP OFFER is sent to the remote device and is later on acknoledged via DHCP ACK from the remote device.īut, for this special NIC (LogiLink 2-Port Gigabit LAN PCI-Express, PC0075 v.2.0 Chipset: RTL8111F see datasheet) I just see multiple DHCP DISCOVERY packets coming in which are replied with a DHCP OFFER on the DHCP server side. This works for the other NICs on the computer. Just NICs and direct connections via RJ45-cable. ![]() Note: There is no router/switch in the setup. I'm experiencing some strange behaviour with a Dual Gigabit Ethernet NIC I've setup a computer which has multiple network interfaces to connect some industrial cameras and setup a DHCP Server (isc-dhcp-server, Ubuntu 16.04) to statically assign their IPs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |