Home
Help
Search
Login
Register
OPNsense Forum
»
International Forums
»
German - Deutsch
»
PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
« previous
next »
Print
Pages:
1
[
2
]
3
Author
Topic: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser? (Read 13662 times)
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #15 on:
January 28, 2018, 10:15:11 pm »
werde ich morgen es machen, ich bin leider nicht zu Hause.
@mimugmail: kannst du mir bitte empfehlen, was ich genau machen soll?. DrayTek mit PPPOE Verbindung, oder Fritzbox mit DHCP? sowieso habe zunächst nur die Fritzbox als Möglichkeit, aber kein Bridge Mode möglich (was ich bis heute wusste). Ist tatsächlich besser direkt an die Internet verbinden, oder ist egal wenn man die OPNsense Box als exposed Host im Fritzbox einstellt?.
Ich kämpfe seit Wochen damit, und bis heute ist das Thema unklar für mich
Logged
mimugmail
Hero Member
Posts: 6767
Karma: 494
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #16 on:
January 29, 2018, 10:21:18 am »
Wenn du dich mit IPSec auf der OPN einwählen willst ist NAT nicht so toll, bei OpenVPN mit exposed host ist es egal. Große Probleme gibts da nicht, schließlich gibts bei LTE ja auch double-nat und die Leute kommen damit klar
IPv6 kann ich nicht beurteilen .. das ist oft vendor abhängig
Logged
WWW:
www.routerperformance.net
Support plans:
https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German):
https://opnsense.max-it.de/
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #17 on:
February 01, 2018, 05:23:14 pm »
@mimugmail: Ich habe mich erkundigt, und die Möglichkeit ein Kabelmodem als Bridge Modem zu nutzen ist verfügbar (z.B. Vodafon)
@mimugmail: System log werde ich zunächst posten in 2 Teilen...
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #18 on:
February 01, 2018, 05:24:58 pm »
Erster Teil: alles funktioniert, Box neu gestartet und alles sieht gut aus:
Jan 29 12:04:19
configd.py: [92646c0f-ee26-427f-b08d-0b967900a0b8] request pfctl byte/packet counters
Jan 29 12:04:05
kernel:
Jan 29 12:04:05
kernel:
Jan 29 12:04:04
kernel:
Jan 29 12:04:04
kernel:
Jan 29 12:04:04
kernel:
Jan 29 12:04:04
kernel:
Jan 29 12:04:03
kernel:
Jan 29 12:04:02
kernel: OK
Jan 29 12:04:02
sshlockout[75049]: sshlockout/webConfigurator v3.0 starting up
Jan 29 12:04:02
configd.py: [ac59fe3c-b2d4-416d-a0e2-004930663280] restarting cron
Jan 29 12:04:00
kernel: load_dn_aqm dn_aqm PIE loaded
Jan 29 12:04:00
kernel: load_dn_aqm dn_aqm CODEL loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched FQ_PIE loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched FQ_CODEL loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched PRIO loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched WF2Q+ loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched RR loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched QFQ loaded
Jan 29 12:04:00
kernel: load_dn_sched dn_sched FIFO loaded
Jan 29 12:04:00
kernel: DUMMYNET 0 with IPv6 initialized (100409)
Jan 29 12:04:00
kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to accept, logging disabled
Jan 29 12:03:56
kernel: done.
Jan 29 12:03:53
root: /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
Jan 29 12:03:53
configd.py: generate template container OPNsense/Syslog
Jan 29 12:03:50
kernel: done.
Jan 29 12:03:50
configd.py: [cc991568-0374-47db-b466-78ec78251dd2] generate template OPNsense/Syslog
Jan 29 12:03:47
kernel: deferred.
Jan 29 12:03:47
kernel: done.
Jan 29 12:03:46
opnsense: /usr/local/etc/rc.bootup: Curl error occurred: bind failed with errno 47: Address family not supported by protocol family
Jan 29 12:03:44
opnsense: /usr/local/etc/rc.bootup: Dynamic DNS: (ERROR!) No Password Provided.
Jan 29 12:03:44
opnsense: /usr/local/etc/rc.bootup: Dynamic DNS: (ERROR!) No Username Provided.
Jan 29 12:03:43
opnsense: /usr/local/etc/rc.bootup: Dynamic DNS: (Success) IP Address Updated Successfully!
Jan 29 12:03:43
opnsense: /usr/local/etc/rc.bootup: Dynamic DNS: updating cache file /var/cache/dyndns_wan_myownspace_0.cache: 87.122.2.48
Jan 29 12:03:41
configd.py: generate template container OPNsense/WebGui
Jan 29 12:03:40
configd.py: generate template container OPNsense/Syslog
Jan 29 12:03:40
configd.py: generate template container OPNsense/Sample/sub2
Jan 29 12:03:39
configd.py: generate template container OPNsense/Sample/sub1
Jan 29 12:03:39
configd.py: generate template container OPNsense/Sample
Jan 29 12:03:32
configd.py: generate template container OPNsense/Proxy
Jan 29 12:03:29
configd.py: generate template container OPNsense/Netflow
Jan 29 12:03:29
configd.py: generate template container OPNsense/Macros
Jan 29 12:03:27
configd.py: generate template container OPNsense/IPFW
Jan 29 12:03:22
configd.py: generate template container OPNsense/IDS
Jan 29 12:03:22
configd.py: generate template container OPNsense/Cron
Jan 29 12:03:20
configd.py: generate template container OPNsense/Captiveportal
Jan 29 12:03:18
configd.py: generate template container OPNsense/Auth
Jan 29 12:03:15
kernel: done.
Jan 29 12:03:15
configd.py: [c9d7bbb8-7374-407d-9a36-13b3034bbf5c] generate template *
Jan 29 12:03:15
kernel: .
Jan 29 12:03:13
kernel: .
Jan 29 12:03:13
kernel: ..
Jan 29 12:03:09
kernel: done.
Jan 29 12:03:08
configd.py: [33aeed92-6344-414e-9e2f-b362925459d5] request pfctl byte/packet counters
Jan 29 12:03:05
kernel: done.
Jan 29 12:03:03
kernel: done.
Jan 29 12:03:02
kernel: done.
Jan 29 12:03:01
configd.py: [b7f258c1-59a6-4d10-958f-15629605844c] request pfctl byte/packet counters
Jan 29 12:02:54
kernel: done.
Jan 29 12:02:54
opnsense: /usr/local/etc/rc.bootup: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:02:54
kernel: done.
Jan 29 12:02:54
opnsense: /usr/local/etc/rc.bootup: ROUTING: setting IPv4 default route to 62.214.63.85
Jan 29 12:02:54
lighttpd[20671]: (server.c.1412) server started (lighttpd/1.4.48)
Jan 29 12:02:53
configd.py: generate template container OPNsense/WebGui
Jan 29 12:02:50
configd.py: [d315836a-6170-4f14-b0de-55072c3bbfc2] generate template OPNsense/WebGui
Jan 29 12:02:50
sshd[19865]: Server listening on 0.0.0.0 port 22.
Jan 29 12:02:50
sshd[19865]: Server listening on :: port 22.
Jan 29 12:02:50
kernel: done.
Jan 29 12:02:50
kernel: done.
Jan 29 12:02:50
kernel: .
Jan 29 12:02:48
kernel: ...
Jan 29 12:02:47
configd.py: [29591dcf-9fb4-4825-a39e-4878733e36ae] Linkup starting igb1_vlan9
Jan 29 12:02:46
kernel: pflog0: promiscuous mode enabled
Jan 29 12:02:46
configd.py: [16f80754-4f9e-4942-87d2-bbdc26ea2a6d] Linkup starting igb1_vlan8
Jan 29 12:02:46
configd.py: [8af9e727-2c51-4423-95ec-cd14dcadd10d] Linkup starting igb1_vlan6
Jan 29 12:02:45
configd.py: [9f3d2234-38c0-43ae-b6f1-ca4d02f6542a] Linkup starting igb1_vlan5
Jan 29 12:02:45
configd.py: [2dd307b6-d950-45e6-a621-fbee02b4a4f0] New IPv6 on pppoe0
Jan 29 12:02:44
configd.py: [eeec59cf-5a5c-4dae-af2f-2a51290350ac] Linkup starting igb1_vlan4
Jan 29 12:02:44
configd.py: [b79c719d-870f-46f1-bbcf-e76c67473f62] New IPv4 on pppoe0
Jan 29 12:02:44
configd.py: [f9e2c1ce-e5ad-48f6-a12b-acd82cb1ba6a] Linkup starting igb1
Jan 29 12:02:44
kernel: igb1_vlan9: link state changed to UP
Jan 29 12:02:44
kernel: igb1_vlan8: link state changed to UP
Jan 29 12:02:44
kernel: igb1_vlan6: link state changed to UP
Jan 29 12:02:44
kernel: igb1_vlan5: link state changed to UP
Jan 29 12:02:44
kernel: igb1_vlan4: link state changed to UP
Jan 29 12:02:44
kernel: igb1: link state changed to UP
Jan 29 12:02:44
configd.py: [57021cf6-05df-4825-b262-aa0994fa16e0] New IPv6 on pppoe0
Jan 29 12:02:43
configd.py: [063bd877-5725-45a7-aa62-09afe9122f74] New IPv4 on ovpns3
Jan 29 12:02:42
kernel: ovpns3: link state changed to UP
Jan 29 12:02:42
configd.py: [15b39586-fc87-469c-9055-1fdb9e9b1288] New IPv4 on ovpns2
Jan 29 12:02:42
configd.py: [c8344f25-0560-48a0-bbf0-754bd61deae1] Linkup starting igb0_vlan7
Jan 29 12:02:42
kernel: ovpns2: link state changed to UP
Jan 29 12:02:42
configd.py: [9b3595d4-38c9-40a7-b241-df355a61757e] New IPv4 on ovpns1
Jan 29 12:02:41
kernel: ovpns1: link state changed to UP
Jan 29 12:02:41
kernel: ng_pppoe[14]: no matching session
Jan 29 12:02:41
kernel: ng_pppoe[14]: no matching session
Jan 29 12:02:41
configd.py: [f7546fae-b810-46b5-a259-541921bcb128] Linkup starting igb0
Jan 29 12:02:41
kernel: igb0_vlan7: link state changed to UP
Jan 29 12:02:41
kernel: igb0: link state changed to UP
Jan 29 12:02:41
kernel:
Jan 29 12:02:41
kernel: done.
Jan 29 12:02:41
opnsense: /usr/local/etc/rc.bootup: Resyncing OpenVPN instances.
Jan 29 12:02:40
kernel: done.
Jan 29 12:02:40
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #19 on:
February 01, 2018, 05:30:21 pm »
Zweiter Teil: nach Zwangstrennung, entweder IPv4 oder IPv6 im Wechsel funktionieren nicht mehr, OpenVPN (über WAN zeigt immer weiter diese Message:
RemoteOVPN UDP:1194 Client connections
Name/Time
Real/Virtual IP
[error]
0
Unable to contact daemon
Service not running?
alt_RemoteOVPN TCP:443 Client connections
Name/Time
Real/Virtual IP
[error]
0
Unable to contact daemon
Service not running?
und keine Internet Verbindung möglich.
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #20 on:
February 01, 2018, 05:30:41 pm »
Jetzt System log:
Jan 29 12:14:32
opnsense: /usr/local/etc/rc.newwanip: Curl error occurred: bind failed with errno 47: Address family not supported by protocol family
Jan 29 12:14:29
opnsense: /usr/local/etc/rc.newwanip: Aborted IP detection: Failed to connect to checkipv6.dyndns.org port 80: Operation timed out
Jan 29 12:14:09
configd.py: [5204bf1b-792a-4e0c-8ed3-cfac2208f87e] Reloading filter
Jan 29 12:14:08
opnsense: /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 29 12:14:08
opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:14:08
opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 62.214.63.85
Jan 29 12:14:08
opnsense: /usr/local/etc/rc.newwanip: Accept router advertisements on interface pppoe0
Jan 29 12:14:06
opnsense: /usr/local/etc/rc.newwanip: On (IP address: 89.245.77.211) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:14:06
opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'pppoe0'
Jan 29 12:14:05
configd.py: [01029271-2abd-4e6c-b418-25936a52f7b2] New IPv4 on pppoe0
Jan 29 12:13:40
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:13:40
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:13:40
configd.py: [0e15201b-5d7f-4303-9090-bc5a5ae4d0eb] New IPv6 on pppoe0
Jan 29 12:13:40
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:13:40
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:13:40
configd.py: [0e15201b-5d7f-4303-9090-bc5a5ae4d0eb] New IPv6 on pppoe0
Jan 29 12:13:33
configd.py: [e2867ad6-0857-46f9-9471-995beb34b493] Rewriting resolv.conf
Jan 29 12:13:33
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for interface pppoe0
Jan 29 12:13:32
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for IP fe80::20d:b9ff:fe48:5d64%pppoe0/32
Jan 29 12:13:31
configd.py: [06eb2787-41c3-40e6-9724-0fc1ab70014c] Rewriting resolv.conf
Jan 29 12:13:31
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for interface pppoe0
Jan 29 12:13:31
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for IP 87.122.1.151/32
Jan 29 12:13:27
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:13:27
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:13:27
configd.py: [b6eb9ce9-bb72-4691-9f64-7a86a2ed2ee1] New IPv6 on pppoe0
Jan 29 12:13:22
opnsense: /usr/local/etc/rc.newwanip: Curl error occurred: bind failed with errno 47: Address family not supported by protocol family
Jan 29 12:13:20
opnsense: /usr/local/etc/rc.newwanip: Aborted IP detection: Failed to connect to checkipv6.dyndns.org port 80: Operation timed out
Jan 29 12:13:15
opnsense: /usr/local/etc/rc.newwanip: Dynamic DNS: (ERROR!) No Password Provided.
Jan 29 12:13:15
opnsense: /usr/local/etc/rc.newwanip: Dynamic DNS: (ERROR!) No Username Provided.
Jan 29 12:13:14
opnsense: /usr/local/etc/rc.newwanip: Dynamic DNS: (Success) IP Address Updated Successfully!
Jan 29 12:13:14
opnsense: /usr/local/etc/rc.newwanip: Dynamic DNS: updating cache file /var/cache/dyndns_wan_myownspace_0.cache: 87.122.1.151
Jan 29 12:13:10
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:13:10
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:13:09
configd.py: [40510e10-4e1e-4121-811d-8c946e6b2dfe] New IPv6 on pppoe0
Jan 29 12:13:01
configd.py: [aa5d9333-aae1-4d4f-9dc0-22af942399fa] Reloading filter
Jan 29 12:12:54
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:12:54
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:12:53
configd.py: [fc07c006-f228-400c-8a52-df0e005e98b3] Reloading filter
Jan 29 12:12:53
configd.py: [cff3df2e-9d62-4cc2-a7fc-e347d20faf0c] New IPv6 on pppoe0
Jan 29 12:12:53
opnsense: /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Jan 29 12:12:53
opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:12:53
opnsense: /usr/local/etc/rc.newwanip: ROUTING: setting IPv4 default route to 62.214.63.85
Jan 29 12:12:52
opnsense: /usr/local/etc/rc.newwanip: Accept router advertisements on interface pppoe0
Jan 29 12:12:50
opnsense: /usr/local/etc/rc.newwanip: On (IP address: 87.122.1.151) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:12:50
opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'pppoe0'
Jan 29 12:12:50
configd.py: [00ea5adc-9a9d-4159-9e6c-cff832c2c085] New IPv4 on pppoe0
Jan 29 12:12:47
kernel: dc3::35,6705,53,36
Jan 29 12:12:46
configd.py: unable to sendback response [OK ] for [interface][newipv6][['pppoe0']] {751f8172-f634-4233-ae53-954e6de5f20f}, message was Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 202, in run self.connection.sendall('%s\n' % result) File "/usr/local/lib/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) error: [Errno 32] Broken pipe
Jan 29 12:12:36
kernel: 500:2f::f,14233,53,36
Jan 29 12:12:35
kernel: 500:2d::d,37249,53,36
Jan 29 12:12:35
kernel: dc3::35,63008,53,36
Jan 29 12:12:35
opnsense: /usr/local/etc/rc.newwanipv6: Curl error occurred: Could not resolve host: ipv6.cloudns.net
Jan 29 12:12:28
kernel: 502:1ca1::30,4520,53,54
Jan 29 12:12:28
kernel: 500:200::b,45723,53,52
Jan 29 12:12:27
kernel: 500:2f::f,6185,53,36
Jan 29 12:12:27
kernel: 503:ba3e::2:30,32044,53,36
Jan 29 12:12:27
kernel: 503:c27::2:30,23448,53,36
Jan 29 12:12:27
kernel: 500:a8::e,60732,53,36
Jan 29 12:12:27
kernel: 7fe::53,41214,53,36
Jan 29 12:12:26
kernel: 500:200::b,54127,53,36
Jan 29 12:12:25
configd.py: unable to sendback response [OK ] for [interface][newipv6][['pppoe0']] {0b75430c-9449-4e18-a10c-c5dfc0be447e}, message was Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 202, in run self.connection.sendall('%s\n' % result) File "/usr/local/lib/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) error: [Errno 32] Broken pipe
Jan 29 12:12:24
kernel: 500:2d::d,61956,53,36
Jan 29 12:12:21
opnsense: /usr/local/etc/rc.newwanipv6: Aborted IP detection: Resolving timed out after 5526 milliseconds
Jan 29 12:12:17
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:12:17
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:12:17
configd.py: [4d1ad52b-f730-47b2-a6a8-9d3bed0423b2] New IPv6 on pppoe0
Jan 29 12:12:15
kernel: 7fe::53,10058,53,36
Jan 29 12:12:15
kernel: 500:12::d0d,30743,53,36
Jan 29 12:12:15
kernel: 503:d414::30,44946,53,54
Jan 29 12:12:15
kernel: 500:200::b,39330,53,36
Jan 29 12:12:15
kernel: 500:12::d0d,35161,53,36
Jan 29 12:12:15
kernel: 500:a8::e,58827,53,36
Jan 29 12:12:15
kernel: 7fe::53,42166,53,70
Jan 29 12:12:15
kernel: 7fd::1,4577,53,36
Jan 29 12:12:14
kernel: 500:200::b,65294,53,36
Jan 29 12:12:14
kernel: 503:c27::2:30,5705,53,62
Jan 29 12:12:14
kernel: 500:1::53,28875,53,62
Jan 29 12:12:14
kernel: 500:12::d0d,57637,53,36
Jan 29 12:12:14
kernel: 500:2f::f,5885,53,36
Jan 29 12:12:14
kernel: 500:2d::d,27447,53,36
Jan 29 12:12:14
kernel: 500:200::b,51502,53,36
Jan 29 12:12:13
kernel: 503:ba3e::2:30,49078,53,36
Jan 29 12:12:12
configd_ctl.py: error in configd communication Traceback (most recent call last): File "/usr/local/opnsense/service/configd_ctl.py", line 65, in exec_config_cmd line = sock.recv(65536) timeout: timed out
Jan 29 12:12:11
configd.py: [2f9736e9-7087-4151-ad45-3d835ad20219] Rewriting resolv.conf
Jan 29 12:12:11
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for interface pppoe0
Jan 29 12:12:11
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for IP fe80::20d:b9ff:fe48:5d64%pppoe0/32
Jan 29 12:12:10
configd_ctl.py: error in configd communication Traceback (most recent call last): File "/usr/local/opnsense/service/configd_ctl.py", line 65, in exec_config_cmd line = sock.recv(65536) timeout: timed out
Jan 29 12:11:20
opnsense: /usr/local/etc/rc.newwanipv6: Aborted IP detection: Resolving timed out after 5651 milliseconds
Jan 29 12:11:17
opnsense: /usr/local/etc/rc.newwanipv6: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:11:14
opnsense: /usr/local/etc/rc.newwanipv6: Dynamic DNS: (ERROR!) No Password Provided.
Jan 29 12:11:14
opnsense: /usr/local/etc/rc.newwanipv6: Dynamic DNS: (ERROR!) No Username Provided.
Jan 29 12:11:13
opnsense: /usr/local/etc/rc.newwanipv6: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:11:05
opnsense: /usr/local/etc/rc.newwanip: Interface '' is disabled or empty, nothing to do.
Jan 29 12:11:04
opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'ovpns3'
Jan 29 12:11:04
configd.py: [a49cb36c-b64f-4b4e-b2d1-86f3c6cf70b6] New IPv4 on ovpns3
Jan 29 12:11:04
configd.py: [738311d3-efb0-4907-af8f-3bd033a2aaa3] Reloading filter
Jan 29 12:11:04
kernel: ovpns3: link state changed to UP
Jan 29 12:11:04
configd.py: [a38d33ca-8269-41f7-bbaf-c883aea0dca5] Reloading filter
Jan 29 12:10:54
configd.py: [492955e2-5ba7-4c3d-ae20-8f57f7eb1602] Reloading filter
Jan 29 12:10:54
configd.py: [492955e2-5ba7-4c3d-ae20-8f57f7eb1602] Reloading filter
Jan 29 12:10:53
kernel: ovpns3: link state changed to DOWN
Jan 29 12:10:45
opnsense: /usr/local/etc/rc.newwanip: Interface '' is disabled or empty, nothing to do.
Jan 29 12:10:45
opnsense: /usr/local/etc/rc.newwanip: IP renewal is starting on 'ovpns2'
Jan 29 12:10:45
configd.py: [322b160d-f284-4934-9d3d-2dd229306122] New IPv4 on ovpns2
Jan 29 12:10:44
configd.py: [67a85ed5-ddfc-4767-ae9f-4c7158ce09af] Reloading filter
Jan 29 12:10:44
kernel: ovpns2: link state changed to UP
Jan 29 12:10:44
configd.py: [b0082bc5-c57d-44cc-bceb-cfdb1b3fbb17] Reloading filter
Jan 29 12:10:38
opnsense: /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
Jan 29 12:10:38
opnsense: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:10:38
opnsense: /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
Jan 29 12:10:38
opnsense: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:10:37
configd.py: [d01b9795-b97e-4321-84d7-181a25e6680b] Reloading filter
Jan 29 12:10:37
kernel: ovpns2: link state changed to DOWN
Jan 29 12:10:37
opnsense: /usr/local/etc/rc.newwanipv6: Resyncing OpenVPN instances for interface WAN.
Jan 29 12:10:37
opnsense: /usr/local/etc/rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::5651:1bff:fe83:ba9b
Jan 29 12:10:12
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:10:12
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:10:12
configd.py: [751f8172-f634-4233-ae53-954e6de5f20f] New IPv6 on pppoe0
Jan 29 12:10:12
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:10:12
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:10:12
configd.py: [751f8172-f634-4233-ae53-954e6de5f20f] New IPv6 on pppoe0
Jan 29 12:10:11
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: fe80::20d:b9ff:fe48:5d64) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:10:11
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:10:10
configd.py: [0b75430c-9449-4e18-a10c-c5dfc0be447e] New IPv6 on pppoe0
Jan 29 12:08:29
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:08:29
opnsense: /usr/local/etc/rc.dyndns: Aborted IP detection: Could not resolve host: checkipv6.dyndns.org
Jan 29 12:08:28
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: (ERROR!) No Password Provided.
Jan 29 12:08:28
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: (ERROR!) No Username Provided.
Jan 29 12:08:27
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:08:26
configd.py: [3da2e8ce-7de6-4d2b-bbc2-135ab69a8145] updating dyndns wan
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: Accept router advertisements on interface pppoe0
Jan 29 12:08:13
kernel: ng0: changing name to 'pppoe0'
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: The command '/sbin/ifconfig 'pppoe0' inet6 -accept_rtadv' returned exit code '1', the output was 'ifconfig: interface pppoe0 does not exist'
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: The command `/sbin/ifconfig -m 'pppoe0'' failed to execute ifconfig: interface pppoe0 does not exist
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface wan
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for wan
Jan 29 12:08:13
configd.py: [732960c7-5351-4472-a7fc-8273ccb17218] Linkup starting igb0_vlan7
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: Accept router advertisements on interface pppoe0
Jan 29 12:08:13
kernel: ng0: changing name to 'pppoe0'
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: The command '/sbin/ifconfig 'pppoe0' inet6 -accept_rtadv' returned exit code '1', the output was 'ifconfig: interface pppoe0 does not exist'
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: The command `/sbin/ifconfig -m 'pppoe0'' failed to execute ifconfig: interface pppoe0 does not exist
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface wan
Jan 29 12:08:13
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for wan
Jan 29 12:08:13
configd.py: [732960c7-5351-4472-a7fc-8273ccb17218] Linkup starting igb0_vlan7
Jan 29 12:08:12
configd.py: [857d3064-7bcd-4a88-a335-97e09a2307af] updating dyndns opt1
Jan 29 12:07:59
opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface opt1
Jan 29 12:07:59
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for opt1
Jan 29 12:07:59
configd.py: [ad25e7f8-9fcf-486f-9d87-64b328b6c22a] Linkup starting igb0
Jan 29 12:07:58
opnsense: /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -d -i 'pppoe0' -a' returned exit code '1', the output was 'arp: interface pppoe0 does not exist'
Jan 29 12:07:56
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for wan
Jan 29 12:07:56
configd.py: [54cf1784-6d63-4e13-bcec-98958e8da90e] Linkup stopping igb0_vlan7
Jan 29 12:07:55
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for opt1
Jan 29 12:07:55
configd.py: [a3bcb477-cade-40ff-a205-63e2a5260605] Linkup stopping igb0
Jan 29 12:07:54
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:07:54
opnsense: /usr/local/etc/rc.dyndns: Aborted IP detection: Could not resolve host: checkipv6.dyndns.org
Jan 29 12:07:53
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: (ERROR!) No Password Provided.
Jan 29 12:07:53
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS: (ERROR!) No Username Provided.
Jan 29 12:07:52
opnsense: /usr/local/etc/rc.dyndns: Dynamic DNS (myownspace) There was an error trying to determine the public IP for interface - wan(pppoe0). Probably interface is not a WAN interface.
Jan 29 12:07:51
configd.py: [d322e6ce-02b9-4cb1-b705-2aec7aa512e9] updating dyndns wan
Jan 29 12:07:39
opnsense: /usr/local/etc/rc.linkup: Accept router advertisements on interface pppoe0
Jan 29 12:07:38
kernel: ng0: changing name to 'pppoe0'
Jan 29 12:07:38
opnsense: /usr/local/etc/rc.linkup: The command '/sbin/ifconfig 'pppoe0' inet6 -accept_rtadv' returned exit code '1', the output was 'ifconfig: interface pppoe0 does not exist'
Jan 29 12:07:38
opnsense: /usr/local/etc/rc.linkup: The command `/sbin/ifconfig -m 'pppoe0'' failed to execute ifconfig: interface pppoe0 does not exist
Jan 29 12:07:38
opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface wan
Jan 29 12:07:38
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for wan
Jan 29 12:07:38
configd.py: [ad037e4e-ebe6-4947-9e54-edf26bc42e93] Linkup starting igb0_vlan7
Jan 29 12:07:37
configd.py: [817168ed-a478-47f8-878c-cb477ce630cc] updating dyndns opt1
Jan 29 12:07:28
kernel: igb0_vlan7: link state changed to UP
Jan 29 12:07:28
kernel: igb0: link state changed to UP
Jan 29 12:07:23
opnsense: /usr/local/etc/rc.linkup: HOTPLUG: Configuring interface opt1
Jan 29 12:07:23
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet attached event for opt1
Jan 29 12:07:23
kernel: igb0_vlan7: link state changed to DOWN
Jan 29 12:07:23
kernel: igb0: link state changed to DOWN
Jan 29 12:07:23
configd.py: [c3f18b0b-0211-4381-a681-3e9bea048e3c] Linkup starting igb0
Jan 29 12:07:23
opnsense: /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -d -i 'pppoe0' -a' returned exit code '1', the output was 'arp: interface pppoe0 does not exist'
Jan 29 12:07:22
opnsense: /usr/local/etc/rc.newwanipv6: Failed to detect IP for WAN[wan]
Jan 29 12:07:22
opnsense: /usr/local/etc/rc.newwanipv6: On (IP address: ) (interface: WAN[wan]) (real interface: pppoe0).
Jan 29 12:07:22
opnsense: /usr/local/etc/rc.newwanipv6: IP renewal is starting on 'pppoe0'
Jan 29 12:07:22
configd.py: [ca4d44e5-f23b-418b-b62d-54d43104661d] New IPv6 on pppoe0
Jan 29 12:07:14
kernel: igb0_vlan7: link state changed to UP
Jan 29 12:07:14
kernel: igb0: link state changed to UP
Jan 29 12:06:53
configd.py: [da34ea73-0b5b-4142-b2e7-eb9b8196a524] Rewriting resolv.conf
Jan 29 12:06:53
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for interface pppoe0
Jan 29 12:06:53
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for IP fe80::20d:b9ff:fe48:5d64%pppoe0/32
Jan 29 12:06:52
configd.py: [7f1e8451-c7ba-4b3b-b7b2-a0be61679c73] Rewriting resolv.conf
Jan 29 12:06:52
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for interface pppoe0
Jan 29 12:06:52
opnsense: /usr/local/etc/rc.kill_states: rc.kill_states: Removing states for IP 87.122.2.48/32
Jan 29 12:06:51
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for wan
Jan 29 12:06:51
configd.py: [d378aac4-f787-457d-8465-beb3c47cdcd5] Linkup stopping igb0_vlan7
Jan 29 12:06:51
opnsense: /usr/local/etc/rc.linkup: DEVD Ethernet detached event for opt1
Jan 29 12:06:50
configd.py: [1ca0205f-8d29-4695-b612-d08248dfe587] Linkup stopping igb0
Jan 29 12:06:50
kernel: igb0_vlan7: link state changed to DOWN
Jan 29 12:06:50
kernel: igb0: link state changed to DOWN
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #21 on:
February 01, 2018, 05:33:15 pm »
Ich weiß wirklich nicht mehr was mit meine Box los ist. Ich möchte es wirklich nicht vergleichen mit "pf" , aber "pf" sieht echt viel stabiler aus, die gleichen Einstellungen laufen mit "pf" seit mehr als 3 Monate ohne Probleme, DynDNS über IPv6 auch funktioniert und es zeigt keinen Fehler, Reset all States after WAN IP Change funktioniert auch wunderbar und FritzBox hinter "pf" hat seine Verbindung direkt ohne Problem mit den aus- oder eingehenden Anrufen, OpenVPN funktioniert auch sehr gut.
Ich habe das Gefühl dass die Entwickler von OPNsense etwas schönes in kürzer Zeit erreicht haben (was "pf" in mehr als 10 Jahren erreicht hat), viele schöne Features, aber "pf" ist stabiler im Vergleich mit OPNsense.
Ich möchte keine Diskussion führen "welches ist besser: pf oder OPN", aber ich bin der Meinung, die Welt von Open Source ist schöner und sauberer, weg von der Firmenpolitik, aber meine Erfahrung damit sagt bis heute "pf" ist stabiler und läuft sehr sauber.
Ich hoffe dass jemand dabei hilft, und vielleicht ist dieses Problem ein BUG.
Danke euch alle.
P.S. Sorry, aber ich musste mein Topic auf mehrere Teile posten, weil es auf eins nicht geklappt hat.
«
Last Edit: February 01, 2018, 05:35:35 pm by karl047
»
Logged
theq86
Sr. Member
Posts: 272
Karma: 37
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #22 on:
February 01, 2018, 08:24:18 pm »
Interessant. Ich habe momentan ebenfalls Probleme mit IPv6 nach der Zwangstrennung.
Meine Clients wollen einfach nicht über IPv6 ins Internet. Adressen bekommen sie problemlos zugewiesen.
Eine Analyse ergab, dass Pings von einem Client an einen Testserver ankamen, vom Testserver replied wurden, aber dann an der sense auf pppoe0 kommt nichts mehr an. Nach einem Restart der Box funktioniert wieder alles.
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #23 on:
February 01, 2018, 08:54:14 pm »
@nasq: ich sage dir warum: Ich habe zuletzt OPNsense installiert und von vornherein eingestellt (PPPoE Verbindung), ich wollte nur wissen ob ich früher mit meinen Einstellungen "vlt" etwas falsches gemacht habe, alles hat nach der Einrichtung funktioniert, danach kam der Punkt: ICMP für IPv4 und IPv6 im WAN Interface einrichten, dann kam der Fehler (das Bild in meinem vorherigen Post), obwohl die beiden Family Adressen mit eigenen Protokollen eingestellt sind.
Später habe ich getestet wie die Box reagieren wird wenn die Zwangtrennung geführt wird, dann habe ich festgestellt: Ja, tatsächlich, ich bekomme eine neue Verbindung mit IPv4 aber instabil, und ein paar Internet Seiten funktionieren nicht mehr. Ich habe gemerkt dass die Box von ISP eine neue IPv6 Adresse bekommt, aber die Prefix ist weiter gleich geblieben!.
Das ist das Problem, ICMP im WAN Interface hat irgendwie mit dieser Version einen BUG, definitiv, und die Prefix nach der neuen Verbindungsaufbau wird nicht aktualisiert: Alle Clients bekommen die IPv6 Adresse zugewiesen, aber nicht aktuell, sondern verbunden mit der alten Prefix.
du kannst es probieren, ich habe 3 Mal nachgeguckt, und mehr als 30 Minuten gewartet, vlt wird die Prefix für meine Interfaces aktualisiert, aber leider ist nichts passiert. Nach einem Restart bekommst du alles neu und aktualisiert, deswegen wird alles funktionieren wie du beschrieben hast.
Gruß
Karl
«
Last Edit: February 01, 2018, 09:03:09 pm by karl047
»
Logged
theq86
Sr. Member
Posts: 272
Karma: 37
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #24 on:
February 01, 2018, 09:47:01 pm »
Ich habe bei Github ein Bugreport eingestellt. Hier würde das vermutlich untergehen.
Logged
karl047
Full Member
Posts: 129
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #25 on:
February 01, 2018, 10:07:23 pm »
@nasq: gut gemacht... schickst mir bitte das Link damit ich es weiter verfolgen kann?
Logged
theq86
Sr. Member
Posts: 272
Karma: 37
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #26 on:
February 01, 2018, 10:18:18 pm »
https://github.com/opnsense/core/issues/2155
Logged
JeGr
Hero Member
Posts: 1945
Karma: 227
old man standing
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #27 on:
February 06, 2018, 04:27:39 pm »
Hmm keiner der Mods/Admins da - irgendwie sehen die letzten Post ein wenig SPAMmy aus?!
Logged
"It doesn't work!" is no valid error description!
- Don't forget to [applaud] those offering time & brainpower to help you!
Better have some *sense as no(n)sense!
If you're interested in german-speaking business support, feel free to reach out via PM.
franco
Administrator
Hero Member
Posts: 17668
Karma: 1611
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #28 on:
February 06, 2018, 05:59:54 pm »
Ja, cleveres Spam. Jetzt ist's weg. Sorry.
Grüsse
Franco
Logged
vikozo
Full Member
Posts: 211
Karma: 5
Re: PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?
«
Reply #29 on:
February 07, 2018, 01:39:50 pm »
hallo
Fritzbox und Bridge Mode würde gehen
https://www.green.ch/Support/Helpdesk/HelpdeskSub/TabId/1544/ArtMID/6180/ArticleID/88/FRITZBox-als-Bridge.aspx
gruss
vinc
Logged
apu2c4 / wle200nx / 240 Disk
--> Firewall | FW-03
---
OPNsense 22.1.6-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1n 15 Mar 2022
Print
Pages:
1
[
2
]
3
« previous
next »
OPNsense Forum
»
International Forums
»
German - Deutsch
»
PPP0E Verbindung oder direkte Verbindung zu FritzBox? welche Methode ist besser?