10 mbps full duplex



  • My ISP is proving a 10 mbps link. When I first configure the box, I've put the WAN and LAN interface to autoselect as usual. LAN interface is ok and negociating fine. WAN interface was negociating at 10 mbps half-duplex. After speaking with the provider, he told us to force the wan interface to 10 mbps full duplex. I'm version 2.01 so I tried to do it via the gui, even after a reboot the dashbord shows half duplex. I tried to do it via editing the config file and I still get half duplex, even after a reboot.

    If I do a ifconfig -m re1 the 10 mbps fulld duplex shows as supported.

    If I do a ifconfig -a I see that I'm configured as full duplex, but the active state show half duplex :

    re1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    options=389b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic>ether 90:f6:52:03:50:f6
    inet xxx.xxx.xxx.xxx netmask 0xfffffff8 broadcast xxx.xxx.xxx.xxx
    inet6 fe80::92f6:52ff:fe03:50f6%re1 prefixlen 64 scopeid 0x2
    nd6 options=3 <performnud,accept_rtadv>media: Ethernet 10baseT/UTP <full-duplex>(10baseT/UTP <half-duplex>)
    status: active

    Any idea?</half-duplex></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast>



  • I think
    @heIIvis:

    media: Ethernet 10baseT/UTP <full-duplex>(10baseT/UTP <half-duplex>)</half-duplex></full-duplex>

    is a confusing report.

    Do you have any evidence of misconfiguration other than this confusing report? (Perhaps high error counters on one or both ends of the link?)



  • I'm sure of the problem because I can't get the full speed on the WAN when I do a speed test througt pfsense..But directly with a laptop on the provider device, I get it…



  • Some Realtek NICs have broken the ability to force speed and duplex, which is exactly what it looks like you have there. What that shows is the driver told the NIC to be 10 Mb full duplex, and the NIC is 10 Mb half which means it's still doing autonegotiation and refuses to do what the driver told it. There's no rhyme or reason to it, most Realteks can force speed and duplex just fine, but others with the exact same chipset have that ability broken. You'll have to use a different NIC.



  • Hate to hijack the thread, but what is with providers forcing their interfaces in the first place?  I can see this practice starting back in the days before auto-negotiation, but when is the SOP going to change to ports being set to auto-negotiate unless directed otherwise by the client?  We just went through a minor crisis traced back to a carrier forcing an interface to 100m full duplex when it was connected to our Cisco switch which auto-negotiated 1g-full.



  • @mhab12:

    Hate to hijack the thread, but what is with providers forcing their interfaces in the first place?  I can see this practice starting back in the days before auto-negotiation, but when is the SOP going to change to ports being set to auto-negotiate unless directed otherwise by the client?

    They should, I completely agree. The days of misbehaving autonegotiation are over a decade past us. It has to cause far more problems than it solves for carriers. I can't remember the last time I've seen autonegotiation fail, it's been a very, very long time ago. Especially as much as the complications of forcing speed and duplex are misunderstood by people who should know better, you'd think carriers would get away from it. They don't even do it consistently at times, I have one client with multiple metro E connections from AT&T, some of which are 100/full, some of which are auto. Fun…


  • Netgate Administrator

    @cmb:

    I can't remember the last time I've seen autonegotiation fail,

    Happened to me last week. Realtek NIC in a laptop running Linux Mint, SMC switch. Fail. Much head scratching.  ::)
    I completely agree with it auto by default though.

    Steve



  • @mhab12:

    Hate to hijack the thread, but what is with providers forcing their interfaces in the first place?  I can see this practice starting back in the days before auto-negotiation, but when is the SOP going to change to ports being set to auto-negotiate unless directed otherwise by the client?  We just went through a minor crisis traced back to a carrier forcing an interface to 100m full duplex when it was connected to our Cisco switch which auto-negotiated 1g-full.

    Sometimes, it's due to specific equipment.  I know that Cisco router/ firewall equipment tend not to negotiate well with Intel adapters for some reason.  Both try to be 'slaves' in an auto negotiation scenario and they end up with half-duplex most of the time.

    I've encountered this on Intel GBe NICs paired with ISR 87X, 88X, 17XX & 27XX equipment.  They almost always fallback to 100m half-duplex if I have the NIC set to auto mode.

    I also encountered this on certain Ericsson GPON ONT units where the situation is worse.
    The ONT is GBe capable but refuses to negotiate with the Intel NICs at GBe.  When left to auto-negotiation, the NIC connects at 100m half-duplex.
    If I force it to GBe, the carrier goes down.  Using a Realtek NIC results in full GBe speeds.



  • I had the exact same issue with a realtek 1Gbps port in our datacenter where they force 10full.  The solution was to put an Alix box in there that would actually work at 10full.  Been there for 3 years now with only 2 reboots both of which were upgrades to PFSense.


Log in to reply