![]() ![]() # ip address delete 10.10.141.253/24 dev eth0įrom 10.10.141.83 icmp_seq=1 Destination Host Unreachableįrom 10.10.141.83 icmp_seq=2 Destination Host Unreachableįrom 10.10.141.83 icmp_seq=3 Destination Host UnreachableĤ packets transmitted, 0 received, +3 errors, 100% packet loss, time 3016msĪctually dead simple. Refer to the documentation on Interface Commands for more information. Inet 10.10.141.83/24 brd 10.10.141.255 scope global eth0 The extended ping test can be performed without a loopback plug by setting the CSU/DSU to loopback mode however, using a loopback plug is more effective to isolate problems. ![]() Still, I'm intrigued by the technical aspects of this and want to experiment on this subject on my own.Ģ: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 ![]() Since this seems to be harder than expected, our team at work made the decision to test the Linux boxen ethernet ports by picking up a small home NAT router and then pinging the router, and putting that in the hardware test fixtures. Maybe make my own "loopback adapter plug" using a keystone jack + some wires from a hardware store, and try to see if I can peek at the signals using an oscilloscope or logic analyser to ensure that signals are actually hitting the wire. I'll have to try out some of these ideas this weekend to see what happens. UPDATE: Added comments about why I'm testing the boxes in the above comments. The ping command first sends an OAM command loopback cell to the destination and then waits for an OAM response loopback cell. Ex: ping -I AddressA AddressBĪlso, is there a test available that would test the Ethernet interface solely on a L2 / MAC address level using the loopback plug? If I recall, RealTek had a diagnostics tool for their 8139 ethernet adapters that did a L2-only loopback test of sorts, and I was wondering if there was a linux tool that did the same. The simpler ping command provides an interactive mode for testing ATM network connectivity. In IBM Navigator for i, expand IBM i Management > Network > All Tasks > TCP/IP Configuration and click Work with Ping. I'd like to be able to setup two different IP addresses (AddressA and AddressB) on one Ethernet interface, and then run a ping from AddressA to AddressB. If you are still unable to make this work after reviewing the above material (and similar articles around the web), we recommend engaging our Enterprise Support team by creating a support case.For a project at work, I need to be able to test various Ethernet NICs by connecting them to a "loopback adapter plug", like this one on various embedded Linux boxen that come off a production assembly line. In order to work around this situation, it is possible to use advanced routing and rules on the host side to guarantee that the Linux kernel will not accept traffic on a given interface if the destination IP is not defined on the incoming interface.Įxamples of this type of configuration can be found on the web, for example:īut our recommendation is to use 2 separate systems to perform network testing and throughput measurements, as this type of test case is more representative of real-world capabilities. In Linux, when multiple interfaces on a node belong to the same subnet, it can lead to unexpected network behavior (as Linux hosts may respond to incoming packets via a different interface than the packet came in on). With both ports connected in the same system, I assume you are assigning each interface an IP which is on the same subnet. Welcome, and thank you for posting your inquiry to the NVIDIA Developer Forums! Host loopback refers to the fact that no data packet addressed to 127.0.0.1 should ever leave the computer (host), sending it - instead of being sent to the local network or the internet, it simply gets 'looped back' on itself, and the computer sending the packet becomes the recipient. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |