OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • WAN re-negotiation fails on daily forced separation
« previous next »
  • Print
Pages: [1]

Author Topic: WAN re-negotiation fails on daily forced separation  (Read 2124 times)

kug1977

  • Newbie
  • *
  • Posts: 29
  • Karma: 4
    • View Profile
WAN re-negotiation fails on daily forced separation
« on: February 03, 2018, 04:32:43 pm »
Hi,

I've an APU1 board for OPNsense 18.1.1 and on port 0 works a Vigor 130 as VDSL modem. The Interface is configured as IPv4 / PPPoE and IPv6 / DHCPv6. I have enabled "Block private networks" and "Block bogon networks". Only username and password is set.

On a restart, the WAN come up and work probably. But it will not survive the daily forced separation and stay in interface overview than with status "up", but no network is working. It need a restart to work again. It stopped working after the upgrade to 17.7.11. 17.7.10 was working fine.

I can see in the logs at this time the following entries in /var/log/ppps.log. What is different between  re-negotiation and restart is the entry Feb  3 15:35:31 fw2 ppp: caught fatal signal TERM.

Any idea, why the re-negotiation is failing?

Kind regards,
Kay-Uwe
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13679
  • Karma: 1176
    • View Profile
Re: WAN re-negotiation fails on daily forced separation
« Reply #1 on: February 05, 2018, 08:53:36 am »
Maybe this... https://github.com/opnsense/core/commit/f09eaf7f3a

It was added to 18.1.2, but the impact is unclear because that is the behaviour since at least 17.1.


Cheers,
Franco
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 18.1 Legacy Series »
  • WAN re-negotiation fails on daily forced separation
 

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