Netgate 6100 using 2.5Gbe port for WAN?
-
Hello, I know there have been previous topics about this and I have read them before posting. I can't get this to work I'm just wondering why? Comcast recently upgraded me to 1.3GBps service, I bought a new modem and didn't even consider that the firewall had a 1GB WAN port, so I figured I could use one of the 2.5 LAN ports since everything I read says any port can be swapped.
So I searched the topic and found threads telling me to just go to Interfaces -> assignments and swap IX3(default 1GB WAN port) with IGC3 (LAN Port 4 on the 2.5GBe side). I did that, multiple times, rebooted the firewall and all that happens is that my modem gets assigned a private IP address likes it's on the LAN instead of that port being used as WAN.
Is there something else I need to do? Has anyone got this working, one thing I noticed is that no one ever confirmed that it worked. Not sure if it matters, but I am using LAN port 1, and LAN port 2 on the 2.5GBe side as actual LAN ports. My wife and I both WFH so I can only tinker at night and on weekends. Spent all day on this yesterday but no luck.
-
No that should be all that's required.
By default the LAN4 interface is assigned but doesn't have a subnet or a dhcp server running so nothing connected to it should pull a private IP. And obviously it shouldn't if it actually becomes the WAN.
You say the modem pulls a lease in the LAN1 subnet? Or just in a different private subnet?
You may need to power cycle the modem because the MAC address you are connecting with will change from ix3 to igc3 and it may be locked to the old one.
Steve
-
@stephenw10 Hi Stephen, yes the Modem pulls a lease in the LAN subnet that I use for everything. I set this up so long ago and rarely touch it, but I had several devices in the house that 2.5Gbe connections so I had them all using those ports. I do have things connected on LAN1 and LAN2, but I was hoping I could use LAN4 as a WAN port to take advantage of the higher speed, I can't do it now, but tonight I will try as you said and reboot the modem and see if it swaps to WAN on that port. Thank you.
-
Is it actually pulling a lease in the LAN subnet or just happens to be using the same subnet? 192.168.1.X is very common.
Check the DHCP status to be sure.
But I think there's a very good chance it was just locked to the ix3 MAC. We will see...
-
@stephenw10 Yes it's pulling from the 10.100.200 network that I set up. The firewall does handout DHCP to everything, but I figured swapping the port to WAN would disable that. I'll give it a try tonight and report back tomorrow. Thanks for the insight.
-
@stephenw10 Hi Steve, I had time at lunch to take another swing at this, exact same result. I unplugged the modem from the Netgate and also unplugged the power from the modem, swapped the interfaces, reconnected the modem, then plugged it back in to the Netgate, same result, it just gets assigned a LAN IP instead of a WAN IP. In the dashboard it even shows as the WAN interface but it's getting a 10.100.200 address (the internal LAN). I rebooted the firewall just to be safe, but same result. Is there anything else I can try? I will have time again this afternoon as the wife went away on a business trip and I'm not super busy today.
-
Where are you looking at that?
If you look at Status > DHCP Leases is it actually handing out a lease to the modem?
Is 10.100.200.X a subnet you assigned to LAN4?
-
@stephenw10 Hi Sorry for the late reply, I didn't get an email about your last post. Anyway, I did finally get it to work (just now), before I did, I checked what you asked, and yes, after I swapped the Interfaces, the WAN interface was infact receiving a DHCP lease and it was listed there in the leases. So the Netgate WAS giving a LAN DHCP address to the WAN interface temporarily.
What finally worked for me was to, swap the interfaces, reboot the Netgate, once it came back up, it was still giving a DHCP address to the WAN interface, so I rebooted the modem once, it still received the same DHCP address, so I rebooted the modem a second time, it temporarily showed up with it's own 192.168 default IP, then it finally showed the WAN address I was waiting for.
So swap interfaces, reboot Netgate, once it comes back up, reboot Modem, wait for it to come back up, reboot Modem again, wait for a while, it finally gets the WAN address assigned to that interface.
I just did a speedtest and pulled 1600/Mbps down, 300 more than I'm rated for. This pleases me. Thank you for the help.
-
Hmm, well I'm not entirely sure what was happening there but glad you got a good result.
-
@dragonfly said in Netgate 6100 using 2.5Gbe port for WAN?:
So the Netgate WAS giving a LAN DHCP address to the WAN interface temporarily.
Hard to see how that’s possible without cabling connected between the two networks.
-
I have seen it happen in the past when the change is initially made. Somehow the dhcp server is still running on the interface. But not for a while and not beyond the initial switch.
