OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 16.1 Legacy Series »
  • [SOLVED] pppoe + unbound
« previous next »
  • Print
Pages: [1]

Author Topic: [SOLVED] pppoe + unbound  (Read 3958 times)

gratis

  • Newbie
  • *
  • Posts: 15
  • Karma: 5
    • View Profile
[SOLVED] pppoe + unbound
« on: April 04, 2016, 11:05:36 am »
I have recently switched internet providers, and have implemented pppoe on OPNsense.  With the internet provider supplied router in bridge mode, once every day or so a new IP address is issued to OPNsense, which creates a new route entry, which causes Unbound to stop working.

Once a day, when the DNS stops resolving, I simply login to OPNsense and restart Unbound, which restores proper operation, but I am wondering if there is some automated way to handle this situation so that no manual intervention is required?
« Last Edit: May 04, 2016, 07:18:53 am by franco »
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13679
  • Karma: 1176
    • View Profile
Re: pppoe + unbound
« Reply #1 on: April 04, 2016, 06:36:55 pm »
This is on 16.1.8? Can you provide the unbound log directly after the incident before restart? PM me if you like.

Thanks!
Logged

gratis

  • Newbie
  • *
  • Posts: 15
  • Karma: 5
    • View Profile
Re: pppoe + unbound
« Reply #2 on: April 05, 2016, 03:01:41 pm »
Just happened, have log. Will send via PM.

And yes, it's 16.1.8.
« Last Edit: April 05, 2016, 04:52:41 pm by gratis »
Logged

pylox

  • Jr. Member
  • **
  • Posts: 50
  • Karma: 7
    • View Profile
    • WbaSec Solutions
Re: pppoe + unbound
« Reply #3 on: May 03, 2016, 06:10:51 pm »
Hi (Franco),

is there any progress on this topic ? - i have the same problem... This is a very annoying "feature". ;)

regards pylox
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13679
  • Karma: 1176
    • View Profile
Re: pppoe + unbound
« Reply #4 on: May 04, 2016, 07:18:40 am »
Yes, we've resolved this with gratis in private conversations. In this case the "outgoing interface" was set to something other than all/any, which has this inherent behaviour with unbound. This is not a bug, it's intentional like DHCP can't run on non-static interfaces. Do not use dynamically configured interfaces as outgoing interfaces.

We still do want to improve the GUI, but there are far more important areas at the moment.

https://github.com/opnsense/core/issues/881
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 16.1 Legacy Series »
  • [SOLVED] pppoe + unbound
 

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