<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SG-5100 Multi-Wan Setup]]></title><description><![CDATA[<p dir="auto">Hi All,<br />
I have an SG-5100 running 21.02-RELEASE and I am having an issue with setting up multiple WANs.</p>
<p dir="auto">I recently purchased a Starlink kit to act as a backup of my primary residential cable modem (just a modem).</p>
<p dir="auto">I've setup my gateway groups and set the default gateway to the group I created:<br />
<img src="/assets/uploads/files/1616817767140-912079b0-935e-4900-97b9-7f059f6afda8-image.png" alt="912079b0-935e-4900-97b9-7f059f6afda8-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto"><img src="/assets/uploads/files/1616817797838-e44745ed-b2c6-4a03-b971-5df01e0bc390-image.png" alt="e44745ed-b2c6-4a03-b971-5df01e0bc390-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">However, if both WAN links are connected at the same time, one of them will go down:<br />
<img src="/assets/uploads/files/1616817879212-d52b11c5-a3cf-47d9-a005-35c6bb32a687-image.png" alt="d52b11c5-a3cf-47d9-a005-35c6bb32a687-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">The "public" IP of my secondary connection dies, and in the ARP table all I am seeing is a 192 address<br />
<img src="/assets/uploads/files/1616817984495-725d81f1-6ade-4c27-a746-8f01b76dd826-image.png" alt="725d81f1-6ade-4c27-a746-8f01b76dd826-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">If I shut off the primary and bounce the port on the secondary it gets an address and works fine:<br />
<img src="/assets/uploads/files/1616818091877-236fa9fb-6835-424e-886f-ad37e8049fe1-image.png" alt="236fa9fb-6835-424e-886f-ad37e8049fe1-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Outbound NAT is set to Automatic outbound NAT rule generation.</p>
<p dir="auto">I have no virtual IPs setup.</p>
<p dir="auto">Looking at the logs when I have both enabled I see this:<br />
<img src="/assets/uploads/files/1616818629500-e9fd8b63-c8cd-4d69-ae40-050a3b87d25b-image.png" alt="e9fd8b63-c8cd-4d69-ae40-050a3b87d25b-image.png" class=" img-fluid img-markdown" /><br />
<img src="/assets/uploads/files/1616818661169-d0f7b6c5-de7c-4485-b01d-741cae182311-image.png" alt="d0f7b6c5-de7c-4485-b01d-741cae182311-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">What am I doing wrong?</p>
]]></description><link>https://forum.netgate.com/topic/162462/sg-5100-multi-wan-setup</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 02:09:49 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/162462.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 27 Mar 2021 04:02:39 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to SG-5100 Multi-Wan Setup on Sat, 08 May 2021 14:26:04 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nickf1227">@<bdi>nickf1227</bdi></a> Wanted to give you an update.  I was able to resolve the issue by hard coding the gateway IP monitor address to 8.8.8.8.  Starlink is working great on my SG-1100 now.</p>
]]></description><link>https://forum.netgate.com/post/982031</link><guid isPermaLink="true">https://forum.netgate.com/post/982031</guid><dc:creator><![CDATA[chief764]]></dc:creator><pubDate>Sat, 08 May 2021 14:26:04 GMT</pubDate></item><item><title><![CDATA[Reply to SG-5100 Multi-Wan Setup on Fri, 07 May 2021 13:58:38 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nickf1227">@<bdi>nickf1227</bdi></a> Thanks for your reply.  You have gone above and beyond what I am capable of doing right now.  My course of action will be to work with Netgate support and see if they can help solve it.  If it works out I will be sure to report back.  Thanks again for taking the time to respond to my post.</p>
]]></description><link>https://forum.netgate.com/post/981893</link><guid isPermaLink="true">https://forum.netgate.com/post/981893</guid><dc:creator><![CDATA[chief764]]></dc:creator><pubDate>Fri, 07 May 2021 13:58:38 GMT</pubDate></item><item><title><![CDATA[Reply to SG-5100 Multi-Wan Setup on Fri, 07 May 2021 00:55:03 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/chief764">@<bdi>chief764</bdi></a> I ended up virtualizing a second pfsense box to solve the problem. I created a L3 link between each of the two pfsense boxes. On the SG-5100 the second pfsense box is a secondary gateway. I think the problem was that both ISPs were DHCP and were advertising themselves as a route to 0.0.0.0/0.</p>
<p dir="auto">You can then use the existing failover mechanisms in pfsense. If the internet connection dies on your default gateway, the failover algorithm will send the traffic through the first router and out to to the other router to get to the internet. If you are using static routing only, you will have WAN redundancy, but not firewall redundancy, and you will actually need two working firewalls to keep both connections usable. You will also need to make sure you properly write the firewall rules between each to allow for this.</p>
<p dir="auto">I also implemented OSPF in conjunction with the failover settings in pfsense in my environment. I was super annoyed by this problem, so I went all in snd I'm also using dynamic routing with the frr package.</p>
<p dir="auto">My internal network is area 0, the l3 link to my sg-5100 is area 1, the l3 link to my virtualized pfsense box is are 2 and the link between the two pfsense boxes is are 3.</p>
<p dir="auto">This yielded the best results for me, and my internal network can route to either the virtualized box or the sg-5100 and out to either connection.</p>
<p dir="auto">The extra connection between the two firewalls helps eliminate issues, so I wouldn't skip that step. When the SG-5100s connection to my cable ISP was down it was still advertising itself as the default route in OSPF sometimes. By introducing that extra l3 link in conjunction with the wan failover settings in pfsense,  it can still be the default gateway if it wants to be. I also weighted the area links so that my network prefers the sg-5100 and will only route out of the other pfsense box if there is a failure. You don't have to do this, and you can dynamically route your traffic through both at the same time of you want. Just be careful with the asymmetric routing problems that may arise.</p>
<p dir="auto">I hope that's helpful</p>
]]></description><link>https://forum.netgate.com/post/981818</link><guid isPermaLink="true">https://forum.netgate.com/post/981818</guid><dc:creator><![CDATA[nickf1227]]></dc:creator><pubDate>Fri, 07 May 2021 00:55:03 GMT</pubDate></item><item><title><![CDATA[Reply to SG-5100 Multi-Wan Setup on Thu, 06 May 2021 23:05:00 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nickf1227">@<bdi>nickf1227</bdi></a> I'm having the same problem when I plug Starlink into the SG-1100.  I followed a guide posted on Reddit but it is a no go.  Did you ever solve this?</p>
]]></description><link>https://forum.netgate.com/post/981811</link><guid isPermaLink="true">https://forum.netgate.com/post/981811</guid><dc:creator><![CDATA[chief764]]></dc:creator><pubDate>Thu, 06 May 2021 23:05:00 GMT</pubDate></item></channel></rss>