OPNsense Forum
Archive => 19.7 Legacy Series => Topic started by: Bytechanger on May 23, 2019, 06:16:45 am
-
Hi,
since last Update my DynamicDNS doesn´t update!
My OPNsense is connected to an vigor 130 modem in bridge modus.
I think, before update it works fine.
Now only pushing "Save and Force Update" works for me and the numbers went green.
I also tested an cron job, but this doesn´t work also.
In Interfaces->Overview->WAN->IPv4 address it´s shown correctly.
Logfile in Time of cutting PPOE:
May 23 04:00:07 opnsense-devel: /usr/local/etc/rc.newwanipv6: Failed to detect IP for WAN[wan]
May 23 04:00:07 opnsense-devel: /usr/local/etc/rc.newwanipv6: On (IP address: ) (interface: WAN[wan]) (real interface: pppoe0).
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: The Raspberry_Pi monitor address is empty, skipping.
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: The WAN_PPPOE monitor address is empty, skipping.
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: The GW_LAN monitor address is empty, skipping.
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: creating /tmp/pppoe0_defaultgw using '62.155.XXX.XXX'
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: removing /tmp/pppoe0_defaultgw
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 62.155.XXX.XXX
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: IPv4 default gateway set to wan
May 23 04:00:06 opnsense-devel: /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
May 23 04:00:05 opnsense-devel: /usr/local/etc/rc.newwanip: On (IP address: 87.148.XXX.XXX) (interface: WAN[wan]) (real interface: pppoe0).
May 23 04:00:05 opnsense-devel: /usr/local/etc/rc.newwanip: IP renewal is starting on 'pppoe0'
May 23 04:00:05 kernel: ng0: changing name to 'pppoe0'
May 23 04:00:01 ppp-linkdown: Removing stale PPPoE gateway fe80::XXXX:XXXX:XXXX:XXXX%pppoe0 on inet6
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: Warning! dhcpd_dhcp4_configure() found no suitable IPv4 address on opt2
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: Warning! dhcpd_dhcp4_configure() found no suitable IPv4 address on opt1
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: creating /tmp/pppoe0_defaultgwv6 using 'fe80::XXXX:XXXX:XXXX:XXXX%pppoe0'
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: removing /tmp/pppoe0_defaultgwv6
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: setting IPv6 default route to XXXX::XXXX:XXXX:XXXX:XXXX
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: IPv6 default gateway set to wan
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: skipping IPv4 default route
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: IPv4 default gateway set to lan
May 23 04:00:01 opnsense-devel: /usr/local/etc/rc.configure_interface: ROUTING: entering configure using 'wan'
May 23 04:00:00 kernel: vlan1: changing name to 're1_vlan50'
May 23 04:00:00 kernel: vlan0: changing name to 're1_vlan100'
Every 10 Minutes after full hour, where my cron runs:
May 23 05:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (home.biegner.org) There was an error trying to determine the public IP for interface - opt1(re1_vlan100). Probably interface is not a WAN interface.
May 23 05:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (xxx.xxx.xx): running dyndns_failover_interface for wan. found pppoe0
May 23 05:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (xxx.xxx.xx): IP address could not be extracted
May 23 05:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Aborted IPv4 detection: no address for re1_vlan100
May 23 05:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS: updatedns() starting
May 23 04:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (xxx.xx.xxx) There was an error trying to determine the public IP for interface - opt1(re1_vlan100). Probably interface is not a WAN interface.
May 23 04:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (xxx.xx.xxx): running dyndns_failover_interface for wan. found pppoe0
May 23 04:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS (xxx.xx.xxx): IP address could not be extracted
May 23 04:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Aborted IPv4 detection: no address for re1_vlan100
May 23 04:10:00 opnsense-devel: /usr/local/etc/rc.dyndns: Dynamic DNS: updatedns() starting
I need any help.
Greets
Byte
-
Oh in Reporter there was an error to report:
[23-May-2019 04:00:02 Europe/Berlin] PHP Fatal error: Uncaught Error: Call to undefined function lookup_gateway_interface_by_name() in /usr/local/etc/rc.dyndns:46
Stack trace:
#0 {main}
thrown in /usr/local/etc/rc.dyndns on line 46
-
You are using the development version of OPNsense. Install the development version of os-dyndns as well to fix this :)
-
OK, I need develop, because I´m using Wireguard.
But you mean, the bug is known, so at the next update it´s fixed?
Greets
Byte
-
There is no bug. 19.7 has a few code changes coming up that are not on 19.1 and you have a mixed env with code from 19.7 and plugins from 19.1....
Cheers,
Franco
-
Hi,
thanks for fast answerinig.
I´am a newbie and DynDNS was installed by default.
I only change update channel.
At this time os-dyndns (installed) 1.15 is installed.
Can I solve this problem by changing anything?
What should I change? Can I change Plugins to devolop channel also?
(by the way, there is an additional plugin: os-dyndns-devel 1.15_2 ).
EDIT:
OK, I think, -devel Plugins are for the developer-versions. Right?
I will install it now.
Greets
Byte
-
Yes, exactly. Development mode changes "opnsense" package to "opnsense-devel". It is the same for plugins so os-dyndns-devel indeed. os-dyndns will be removed in the process. However, we don't automatically change plugin packages for the user... probably more a historic oddity than any particular reason.
Development and release are mostly the same, but 19.7 introduces a few core changes that require plugins to follow. This happened over the years a few times. Friction is pretty low, but it's there when it is so here we are. :)
Cheers,
Franco