Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    WAN Speed Negotiation in 2.81

    Scheduled Pinned Locked Moved General pfSense Questions
    20 Posts 4 Posters 609 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      r801248
      last edited by

      Re: Issue with WAN speed negotiation after upgrading from 2.7 to 2.8 or 2.8.1

      Hello, Gang

      Wondering if any development has been made on the issue of the WAN running at half-duplex in 2.8(2.81). My Supermicro box dropped to half after the upgrade from 2.7, and I only see 80 Mbps, instead of the 1Gbps I get straight from the Modem.

      Thanks,

      W 1 Reply Last reply Reply Quote 0
      • W Offline
        WN1X @r801248
        last edited by

        @r801248 What hardware are you using? NIC, in particular.

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          r801248 @WN1X
          last edited by

          @WN1X

          Supermicro E200-9B, Intel® I210-AT.
          All worked fine till 2.7

          ty

          1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            Is your modem port set to 1G fixed? Do you have any control over that?

            The driver bug in igb has been fixed in 25.11 and will be in 2.9.

            R 1 Reply Last reply Reply Quote 1
            • R Offline
              r801248 @stephenw10
              last edited by

              @stephenw10

              I don't know if it's a fixed 1G, as I have no control. This is one of those dumb Spectrum modems I can't access.

              chpalmerC 1 Reply Last reply Reply Quote 0
              • chpalmerC Offline
                chpalmer @r801248
                last edited by

                @r801248 What model modem is it?

                Some later modems have a couple of ports available that include a 1gig port and a 2.5gig port. The 2.5 gig port will probably be yellow if I remember right.

                The Motorola MB8611 has a single 2.5gb port.

                The Motorola MB8600 has 4 gig ports in which two are bondable. LAGG style.

                ect..

                I am not familiar with a modem that has an adjustable port other than autonegotiate.. but Ive been know to be wrong. Just ask my wife.. ;)

                Triggering snowflakes one by one..
                Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                R 1 Reply Last reply Reply Quote 0
                • R Offline
                  r801248 @chpalmer
                  last edited by

                  @chpalmer

                  It's a EU2251. Just one 2.5G port, plus two ports for voice.

                  W 1 Reply Last reply Reply Quote 0
                  • stephenw10S Offline
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, hard to believe that isn't negotiating then.

                    What does ifconfig -vm show the port is actually linked at?

                    Have you tried setting a fixed speed?

                    R 1 Reply Last reply Reply Quote 0
                    • W Offline
                      WN1X @r801248
                      last edited by

                      @r801248 Have you tried replacing the ethernet cable?

                      1 Reply Last reply Reply Quote 2
                      • stephenw10S Offline
                        stephenw10 Netgate Administrator
                        last edited by

                        Yeah always worth trying.

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          r801248 @stephenw10
                          last edited by r801248

                          @stephenw10

                          Thanks for replying; this is what shows. Yes, I replaced the cord.

                          Edit: Wrong paste. Corrected 😀

                          igb1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=4e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
	capabilities=4f53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,NETMAP,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG>
	ether xxxxxxxx
	inet xxxxxxx netmask 0xfffffc00 broadcast 255.255.255.255
	inet6 xxxxxxxxxxx prefixlen 64 scopeid 0x2
	inet6 yyyyyyyyy
 prefixlen 128 pltime 604800 vltime 604800
	media: Ethernet autoselect (100baseTX <half-duplex>)
	status: active
	supported media:
		media autoselect
		media 1000baseT
		media 1000baseT mediaopt full-duplex
		media 100baseTX mediaopt full-duplex
		media 100baseTX
		media 10baseT/UTP mediaopt full-duplex
		media 10baseT/UTP
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
	drivername: igb1
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S Offline
                            stephenw10 Netgate Administrator
                            last edited by

                            Oh so it's 100M-half. Yeah that's probably the default when negotiation fails.

                            I would certainly try setting it to 1G but that may also fail. But 100% check the cable because that's exactly what you would see if it had a bad conductor.

                            R 1 Reply Last reply Reply Quote 1
                            • R Offline
                              r801248 @stephenw10
                              last edited by

                              @stephenw10

                              I will set it to 1G to see what the heck. The cable should be fine; I get full speed when connecting the workstation to the modem using same.

                              Thanks

                              R 1 Reply Last reply Reply Quote 0
                              • R Offline
                                r801248 @r801248
                                last edited by

                                Update: Forcing 1G messes things up; dpinger and unbound go off/on intermittently.

                                1 Reply Last reply Reply Quote 0
                                • stephenw10S Offline
                                  stephenw10 Netgate Administrator
                                  last edited by

                                  Like the link is flapping? Do you see link events in the system log continuously?

                                  R 1 Reply Last reply Reply Quote 0
                                  • R Offline
                                    r801248 @stephenw10
                                    last edited by

                                    @stephenw10

                                    No, it wasn't flapping. Both services went down. I restarted them, and dpinger came back on, then went off again. These are the logs from that time.

                                    Unbound

                                     15:02:36	unbound	19643	[19643:0] notice: init module 2: iterator
