Messages

I was observing similar (if not exactly the same) behavior. It all stopped after I correctly set System: Settings: General: DNS servers
By correct I mean each GW is listed and uses same DNS server as one used to monitor status.
I didn't debug why this helped on my setup, but I haven't seen dpinger stuck since.

I did. Step 5 rule matches LAN traffic, it will not match traffic originating from firewall itself. As there is no way to force it thru PF it cannot be used to modify GW.

Is there a way to push this traffic thru firewall?

(Sorry if I'm asking dumb questions, new to PF.)

Hi all,
I have a working setup using BIND DNSBL and MultiWAN (with one GW at this stage). All works correctly however adding a second GW (same tier) breaks DNS unless I set System -> General -> DNS per GW. Unfortunately, setting those ignores my BIND setup.

Is there some trick I'm missing or do I need to create firewall rule redirecting the hosts from System -> General -> DNS per GW to my BIND. For BIND I use a different set of servers.

L.

I had this issue before more than a year with Linux based firewall IPFire. Was a bad Intel driver with some of the updates of the firewall.

Here is the workaround:

https://forum.ipfire.org/viewtopic.php?f=50&t=17549&p=111842#p111842

Switching off offload was first thing I did. Had no effect. I217-LM is stable. After provider fixes issues on their side will switch back to I340-T4

I have a fresh install of 19.1, running 19.1.2 on HP 800 G1 i3-4130.
Two NICs: I217-LM and I340-T4.

If I put WAN on any of 4 I340-T4 ports it's going down every few hours. Card itself is ok, as LAN and OPTx are stable on it.
WAN on I217-LM is also stable so it's not ONT device.

EDIT: Was happy too early. The I217-LM link is also going down. It just took 9h instead of 3h.
EDIT #2: On second thought on I217-LM link remains up, so it looks like ONT is acting up.

Was this working before (pre 19.01)?