This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Interface link not available (Intel 82547L)

Hello,

I've recently bought my self a Jetway NF9N with the additonal NIC-daughterboard (4x Intel 82574L)
The UTM (9.315-2) is running, I use one of the 82574L as my eth1 to access the WebAdmin and the SSH.

My problem now is, I created a new interface on eth2 (82547L), activated it, connect another PC via crossover cable to it. But the link on the interface is not coming up.

Altough it says so in the ifconfig output:
win-fw-001:/home/login # ifconfig

eth1      Link encap:Ethernet  HWaddr 00:30:18:C6:21:50
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11476 errors:0 dropped:4607 overruns:0 frame:0
          TX packets:5951 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1712573 (1.6 Mb)  TX bytes:4491828 (4.2 Mb)
          Interrupt:16 Memory[:D]0900000-d0920000

eth2      Link encap:Ethernet  HWaddr 00:30:18:C6:21:53
          inet addr:172.16.1.1  Bcast:172.16.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 Memory[:D]0800000-d0820000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:74166 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74166 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:25513700 (24.3 Mb)  TX bytes:25513700 (24.3 Mb)


Now, I've read that the UTM has many problems with the 82574L.

I haven't change anything regarding the offloads, all settings seen here are standard UTM settings.

Here are ethtool outputs for eth1 and eth2.
eth1:
win-fw-001:/home/login # ethtool -k eth1

Features for eth1:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
        tx-tcp-segmentation: off
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp6-segmentation: off
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: on [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]


eth2:
win-fw-001:/home/login # ethtool -k eth2

Features for eth2:
rx-checksumming: on
tx-checksumming: on
        tx-checksum-ipv4: off [fixed]
        tx-checksum-ip-generic: on
        tx-checksum-ipv6: off [fixed]
        tx-checksum-fcoe-crc: off [fixed]
        tx-checksum-sctp: off [fixed]
scatter-gather: on
        tx-scatter-gather: on
        tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
        tx-tcp-segmentation: off
        tx-tcp-ecn-segmentation: off [fixed]
        tx-tcp6-segmentation: off
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off [fixed]
receive-hashing: on
highdma: on [fixed]
rx-vlan-filter: on [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]


It looks the same, all of the offloads are deactivated, or at least are identical.

I don't see any kernel errors in the log from the e1000 driver.
"Just" the link is not coming up.

Could some give me hint what I'm doing wrong? Or what I'm missing.
Thank you in advance!


This thread was automatically locked due to age.
  • the Intel  82574L has a Linux bug in it's driver that Intel seems unwilling to fix.  You need to buy an I2xx series chipset based card or use broadcom netextreme II cards.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • Thank you for your answer!

    But why is my eth1 working, which is also using the 82547L?

    Is the driver support for a Realtek RTL8111F NIC any better?
  • Thank you for your answer!

    But why is my eth1 working, which is also using the 82547L?

    Is the driver support for a Realtek RTL8111F NIC any better?


    Realteks are "win nics"(aka winmodems) and are not recommended.  The Intel bug isn't one that is 100% but it is prevalent enough for folks(including Sophos) have moved to the Intel I2xx series chpsets.  Broacoms netextremes are good too..[:)]

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • Unfortunately my Mini-ITX case is too small for an PCIe card. [:(]

    What irritates me the most is that the interface, which is created during setup, is working fine.
    What is the difference between those two interfaces?
  • Realteks are "win nics"(aka winmodems) and are not recommended.  The Intel bug isn't one that is 100% but it is prevalent enough for folks(including Sophos) have moved to the Intel I2xx series chpsets.  Broacoms netextremes are good too..[[:)]]


    I have room for one low-profile NIC, it's going to require some work to fit it in [[:)]] But it's going tobe worth it.

    Now, do you have any opinions about these NICs/chipsets?

    • HP NC382 (BCM5709)
    • HP 332T (BCM5720)


    Or can you recommend NICs? It must be low-profile, and should have at least 2 ports.