OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of lzamel »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - lzamel

Pages: [1]
1
23.1 Legacy Series / Re: dpinger Needs Frequent Manual Restarts - Multi-WAN
« on: March 07, 2023, 09:15:36 am »
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.

2
20.1 Legacy Series / Re: MultiWAN and BIND DNSBL
« on: July 13, 2020, 08:44:36 pm »
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.

3
20.1 Legacy Series / Re: MultiWAN and BIND DNSBL
« on: July 10, 2020, 05:56:36 pm »
Is there a way to push this traffic thru firewall?

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

4
20.1 Legacy Series / MultiWAN and BIND DNSBL
« on: July 10, 2020, 05:24:43 pm »
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.

5
19.1 Legacy Series / Re: WAN Link Cycling Up and Down
« on: March 05, 2019, 05:46:47 pm »
Quote from: Antaris on March 04, 2019, 08:12:40 pm
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

6
19.1 Legacy Series / Re: WAN Link Cycling Up and Down
« on: March 04, 2019, 07:43:32 am »
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.

7
19.1 Legacy Series / Re: NAT Reflection
« on: March 03, 2019, 12:51:29 pm »
Was this working before (pre 19.01)?

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2