Problem with my connect box 2 and x540-t1 network adapter

Xch · 2023-01-12T18:31:28+00:00

Sunrise Community - Kunden helfen anderen Kunden rund um die Themen Fernsehen, Internet, Telefon und Mobile. Jetzt registrieren!

Xch

I have a home server using x540-t1 network adapter for the ethernet connections.

I configured it with a fixed IP address. It worked well with my old router. It works well with my computer with direct cable connection (PC as gateway).

However, it doesn’t work well with connect box 2. I even tried to connect my server to the box directly (without any switch or cable socket), its ethernet port didn’t light up –> no communication between them. As a result, I cannot access to my server (ping fails in two directions).

As my server works well with all other devices, I’d like to know if there is some compatibility problem for the intel x540-t1 with connect box 2? (from the console page, I cannot see my server in the device list. I never had this problem)

Thanks for your help!

pato

This could be an MDI-X issue or speed negotiation. Try to set the speed to a fixed 1 Gbps and disable MDI-X on the adapter for testing.

Xch

I tried to set fixed speed and disable MDI-X but nothing happens.

—

More details below:

I’m using Proxmox as the OS. The network card is enp130s0. Here is the output of “ip a” when it is connected to my mac. The ethernet sharing (as a bridge) works in this case.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host 

   valid_lft forever preferred_lft forever

2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

link/ether ac:1f:6b:75:fe:e0 brd ff:ff:ff:ff:ff:ff

altname enp5s0

3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

link/ether ac:1f:6b:75:fe:e1 brd ff:ff:ff:ff:ff:ff

altname enp6s0

4: enp130s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000

link/ether a0:36:9f:bc:db:7c brd ff:ff:ff:ff:ff:ff

5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

link/ether a0:36:9f:bc:db:7c brd ff:ff:ff:ff:ff:ff

inet 192.168.2.2/24 brd 192.168.2.255 scope global dynamic vmbr0

   valid_lft 85542sec preferred_lft 85542sec

inet6 fe80::a236:9fff:febc:db7c/64 scope link 

   valid_lft forever preferred_lft forever

And the “ethtool enp130s0” gives the following:

Settings for enp130s0:

    Supported ports: [ TP ]

    Supported link modes:   100baseT/Full

                            1000baseT/Full

                            10000baseT/Full

    Supported pause frame use: Symmetric

    Supports auto-negotiation: Yes

    Supported FEC modes: Not reported

    Advertised link modes:  100baseT/Full

                            1000baseT/Full

                            10000baseT/Full

    Advertised pause frame use: Symmetric

    Advertised auto-negotiation: Yes

    Advertised FEC modes: Not reported

    Speed: 1000Mb/s

    Duplex: Full

    Auto-negotiation: on

    Port: Twisted Pair

    PHYAD: 0

    Transceiver: internal

    MDI-X: Unknown

    Supports Wake-on: d

    Wake-on: d

    Current message level: 0x00000007 (7)

                           drv probe link

    Link detected: yes

When I connected to Connect Box 2 (directly or via a switch), “ethtool enp130s0” gives:

Settings for enp130s0:

    Supported ports: [ TP ]

    Supported link modes:   100baseT/Full

                            1000baseT/Full

                            10000baseT/Full

    Supported pause frame use: Symmetric

    Supports auto-negotiation: Yes

    Supported FEC modes: Not reported

    Advertised link modes:  100baseT/Full

                            1000baseT/Full

                            10000baseT/Full

    Advertised pause frame use: Symmetric

    Advertised auto-negotiation: Yes

    Advertised FEC modes: Not reported

    Speed: Unknown!

    Duplex: Unknown! (255)

    Auto-negotiation: on

    Port: Twisted Pair

    PHYAD: 0

    Transceiver: internal

    MDI-X: Unknown

    Supports Wake-on: d

    Wake-on: d

    Current message level: 0x00000007 (7)

                           drv probe link

    Link detected: no

It appears that the Connect Box 2 doesn’t want to talk with it. I have another management port on this server, it can be connected to Connect Box 2 with the same cable and socket. So the problem remains between my network card and Connect Box 2.

I tried the advised solution using “ethtool –s enp130s0 speed 100 duplex full autoneg off” command. It takes no effect on the result.

pato

Xch There seems to be a layer 1 issue then between the port firmware. I assume you already tried a different port on the CB2?
Regarding the speed, try 1000 full, not 100. Also can you try to disable only MDI-X? That is the recognition of straight/crossed cables. I’ve seen issues with that in the past, if the adapter allows disabling this.
Not sure though if the ethtool commands actually work on the adapter, that is often very driver dependant.

What you could try, get a small 5 port 1 Gbps switch and put that one between the server and the CB2.

Xch

Thanks a lot. A swtich helps in this case.