Announcement

Collapse
No announcement yet.

Network Test Failed (BIT Linux x86 V4.1)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Network Test Failed (BIT Linux x86 V4.1)

    Hello,

    The system has two network ports, which are connected by a lan cable
    Linux BIT network test failed, but Windwos edition BIT can pass the test (BIT Windows edition V10.0)
    Linux network related settings are as follows, and Windows settings are similar.
    please help ! Thanks.


    enp65s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 1.1.1.2 netmask 255.255.255.0 broadcast 1.1.1.255
    inet6 fe80::b901:a409:296a:504d prefixlen 64 scopeid 0x20<link>
    ether ac:9e:17:2f:96:52 txqueuelen 1000 (Ethernet)
    RX packets 118 bytes 25765 (25.7 KB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 108 bytes 13686 (13.6 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp65s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 1.1.1.3 netmask 255.255.255.0 broadcast 1.1.1.255
    inet6 fe80::d874:64ed:ed64:41e3 prefixlen 64 scopeid 0x20<link>
    ether ac:9e:17:2f:96:53 txqueuelen 1000 (Ethernet)
    RX packets 72 bytes 9390 (9.3 KB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 101 bytes 12754 (12.7 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    If select "Test all available NICs" , can't test.
    Click image for larger version

Name:	Screenshot from 2021-11-05 10-40-17.jpg
Views:	104
Size:	37.5 KB
ID:	51668Click image for larger version

Name:	Screenshot from 2021-11-05 10-45-54.jpg
Views:	67
Size:	51.3 KB
ID:	51669

    If not selected "Test all available NICs" , it can be tested but only test network1.
    Click image for larger version

Name:	Screenshot from 2021-11-05 10-46-19.jpg
Views:	68
Size:	50.0 KB
ID:	51670


  • #2
    Hello,
    Can someone help me answer?

    Comment


    • #3
      Linux behaves differently to windows when using a local IP address, it will route all the traffic through local loopback if a destination address is determined to be on the same system.
      When using the "Test all available" option the "bind" function is used to connect each network card to a specific external address, if a local address is used then the bind call will fail (hence the error message). When not using this option all the packets will be routed over the local loopback address.

      Comment


      • #4
        Thanks for reply
        So is this a loopback test of two LAN ports on the same system?
        Use IP to identify instead of device ID?
        (Because the device ID are seen to be the same, but in fact the two LAN ports device ID are different)
        Click image for larger version  Name:	Screenshot from 2021-11-05 10-46-19.jpg Views:	0 Size:	50.6 KB ID:	51721
        Last edited by Gerald; 11-16-2021, 10:06 AM.

        Comment


        • #5
          If those IPs are not external IPs then the traffic isn't really going anywhere (see attached picture, if you watch the network statistics only the local loopback packet count will be changing).

          If you want to test both network cards you should be using an external IP and the "test all NICs" option.
          Attached Files

          Comment

          Working...
          X