Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    New Fiber install, fresh Pfsense install, only getting 20Mbps up/down

    Scheduled Pinned Locked Moved General pfSense Questions
    81 Posts 6 Posters 17.1k Views
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      A speed like 20Mbps usually indicates a speed/duplex mismatch somewhere. But if that were the case it would apply to the ISP router too. Also I wouldn't expect to see the spike to 100.

      Is it possible the ISP has registered the MAC of the old router and it shaping your traffic with the new MAC? Try spoofing the pfSense WAN MAC to match the other router.

      Steve

      J 1 Reply Last reply Reply Quote 0
      • J
        jddoxtator @stephenw10
        last edited by jddoxtator

        @stephenw10 One of the first things I did. It won't even connect to the gateway without the spoof. I am starting to highly suspect that there is some conversion algorithm happening in that converter that Pfsense doesn't like.

        My only solution would be to buy a compatable FSP for my intel nic and connect the fiber directly.

        1 Reply Last reply Reply Quote 0
        • JKnottJ
          JKnott @jddoxtator
          last edited by

          @jddoxtator

          I have a 500/20 package from my ISP and have seen over 900 down. The problem is not with pfSense.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          J 1 Reply Last reply Reply Quote 0
          • J
            jddoxtator @JKnott
            last edited by

            @jknott Well, yeah. Getting over 400Mbps isn't a problem. If you were getting 400Mbps less then I think you would agree that it is a slight issue.

            I'm not going to play the "My software is perfect" game here. We do need to explore the reality of the situation. There are fringe case devices that do not play well together regardless of how perfect you think your software is.

            Like I was suggesting, I am highly suspect this offbrand SFP device that came with the converter.

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

              I wouldn't expect anything the converter is doing to affect the connection. As long as it's linked correctly on both sides. But clearly something is happening.

              You might try running a packet capture just to see if there is anything obvious being sent.

              Steve

              J 1 Reply Last reply Reply Quote 0
              • J
                jddoxtator @stephenw10
                last edited by

                @stephenw10

                Ok, I found something. Turns out the ISP router is getting a different remote gateway then the Pfsense router. I'm going to try directing it to that gateway and see what happens.

                1 Reply Last reply Reply Quote 0
                • J
                  jddoxtator
                  last edited by

                  Interesting....

                  the ISP router is getting a gateway IP of 192.24.57.1 and the Pfsense box is getting a gateway IP of 172.31.16.1

                  If I try to point it towards the Gateway of the ISP router, Pfsense tells me that The gateway address 192.24.57.1 does not lie within one of the chosen interface's subnets.

                  keyserK JKnottJ 2 Replies Last reply Reply Quote 0
                  • J
                    jddoxtator
                    last edited by jddoxtator

                    Damn no dice.

                    I found the setting to use out of range IP's in advanced, but even setting it to default gateway it still uses 172.31.17.1

                    1 Reply Last reply Reply Quote 0
                    • J
                      jddoxtator
                      last edited by

                      Noticed another discrepancy. ISP router does not connect IPv6. So I turned it off in Pfsense. No effect, still 20Mbps.

                      1 Reply Last reply Reply Quote 0
                      • J
                        jddoxtator
                        last edited by jddoxtator

                        Really at a loss of what to do now.

                        Here is the entire connectivity screen from the ISP router. Maybe one of you can see something I am not.

                        INTERNET

                        Internet Status
                        Internet Status reflects the status of the ISP connection.

                        Connection Status
                        IPv4 Connection Connected
                        IPv6 Connection Disconnected

                        Internet Settings
                        The table below displays the current state of the Internet connection and settings.

                        Internet Setting Status
                        IPv4 WAN Protocol dhcp
                        IPv6 WAN Protocol dhcpv6
                        MTU Size 1500
                        MSS Size 1460
                        TCP Connection 109
                        RWIN Size 163840
                        Packets Sent 4568070
                        Packets Received 11488214

                        IPv4 Addressing
                        The table below displays currently assigned Internet connectivity settings for the device.

                        Parameter Status
                        Device IPv4 Address 192.24.57.117
                        Device IPv4 Subnet Mask 255.255.255.0
                        DNS Address #1 8.8.8.8
                        DNS Address #2 64.235.98.226
                        Remote Gateway Address 192.24.57.1
                        Link Uptime 0D 0H 0M 44S

                        1 Reply Last reply Reply Quote 0
                        • keyserK
                          keyser Rebel Alliance @jddoxtator
                          last edited by

                          @jddoxtator said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                          Interesting....

                          the ISP router is getting a gateway IP of 192.24.57.1 and the Pfsense box is getting a gateway IP of 172.31.16.1

                          If I try to point it towards the Gateway of the ISP router, Pfsense tells me that The gateway address 192.24.57.1 does not lie within one of the chosen interface's subnets.

                          Your ISP router is likely using a certain tagged VLAN on its interface since it lands in a different subnet and gets a different Gateway.
                          Your pfsense by default uses the untagged native VLAN of the interface.

                          Try using the ISP router, quickly switch to the pfSense and do a packet capture in promiscous mode (diagnostics -> packet capture).
                          See if you capture any frames with a VLAN tag that indicates what VLAN you should be usinng

                          Love the no fuss of using the official appliances :-)

                          J P 2 Replies Last reply Reply Quote 0
                          • J
                            jddoxtator @keyser
                            last edited by stephenw10

                            @keyser

                            Ok, I captured packets from WAN with nothing attached to make sure there was no activity, then started a new capture and unplugged the WAN from the ISP router and directly plugged it into the WAN on the Pfsense router

                            This is what I got after 30 seconds of capture:

                            02:28:01.732611 DTPv1, length 38
                            02:28:02.699840 ARP, Request who-has 192.24.57.1 tell 192.24.57.117, length 28
                            02:28:02.731372 DTPv1, length 38
                            02:28:03.429465 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:03.733838 DTPv1, length 38
                            02:28:04.264595 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:04.796229 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:05.302364 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:05.773757 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                            02:28:06.372418 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:06.683297 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                            02:28:06.816486 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:08.433281 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:08.473367 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                            02:28:08.822134 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:10.838025 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:11.155034 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:11.194577 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:12.003469 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                            02:28:12.854932 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:14.882978 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:16.901047 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:18.975871 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:19.022785 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                            02:28:20.998571 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:22.254055 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:23.002261 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:24.361084 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                            02:28:25.030319 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            02:28:27.049727 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                            

                            It looks like a bunch of spam of IP 0.0.0.68 complaining about topology change. What is interesting is the bridge ID. Is that Pfsense or the ISP gateway?

                            keyserK 2 Replies Last reply Reply Quote 0
                            • P
                              Patch @keyser
                              last edited by

                              @keyser said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                              Try using the ISP router, quickly switch to the pfSense and do a packet capture in promiscous mode (diagnostics -> packet capture).
                              See if you capture any frames with a VLAN tag that indicates what VLAN you should be usinng

                              Does that work?
                              I assumed you would need to put a managed switch in the WAN line, configure port mirror, then do a packet capture on that.

                              keyserK 1 Reply Last reply Reply Quote 0
                              • keyserK
                                keyser Rebel Alliance @Patch
                                last edited by

                                @patch said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                                @keyser said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                                Try using the ISP router, quickly switch to the pfSense and do a packet capture in promiscous mode (diagnostics -> packet capture).
                                See if you capture any frames with a VLAN tag that indicates what VLAN you should be usinng

                                Does that work?
                                I assumed you would need to put a managed switch in the WAN line, configure port mirror, then do a packet capture on that.

                                Depends: If your ISP is routing at the edge (ie: where your fiber is linked), then no, because the switching of boxes causes a link down which takes the routing/VLAN interface down in their equipment. But here in DK, the edge equipment is quite often only a stupid L2 bridge device, and then the quick switch usually sees a bunch of TCP retries and what not from existing sessions being transmitted down your line where you can see the VLAN tag.

                                So it was just an attempted quick fix.

                                Love the no fuss of using the official appliances :-)

                                1 Reply Last reply Reply Quote 0
                                • keyserK
                                  keyser Rebel Alliance @jddoxtator
                                  last edited by

                                  @jddoxtator said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                                  @keyser

                                  Ok, I captured packets from WAN with nothing attached to make sure there was no activity, then started a new capture and unplugged the WAN from the ISP router and directly plugged it into the WAN on the Pfsense router

                                  This is what I got after 30 seconds of capture:

                                  02:28:01.732611 DTPv1, length 38
                                  02:28:02.699840 ARP, Request who-has 192.24.57.1 tell 192.24.57.117, length 28
                                  02:28:02.731372 DTPv1, length 38
                                  02:28:03.429465 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:03.733838 DTPv1, length 38
                                  02:28:04.264595 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:04.796229 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:05.302364 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:05.773757 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                                  02:28:06.372418 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:06.683297 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                                  02:28:06.816486 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:08.433281 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:08.473367 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                                  02:28:08.822134 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:10.838025 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:11.155034 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:11.194577 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:12.003469 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                                  02:28:12.854932 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:14.882978 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:16.901047 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:18.975871 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:19.022785 IP6 fe80::3eec:efff:fe70:1cf5.546 > ff02::1:2.547: UDP, length 36
                                  02:28:20.998571 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:22.254055 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:23.002261 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:24.361084 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
                                  02:28:25.030319 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42
                                  02:28:27.049727 STP 802.1d, Config, Flags [Topology change], bridge-id 8055.e0:2f:6d:a5:16:80.814f, length 42

                                  It looks like a bunch of spam of IP 0.0.0.68 complaining about topology change. What is interesting is the bridge ID. Is that Pfsense or the ISP gateway?

                                  Well we can’t decode everything from this as that is only a summary “overview” of the capture. You need to open it in Wireshark or another pcap decoder application.

                                  However, a few things is obvious. Your ISP is not your average setup since they run Spanning Tree to the client edge - that’s a new for me - never seen that before :-)
                                  But there is also Cisco dynamic trunking protocol frames on the wire, so it seems your ISP is running some VLANs on the wire.

                                  The funny thing though… all the 0.0.0.0:68 frames is your pfSense trying to aqquire a IP address via DHCP - it doesn’t get any. So there is no Internet available to it - how on earth are you testing with success albeit very slow speed?

                                  Love the no fuss of using the official appliances :-)

                                  keyserK J 2 Replies Last reply Reply Quote 0
                                  • keyserK
                                    keyser Rebel Alliance @keyser
                                    last edited by

                                    @keyser Also, the very first ARP frame (the second frame in the capture) is very interesting. I fail to understand how that frame was generated since your pfSense does not have an IP address at this time - and certainly not the public IP address your ISP box had when it was connected.

                                    We want your pfSense to aqquire that IP - or another public IP in the same range - via DHCP, but that has not happened at that time in the capture.
                                    It also seems to be an inbound frame instead of outbound…. So it’s just strange. But it might have our needed VLAN tag attached, so inspect that frame in Wireshark.

                                    Love the no fuss of using the official appliances :-)

                                    1 Reply Last reply Reply Quote 0
                                    • keyserK
                                      keyser Rebel Alliance @jddoxtator
                                      last edited by

                                      @jddoxtator said in New Fiber install, fresh Pfsense install, only getting 20Mbps up/down:

                                      @patch The ISP configures it with DHCP, MAC address and an IP alias. The gateway is picked up automatically.

                                      Converter is UMC-GA1F1T some FS-unlimited brand. The router is just a bog standard consumer router.

                                      Just looked that converter up, and it is a L2 Ethernet media converter. You should be able to simply move the SFP fiber module to a SFP port in your pfSense (if it has any).
                                      As I read your posts, you have already tried that unsuccessfully because your NIC does not recognise the SFP.

                                      But even if you get a compatible SFP for your pfSense NIC, you still need to figure out which VLAN tag to use on your WAN interface in pfSense.

                                      Love the no fuss of using the official appliances :-)

                                      1 Reply Last reply Reply Quote 0
                                      • keyserK
                                        keyser Rebel Alliance @jddoxtator
                                        last edited by keyser

                                        @jddoxtator Ahhh, think I just figured your strange packet capture. You had the ISP router connected to a switch, and the switch to the media converter right?
                                        You then disconnected the ISP router from the switch the same time you connected your pfSense right?

                                        Then the first ARP frame is a broadcast from your ISP router because you had them both connected for a brief split second. And all the Spanning tree frames are from your switch…. :-)

                                        AND: if that’s the case then the ARP frame should have your needed VLAN tag attached. So download and install Wireshark on your machine. Download the packet capture from your pfSense and open it in Wireshark. Inspect the ARP frame, and look at the Ethernet VLAN tag on that frame.

                                        You then need to create that VLAN number on your pfSense, and reassign your WAN interface to that VLAN number on the NIC connected to the switch/media converter.

                                        Love the no fuss of using the official appliances :-)

                                        J 1 Reply Last reply Reply Quote 0
                                        • JKnottJ
                                          JKnott @jddoxtator
                                          last edited by

                                          @jddoxtator

                                          The ISP's router has to be within the address range you get. You can't just change the router address and expect it to work.

                                          PfSense running on Qotom mini PC
                                          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                          UniFi AC-Lite access point

                                          I haven't lost my mind. It's around here...somewhere...

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            jddoxtator @keyser
                                            last edited by jddoxtator

                                            @keyser
                                            Ah, This is very helpful.

                                            I am assuming that the ARP IP address is related to the fact that I have set the gateway manually to the same one as the ISP router and forced static IP for the gateway.

                                            There was no switch between the converter and the ISP router before the WAN port was switched over to the WAN port on the pfsense device.

                                            I will download this Wireshark you speak of and see the details.

                                            Edit: Slight problem... I run Linux on all my devices, is there a wireshark for linux?
                                            Edit2: nvm found it.

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