Messages

1

General Discussion / New dashboard: better gateways widget would be appreciated

« on: November 05, 2024, 01:42:26 pm »

Hello!

New dash is nice, and will no doubt improve over time. Here's a partial snap on my setup.

Maybe the next version of 'Gateways' widget showed:
 - which gateways are currently 'active' (ref. multi-wan, gateway switching)
 - some indicator on how many states/sessions or amount of traffic per gateway (ref multi-wan, round-robin)

Thanks.

2

20.1 Legacy Series / Multi-wan, default gw, traffic from this firewall

« on: March 27, 2020, 10:18:01 am »

Hello!

I have multi-wan setup with igb0 and igb2 as the upstream interfaces. Default gw is automatically switched between these two and all traffic from igb1, igb3 and igb4 is load-balanced out via gateway group called internet.

As igb0 and igb2 both have dynamic IP addresses, I am trying to get dyndns to update them to my domain but it seems the curl request gets routed out via default gateway, regardless of --interface and --dns-interface parameters. My dyndns service expects the update request to originate from the ip address mentioned in the update request.

Any hints on how to fix this?

3

19.1 Legacy Series / Here's a fix for DynDNS EuroDNS for Multi-WAN setups

« on: June 14, 2019, 10:52:58 am »

Hello!

Had to add the --interface option for curl to get EuroDNS working on my Multi-WAN setup. See red bolded below.

            case 'eurodns':
                curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
                curl_setopt($ch, CURLOPT_USERPWD, $this->_dnsUser.':'.$this->_dnsPass);
                curl_setopt($ch, CURLOPT_INTERFACE, $this->_dnsIP);
                $server = "https://update.eurodyndns.org/update/";
                $port = "";
                if ($this->_dnsPort) {
                    $port = ":" . $this->_dnsPort;
                }
                curl_setopt($ch, CURLOPT_URL, $server .$port . '?hostname=' . $this->_dnsHost . '&myip=' . $this->_dnsIP);
                break;

4

17.7 Legacy Series / Re: Default gateway address 0.0.0.0 (no, I don't mean 0.0.0.0/0)

« on: September 09, 2017, 06:03:43 pm »

I've been reading more and it seems Windows and Linux can handle the 0.0.0.0 gateway faalback that OpenBSD (and OpnSense), it seems, cannot.

5

17.7 Legacy Series / Default gateway address 0.0.0.0 (no, I don't mean 0.0.0.0/0)

« on: September 03, 2017, 06:54:25 pm »

Hello!

I have a setup with two D-Link DWR-921 4G modems for multi-wan. I run them in "transparent proxy" mode to get my public IPs through to OpnSense. For this setup to work, I need to go in using ssh console and manually edit /conf/config.xml in order to set the gateway address for both modems to 0.0.0.0.

Don't really know the history of this, but apparently this is ok as per IPv4: "In the Internet Protocol version 4 the address 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown or non applicable target. To give a special meaning to an otherwise invalid piece of data is an application of in-band signaling." (see this: https://unix.stackexchange.com/questions/94018/what-is-the-meaning-of-0-0-0-0-as-a-gateway)

Of course I would not use this, but D-Link has chosen to implement their "transparent proxy" in a quirky way: it only passes the (DHCP) WAN IP address to OpnSense, not the WAN GW IP. So as a result, I have two WAN interfaces with gateway address 0.0.0.0 (which is fine by IPv4 I guess). This plays havok on multi-wan and gateway monitoring, perhaps the Dynamic DNS as well. The GUI cannot handle this situation either.

Would you guys consider working your magic to fix this? I can provide whatever log files you desire