Ad Schellevis

Just had a similar issue, for some reason my routing table changed from : ``` Internet: Destination Gateway Flags Netif Expire default xxx.xxx.xxx.1 UGS igc1 xxx.xxx.xxx.0/24 link#2 U igc1 xxx.xxx.xxx.121...

might be https://github.com/opnsense/core/commit/a230326d7fe165e597cd2d5a30b064e0b3a1c58c as well

@mimugmail what does the routing table look like? mine missed a link, which is why it looked similar to https://github.com/opnsense/core/commit/a230326d7fe165e597cd2d5a30b064e0b3a1c58c (but maybe something completely different)

The cases I have seen relate to missing link addresses in the routing table, `netstat -nr -4` would easily tell you if that's the case. If for some reason the...

what does `route show 8.8.8.8` result into?

ok, that's good, doesn't look like a routing issue then. Next question is about the nat rules, what do they look like: ``` grep '^nat on' /tmp/rules.debug ```

Just to be sure, you are not able to ping 8.8.8.8 from this machine? if that's the case, it's probably a good idea to capture some traffic first. so far...

it might make sense to build a UI to control `at(1)` from OPNsense BE, this ticket https://github.com/opnsense/core/issues/1798 is similar but different scope.

settings->backend : ddclient ?

> Why is this not the default? What a headache. I wasted a solid half-hour on this alone. 😕 long story I'm afraid (project was sunsetting, then it wasn't (sort...