Dec 9 15:02:37	unbound	19643	[19643:3] error: recvfrom 23 failed: Protocol not available
Dec 9 15:02:37	unbound	19643	[19643:2] error: recvfrom 24 failed: Protocol not available
Dec 9 15:02:37	unbound	19643	[19643:1] error: recvfrom 25 failed: Protocol not available
Dec 9 15:02:37	unbound	19643	[19643:0] info: start of service (unbound 1.23.0).
Dec 9 15:02:37	unbound	19643	[19643:0] info: service stopped (unbound 1.23.0).
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 1: 2 queries, 0 answers from cache, 2 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 1: requestlist max 2 avg 1 exceeded 0 jostled 0
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 2: 2 queries, 0 answers from cache, 2 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 2: requestlist max 2 avg 1 exceeded 0 jostled 0
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 3: 2 queries, 0 answers from cache, 2 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Dec 9 15:02:37	unbound	19643	[19643:0] info: server stats for thread 3: requestlist max 2 avg 1 exceeded 0 jostled 0
Dec 9 15:02:37	unbound	19643	[19643:0] info: [pfBlockerNG]: pfb_unbound.py script exiting
Dec 9 15:02:45	unbound	51781	[51781:0] notice: init module 0: python
Dec 9 15:02:45	unbound	51781	[51781:0] info: [pfBlockerNG]: pfb_unbound.py script loaded
Dec 9 15:02:48	unbound	51781	[51781:0] info: [pfBlockerNG]: init_standard script loaded
Dec 9 15:02:48	unbound	51781	[51781:0] notice: init module 1: validator
Dec 9 15:02:48	unbound	51781	[51781:0] notice: init module 2: iterator
Dec 9 15:02:48	unbound	51781	[51781:0] info: start of service (unbound 1.23.0).
Dec 9 15:02:48	unbound	51781	[51781:0] info: service stopped (unbound 1.23.0).

                                    dpinger

                                    Dec 9 15:02:28	dpinger	89049	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr XXXX bind_addr XXXX identifier "WAN_DHCP "
Dec 9 15:02:30	dpinger	89320	WAN_DHCP6 XXXX%igb1: Alarm latency 0us stddev 0us loss 100%
Dec 9 15:02:31	dpinger	89320	exiting on signal 15
Dec 9 15:02:31	dpinger	89049	exiting on signal 15
Dec 9 15:02:31	dpinger	29985	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr XXXX bind_addr XXXX identifier "WAN_DHCP "
Dec 9 15:02:31	dpinger	30198	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr XXXX%igb1 bind_addr XXXX%igb1 identifier "WAN_DHCP6 "
Dec 9 15:02:31	dpinger	30198	exiting on signal 15
Dec 9 15:02:31	dpinger	29985	exiting on signal 15
Dec 9 15:02:31	dpinger	54227	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr XXXX bind_addr XXXX identifier "WAN_DHCP "
Dec 9 15:02:32	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:32	dpinger	86562	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% alarm_hold 10000ms dest_addr XXXX%igb1 bind_addr XXXX%igb1 identifier "WAN_DHCP6 "
Dec 9 15:02:33	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:33	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:34	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:34	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:34	dpinger	86562	WAN_DHCP6 XXXX%igb1: Alarm latency 0us stddev 0us loss 100%
Dec 9 15:02:35	dpinger	54227	WAN_DHCP XXXX: sendto error: 65
Dec 9 15:02:35	dpinger	86562	exiting on signal 15
Dec 9 15:02:35	dpinger	54227	exiting on signal 15
                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S Offline
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      What was in the main system log at that time?

                                      R 1 Reply Last reply Reply Quote 0
                                      • R Offline
                                        r801248 @stephenw10
                                        last edited by

                                        @stephenw10

                                        
