<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I see <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">1.1.1.225 is configured on eth1 as well though.</span><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">That should not be.</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font color="#000000">I think that is why the default gateway is also “attached” to eth1.</font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">1.1.1.225 0.0.0.0 255.255.255.255 UH 101 0 0 eth1<br></blockquote></blockquote></blockquote></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br id="lineBreakAtBeginningOfMessage"></span></font><div><br><blockquote type="cite"><div>On 7 Dec 2023, at 14:33, Darren Wolfe via Blueonyx <blueonyx@mail.blueonyx.it> wrote:</div><br class="Apple-interchange-newline"><div><div>Hi,<br><br>I've adjusted for privacies sake, but the last octet is unchanged so the netmasks and network ranges make sense<br><br>eth0 (public interface): 1.1.1.238, netmask 255.255.255.224<br>Gateway address is 1.1.1.225<br><br>eth1 (private interface): 192.168.17.18, netmask 255.255.255.0<br>No gateway address or any other routes needed, this is used as a simple DMZ<br><br><br><br><blockquote type="cite">-----Original Message-----<br>From: Taco Scargo <taco@blueonyx.nl><br>Sent: Thursday, December 7, 2023 8:35 AM<br>To: Darren Wolfe <darren@intersys-group.com>; BlueOnyx General Mailing List<br><blueonyx@mail.blueonyx.it><br>Subject: Re: [BlueOnyx:26639] Interfaces and default routes<br><br>Darren,<br><br>Would you be so kind to share the IP addresses of the interfaces?<br>Because the routing table does not make sense at all and it almost seems that<br>both interfaces share the same network address space, which you should never<br>do.<br><br>Thanks,<br><br>Taco<br><br><blockquote type="cite">On 7 Dec 2023, at 00:44, Darren Wolfe via Blueonyx<br></blockquote><blueonyx@mail.blueonyx.it> wrote:<br><blockquote type="cite"><br>Hi,<br><br><blockquote type="cite">Indeed, the IPv6 autoconf=no should be set. I'll see to it.<br></blockquote><br>Thank you!<br><br><blockquote type="cite">As for the default gateway? In my understanding there should be only one<br>default gateway and that should apply to all interfaces. There may be<br>additional routes that direct traffic destined for an internal network<br>to the interface that the internal network is connected to. Or if<br>OpenVPN is present, there ought to be a route that allows traffic to be<br>directed to the private network that OpenVPN clients use.<br><br>But there shouldn't be two default gateways.<br></blockquote><br><br>I shouldn't have confused the issue by mentioning two public default routes, but<br></blockquote>the idea that the default gateway should apply to all interfaces is an assumption<br>that does not always hold. In my case, the public-facing interface has a public IP<br>address as one would expect, but there is a DMZ network on a different interface<br>and private address range which should not have the same default route applied<br>to it.<br><blockquote type="cite"><br>I may be misinterpreting what I see on the boxes which is that when the server<br></blockquote>is rebooted. This is how it looks:<br><blockquote type="cite">eth0 is the public interface, eth1 is the private (ip's have been changed)<br><br>Destination Gateway Genmask Flags Metric Ref Use Iface<br>0.0.0.0 1.1.1.225 0.0.0.0 UG 100 0 0 eth0<br>0.0.0.0 1.1.1.225 0.0.0.0 UG 101 0 0 eth1<br>1.1.1.224 0.0.0.0 255.255.255.224 U 100 0 0 eth0<br>1.1.1.225 0.0.0.0 255.255.255.255 UH 101 0 0 eth1<br>192.168.17.0 0.0.0.0 255.255.255.0 U 101 0 0 eth1<br><br>I don't know what that 4th rule is attempting to do..<br><br>Sometimes eth1 will get the lower route metric, which results in no network<br></blockquote>connectivity. Even like the above, active monitor says:<br><blockquote type="cite">The network interface eth0 is down. The network interface eth1 is down.<br><br>If the incorrect routes - the 2nd and 4th in the above, are removed, all is well.<br><br><br><br><br>_______________________________________________<br>Blueonyx mailing list<br>Blueonyx@mail.blueonyx.it<br>http://mail.blueonyx.it/mailman/listinfo/blueonyx<br></blockquote></blockquote><br><br>_______________________________________________<br>Blueonyx mailing list<br>Blueonyx@mail.blueonyx.it<br>http://mail.blueonyx.it/mailman/listinfo/blueonyx<br></div></div></blockquote></div><br></div></body></html>