Post by: missionleben on March 27, 2017, 08:58:34 am
Habe ein Problem mit PPPOE auf ein Draytek 130 und Opnsense 17.1.4.
Nach der automatischen 24 Stunden Trennung bei einen VDSL Anschluss wird der PPPOE Stack scheinbar manchmal nicht richtig Initialisiert. Hier mal zwei Beispiele. 24.3 hat funktioniert 25.3. nicht:
Mar 24 15:17:40 MLS-LANGEN-FW01 configd.py: [5dfb56a4-fed3-40bb-abb9-ee22c86bf08b] Rewriting resolv.conf
Mar 24 15:17:40 MLS-LANGEN-FW01 configd.py: [ec58981d-472e-476d-aec9-01ad87da00f7] Rewriting resolv.conf
Mar 24 15:17:44 MLS-LANGEN-FW01 configd.py: [da5ee089-f119-4cd7-adda-4b00c24ecbb5] Rewriting resolv.conf
Mar 24 15:17:46 MLS-LANGEN-FW01 configd.py: [04e33444-3949-41fa-836a-eb479ae0c953] rc.newwanip starting pppoe0
Mar 24 15:17:46 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Mar 24 15:17:46 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for INTERNET[opt1]
Mar 24 15:17:46 MLS-LANGEN-FW01 configd.py: [8b7e92e1-d41b-4c44-b926-0e59825422ad] Rewriting resolv.conf
Mar 24 15:17:47 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host 8.8.8.8' returned exit code '1', the output was 'route: route has not been found delete host 8.8.8.8 fib 0: not in ta
ble'
Mar 24 15:17:47 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host 8.8.4.4' returned exit code '1', the output was 'route: route has not been found delete host 8.8.4.4 fib 0: not in ta
ble'
Mar 24 15:17:48 MLS-LANGEN-FW01 configd.py: [6ce49bb5-4a2f-448b-ab47-4fdd06948633] rc.newwanip starting pppoe0
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: Informational is starting pppoe0.
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 94.46.95.102) (interface: INTERNET[opt1]) (real interface: pppoe0).
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 213.157.2.13
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Removing static route for monitor 8.8.8.8
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Adding static route for monitor through 213.157.2.13
Mar 24 15:17:48 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface INTERNET.
Mar 24 15:17:49 MLS-LANGEN-FW01 kernel: ovpnc1: link state changed to DOWN
Mar 24 15:17:49 MLS-LANGEN-FW01 configd.py: [703cb056-3c89-43b6-91a2-8e9309fdb428] Reloading filter
Mar 24 15:17:51 MLS-LANGEN-FW01 configd.py: [693542d5-7797-4f2d-805e-050934ec2a1e] Reloading filter
Mar 24 15:17:51 MLS-LANGEN-FW01 kernel: ovpnc1: link state changed to UP
Mar 24 15:17:51 MLS-LANGEN-FW01 configd.py: [e54aa7d5-68e4-4a4a-b239-2cea8b0b56fb] rc.newwanip starting ovpnc1
Mar 24 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: Informational is starting ovpnc1.
Mar 24 15:17:52 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Interface is empty, nothing to do.
Mar 24 15:17:54 MLS-LANGEN-FW01 snmpd[68197]: disk_OS_get_disks: adding device 'cd0' to device list
Mar 24 15:17:54 MLS-LANGEN-FW01 devd: notify_clients: send() failed; dropping unresponsive client
Mar 24 15:17:54 MLS-LANGEN-FW01 snmpd[68197]: disk_OS_get_disks: adding device 'vtbd0' to device list
----------------------------------------------------------------------------------------------------
Mar 25 15:17:45 MLS-LANGEN-FW01 configd.py: [6ec4fae6-1008-4db7-af3b-6c2145de2d23] Rewriting resolv.conf
Mar 25 15:17:46 MLS-LANGEN-FW01 configd.py: [0e573053-2f2d-477d-9bc9-3a253180dd17] Rewriting resolv.conf
Mar 25 15:17:49 MLS-LANGEN-FW01 configd.py: [19ef49ad-f918-434a-8715-843c26cfb575] Rewriting resolv.conf
Mar 25 15:17:49 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host 8.8.8.8' returned exit code '1', the output was 'route: route has not been found delete host 8.8.8.8 fib 0: not in ta
ble'
Mar 25 15:17:49 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.resolv_conf_generate: The command '/sbin/route delete -host 8.8.4.4' returned exit code '1', the output was 'route: route has not been found delete host 8.8.4.4 fib 0: not in ta
ble'
Mar 25 15:17:50 MLS-LANGEN-FW01 configd.py: [8a214343-2d00-4e10-a644-3d8646ca53b4] rc.newwanip starting pppoe0
Mar 25 15:17:50 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: Informational is starting pppoe0.
Mar 25 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: on (IP address: 94.46.95.102) (interface: INTERNET[opt1]) (real interface: pppoe0).
Mar 25 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 213.157.2.14
Mar 25 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Removing static route for monitor 8.8.8.8
Mar 25 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Adding static route for monitor through 213.157.2.14
Mar 25 15:17:51 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface INTERNET.
Mar 25 15:17:51 MLS-LANGEN-FW01 kernel: ovpnc1: link state changed to DOWN
Mar 25 15:17:51 MLS-LANGEN-FW01 configd.py: [3a1ee33f-49d0-4371-b5a9-2af1e9cc7e94] Reloading filter
Mar 25 15:17:54 MLS-LANGEN-FW01 configd.py: [b14ecf00-1b4c-4f80-819f-f868d1da7e1d] Reloading filter
Mar 25 15:17:54 MLS-LANGEN-FW01 kernel: ovpnc1: link state changed to UP
Mar 25 15:17:54 MLS-LANGEN-FW01 configd.py: [bb21d48e-497a-483b-921d-075c49fbf9a6] rc.newwanip starting ovpnc1
Mar 25 15:17:54 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: Informational is starting ovpnc1.
Mar 25 15:17:54 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanip: Interface is empty, nothing to do.
Mar 25 15:17:57 MLS-LANGEN-FW01 snmpd[15436]: disk_OS_get_disks: adding device 'cd0' to device list
Mar 25 15:17:57 MLS-LANGEN-FW01 devd: notify_clients: send() failed; dropping unresponsive client
Mar 25 15:17:57 MLS-LANGEN-FW01 snmpd[15436]: disk_OS_get_disks: adding device 'vtbd0' to device list
Mar 25 15:17:59 MLS-LANGEN-FW01 configd.py: [c8f451fb-af61-4802-a0d7-1225dfd16c2d] Rewriting resolv.conf
Mar 25 15:18:00 MLS-LANGEN-FW01 configd.py: [76de148b-51f3-4d85-9f86-f3bc21c924ed] rc.newwanip starting pppoe0
Mar 25 15:18:00 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Mar 25 15:18:00 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for INTERNET[opt1]
Mar 25 15:18:01 MLS-LANGEN-FW01 configd.py: [dce8623d-2b33-4954-b3e1-ebcea976374e] Rewriting resolv.conf
Mar 25 15:18:01 MLS-LANGEN-FW01 configd.py: [95b893ff-4e1a-4a6b-ab88-5db4d79fad6a] Rewriting resolv.conf
Mar 25 15:18:03 MLS-LANGEN-FW01 configd.py: [4589666d-4fe5-41e6-b1df-bf21cc343aca] rc.newwanip starting pppoe0
Mar 25 15:18:03 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Mar 25 15:18:03 MLS-LANGEN-FW01 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for INTERNET[opt1]
Was könnte der Fehler sein?
Post by: blubern on March 29, 2017, 01:10:39 am
Also dann wird aufgebaut und nach 1-2 Minuten ein reconnect gemacht.
Bei mir taucht im log dann zum Zeitpunkt des reconnects das auf:
Mar 29 00:51:19 kernel: 500:2d::d,21222,53,36
Mar 29 00:51:19 syslogd: kernel boot file is /boot/kernel/kernel
Die Zahlen => Kernel: <zahlen> ändern sich
Post by: blubern on March 31, 2017, 12:59:11 pm
opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for WAN[wan]
Nach dieser Zeile fängt die Box wieder an sich neu zu verbinden.
Allerdings in meiner WAN Konfiguration steht bei IPv4 => PPPoE und bei IPv6 => None
Jemand eine Idee? Ist das ein Bug?
Auszug aus dem Log:
Mar 31 01:22:59 opnsense: /usr/local/etc/rc.newwanip: rc.newwanip: Informational is starting pppoe0.
Mar 31 01:22:58 configd.py: [ca06934b-c846-46f5-82a4-288b50092d9d] rc.newwanip starting pppoe0
Mar 31 01:22:58 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Failed to detect IPv6 for WAN[wan]
Mar 31 01:22:57 opnsense: /usr/local/etc/rc.newwanipv6: rc.newwanipv6: Informational is starting pppoe0.
Mar 31 01:22:57 configd.py: [7748d404-3b9c-4bb4-96d2-e23a85153913] rc.newwanip starting pppoe0
Mar 31 01:22:52 configd.py: [37f26013-69b4-40b0-aaaf-916bf0dbe74b] Rewriting resolv.conf
Mar 31 01:22:52 configd.py: [2d792e60-962c-4d1b-beb2-98df60fec075] Rewriting resolv.conf
Mar 31 01:11:02 opnsense: /usr/local/etc/rc.dyndns.update: Dynamic DNS: (Success) IP Address Updated Successfully!
Mar 31 01:11:02 opnsense: /usr/local/etc/rc.dyndns.update: Dynamic DNS: updating cache file /conf/dyndns_wancustom'XXXXXXXXXXXXXXXXXXXX'0.cache: XX.XX.XXX.XXX
Post by: missionleben on March 31, 2017, 02:46:34 pm
Post by: blubern on April 01, 2017, 11:52:40 am
Mein Workarround ist momentan die Box per cron alle 12 stunden neu zu starten.
Der periodic interface reset auf dem wan interface führt übrigens zu dem selben verhalten. Also sobald ich wan down und up mache habe ich eine endlos schleife mit verbunden - trennen - verbinden ....
Gibt es so was wie ein Trace Möglichkeit?
Soll ich mal ins Englische Forum posten?
Wäre für jede Hilfe dankbar.
Post by: missionleben on April 02, 2017, 11:48:29 pm
Das ist leider auch mein Workarround
kann aber irgendwie nicht die Endlösung sein....Gesendet von meinem Nexus 6P mit Tapatalk
Post by: blubern on April 25, 2017, 08:18:45 pm
Schritt für Schritt und immer wieder geschaut ob pppoe geht oder nicht.
Der Moment ab wann PPPOE nicht mehr geht bzw. dieses verhalten aufweißt ist wenn eine OpenVPN Verbindung eingerichtet wird auf dem WAN Interface.
Post by: franco on April 26, 2017, 08:55:00 am
https://github.com/opnsense/core/commit/de1e979f217053254ebea278ef0c4eea89b7c06f
Die Skripte werden gerade überarbeitet, allerdings ist das Testing der verschiedenen WAN-Anbindungen auf Grund der Vielschichtigkeit mühsam und Fehleranfällig. Vielleicht schaffen wir es bis 17.7 hier reinen Tisch zu machen.
Grüsse
Franco