Dec 9 15:02:32	php-fpm	22460	/rc.start_packages: Restarting/Starting all packages.
Dec 9 15:02:32	php-fpm	97187	/rc.openvpn: Gateway, NONE AVAILABLE
Dec 9 15:02:32	php-fpm	90270	/rc.linkup: Accept router advertisements on interface igb0
Dec 9 15:02:32	php-fpm	97187	/rc.openvpn: Default gateway setting Interface WAN_DHCP Gateway as default.
Dec 9 15:02:32	php-fpm	90270	/rc.linkup: Accept router advertisements on interface igb2
Dec 9 15:02:32	php-fpm	97187	/rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
Dec 9 15:02:32	php-fpm	22460	/rc.start_packages: Configuration Change: (system): pfBlockerNG: saving Firewall rules
Dec 9 15:02:32	check_reload_status	480	Syncing firewall
Dec 9 15:02:32	check_reload_status	480	Reloading filter
Dec 9 15:02:32	tail_pfb	83372	[pfBlockerNG] Firewall Filter Service stopped
Dec 9 15:02:32	php_pfb	84260	[pfBlockerNG] filterlog daemon stopped
Dec 9 15:02:32	php-fpm	22460	[pfBlockerNG] Restarting firewall filter daemon
Dec 9 15:02:33	tail_pfb	95711	[pfBlockerNG] Firewall Filter Service stopped
Dec 9 15:02:33	php_pfb	97047	[pfBlockerNG] filterlog daemon stopped
Dec 9 15:02:33	lighttpd_pfb	97668	[pfBlockerNG] DNSBL Webserver stopped
Dec 9 15:02:33	tail_pfb	98986	[pfBlockerNG] Firewall Filter Service stopped
Dec 9 15:02:33	php_pfb	1803	[pfBlockerNG] filterlog daemon stopped
Dec 9 15:02:33	lighttpd_pfb	7321	[pfBlockerNG] DNSBL Webserver started
Dec 9 15:02:33	tail_pfb	10900	[pfBlockerNG] Firewall Filter Service started
Dec 9 15:02:33	tail_pfb	12854	[pfBlockerNG] Firewall Filter Service started
Dec 9 15:02:34	php_pfb	11024	[pfBlockerNG] filterlog daemon started
Dec 9 15:02:34	php_pfb	12948	[pfBlockerNG] filterlog daemon started
Dec 9 15:02:34	php-fpm	433	/rc.newwanipv6: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 9 15:02:34	php-fpm	433	/rc.newwanipv6: Default gateway setting Interface WAN_DHCP Gateway as default.
Dec 9 15:02:34	rc.gateway_alarm	34880	>>> Gateway alarm: WAN_DHCP6 (Addr:XXXX%igb1 Alarm:1 RTT:0ms RTTsd:0ms Loss:100%)
Dec 9 15:02:34	check_reload_status	480	updating dyndns WAN_DHCP6
Dec 9 15:02:34	check_reload_status	480	Restarting IPsec tunnels
Dec 9 15:02:34	check_reload_status	480	Restarting OpenVPN tunnels/interfaces
Dec 9 15:02:34	php-fpm	433	/rc.newwanipv6: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
Dec 9 15:02:35	php-fpm	90270	/rc.linkup: Starting DHCP6 client for interfaces igb0,igb2
Dec 9 15:02:35	rc.gateway_alarm	48670	>>> Gateway alarm: WAN_DHCP6 (Addr:XXXX%igb1 Alarm:down RTT:0ms RTTsd:0ms Loss:100%)
Dec 9 15:02:35	check_reload_status	480	updating dyndns WAN_DHCP6
Dec 9 15:02:35	check_reload_status	480	Restarting IPsec tunnels
Dec 9 15:02:35	check_reload_status	480	Restarting OpenVPN tunnels/interfaces
Dec 9 15:02:35	rc.gateway_alarm	47516	>>> Gateway alarm: WAN_DHCP (Addr:XXXX Alarm:down RTT:0ms RTTsd:0ms Loss:100%)
Dec 9 15:02:35	php-fpm	433	/rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 9 15:02:35	php-fpm	433	/rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
Dec 9 15:02:36	php-fpm	22460	/rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 9 15:02:36	php-fpm	22460	/rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
Dec 9 15:02:45	check_reload_status	480	Reloading filter
Dec 9 15:02:45	php-fpm	79375	/rc.linkup: Hotplug event detected for WAN(wan) dynamic IP address (4: dhcp, 6: dhcp6)
Dec 9 15:02:45	php-fpm	79375	/rc.linkup: DEVD Ethernet attached event for wan
Dec 9 15:02:45	php-fpm	79375	/rc.linkup: HOTPLUG: Configuring interface wan
Dec 9 15:02:45	check_reload_status	480	Linkup starting igb1
Dec 9 15:02:45	kernel		igb1: link state changed to DOWN
Dec 9 15:02:46	php-fpm	83799	/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1765292566] unbound[59999:0] error: bind: address already in use [1765292566] unbound[59999:0] fatal error: could not open ports'
Dec 9 15:02:46	php-fpm	83799	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Dec 9 15:02:46	php-fpm	83799	/rc.newwanip: Creating rrd update script
Dec 9 15:02:48	php-fpm	83799	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 0.0.0.0 -> XXXX - Restarting packages.
Dec 9 15:02:48	check_reload_status	480	Starting packages
Dec 9 15:02:48	check_reload_status	480	Reloading filter
Dec 9 15:02:49	php-fpm	22460	/rc.start_packages: Restarting/Starting all packages.
Dec 9 15:02:49	check_reload_status	480	Linkup starting igb1
Dec 9 15:02:49	kernel		igb1: link state changed to UP
                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S Offline
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          Mmm, so it definitely flapped there. You can see the physical linkup events on igb1. It looks like it was already running services after an event at the start of that log too.

                                          But that doesn't really help much here.

                                          Are you able to test putting a switch between the pfSense WAN and the modem?

                                          R 1 Reply Last reply Reply Quote 0
                                          • R Offline
                                            r801248 @stephenw10
                                            last edited by

                                            @stephenw10

                                            I can do that by switching cables from my Brocade or using another switch I have lying around. I will do it tomorrow as I've had a very long driving day today.

                                            Thanks for all your help!

                                            1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post
                                            Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.