Hat es jemand schon mit GigaNetz zum laufen bekommen? Bin gestern gescheitert mit VLAN7 und SLAAC.
Häng da auch grad dran.
vielleicht kann irgendwer helfen.
Code
UDMPRO ppp1[2049236]: pppd 2.4.9 started by root, uid 0
UDMPRO ppp1[2049236]: PADS: Service-Name: ''
UDMPRO ppp1[2049236]: PPP session is 146
UDMPRO ppp1[2049236]: Connected to 42:8f:9d:22:b9:c7 via interface eth9.7
UDMPRO ppp1[2049236]: using channel 150
UDMPRO ppp1[2049236]: Using interface ppp1
UDMPRO ppp1[2049236]: Connect: ppp1 <--> eth9.7
UDMPRO ppp1[2049236]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x46442459>]
UDMPRO ppp1[2049236]: rcvd [LCP ConfAck id=0x1 <mru 1492> <magic 0x46442459>]
UDMPRO ppp1[2049236]: rcvd [LCP ConfReq id=0x7e <mru 1492> <auth chap MD5> <magic 0x227a1964>]
UDMPRO ppp1[2049236]: sent [LCP ConfAck id=0x7e <mru 1492> <auth chap MD5> <magic 0x227a1964>]
UDMPRO ppp1[2049236]: sent [LCP EchoReq id=0x0 magic=0x46442459]
UDMPRO ppp1[2049236]: rcvd [LCP EchoRep id=0x0 magic=0x227a1964]
UDMPRO ppp1[2049236]: rcvd [CHAP Challenge id=0x69 <27b69dc818912b3c22a5920995c42ab6aac2c4>, name = "JUNOS"]
2025-12-01T17:37:56+01:00 UDMPRO ppp1[2049236]: sent [CHAP Response id=0x69 <1351fc33f30dbffbbd67dcb958def84a>, name = "P1419240@dgn.digital"]
UDMPRO ppp1[2049236]: rcvd [CHAP Success id=0x69 ""]
UDMPRO ppp1[2049236]: CHAP authentication succeeded
UDMPRO ppp1[2049236]: CHAP authentication succeeded
UDMPRO ppp1[2049236]: peer from calling number 42:8F:9D:22:B9:C7 authorized
UDMPRO ppp1[2049236]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
UDMPRO ppp1[2049236]: sent [IPV6CP ConfReq id=0x1 <addr fe80::0cdc:9a18:743d:f61a>]
UDMPRO ppp1[2049236]: rcvd [LCP ProtRej id=0x7f 80 21 01 01 00 16 03 06 00 00 00 00 81 06 00 00 00 00 83 06 00 00 00 00]
UDMPRO ppp1[2049236]: Protocol-Reject for 'Internet Protocol Control Protocol' (0x8021) received
UDMPRO ppp1[2049236]: rcvd [IPV6CP ConfReq id=0xe6 <addr fe80::428f:9dff:fe22:b9c7>]
UDMPRO ppp1[2049236]: sent [IPV6CP ConfAck id=0xe6 <addr fe80::428f:9dff:fe22:b9c7>]
UDMPRO ppp1[2049236]: rcvd [IPV6CP ConfAck id=0x1 <addr fe80::0cdc:9a18:743d:f61a>]
UDMPRO ppp1[2049236]: local LL address fe80::0cdc:9a18:743d:f61a
UDMPRO ppp1[2049236]: remote LL address fe80::428f:9dff:fe22:b9c7
UDMPRO ppp1[2049236]: Script /etc/ppp/ipv6-up started (pid 2049453)
UDMPRO ubios-udapi-server[1447]: dhcp-client: Resuming odhcp6c on ppp1
UDMPRO ppp1[2049236]: Script /etc/ppp/ipv6-up finished (pid 2049453), status = 0x0
UDMPRO mcad[4178]: wman.wan_man_allocate(): Allocating WAN geo-info=yes wan=10:WAN2:ip6tnl2<-ppp1<-eth9.7<-eth9
UDMPRO mcad[4178]: wman._dump(): >> id=10 name=WAN2 geo-info=yes ifname=ip6tnl2<-ppp1<-eth9.7<-eth9 ip=none
UDMPRO mcad[4178]: wman._dump(): >> id=10 name=WAN2 geo-info=yes ifname=ip6tnl2<-ppp1<-eth9.7<-eth9 ip=192.0.0.3
UDMPRO ubios-udapi-server[1447]: hb46pp-client: Resuming ubnt-hb46pp on ppp1
UDMPRO ubios-udapi-server[1447]: utils-daemon: Routine execution time of 697ms exceeds expectations in ubios-udapi-server (single_filter_observer<resource_interfaces_plug_iface_observer> action ppp1)
UDMPRO ubios-udapi-server[1447]: dhcp-client: [RA-absent] Using SERVER address as gateway: fe80::428f:9dff:fe22:b9c7 on ppp1
UDMPRO ubios-udapi-server[1447]: WAN-Diag(ppp1): res-interfaces: Adding dynamic address 2a01:41e3:4000::1:500f/128 with lifetime 86390/86390 to interface ppp1
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-9 (2a01:41e3:4000::1:500f) is skipped due to unmatching version of target's IP address 1.1.1.1
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-10 (2a01:41e3:4000::1:500f) is skipped due to unmatching version of target's IP address 8.8.8.8
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-14 (2a01:41e3:4000::1:500f) is skipped due to unmatching version of target's IP address 1.1.1.1
UDMPRO ubios-udapi-server[1447]: wan-failover-interfaces: wf-interface-ppp1 (2a01:41e3:4000::1:500f) is unknown [---____](~down~)
UDMPRO ubios-udapi-server[1447]: utils-daemon: Routine execution time of 511ms exceeds expectations in ubios-udapi-server (single_filter_observer<wan_failover_interfaces_iface_observer> action ppp1)
UDMPRO ubios-udapi-server[1447]: WAN-Diag(ppp1): res-interfaces: Adding new dynamic route ::/0 via fe80::428f:9dff:fe22:b9c7/ppp1 in table 202 (DHCP)
UDMPRO ubios-udapi-server[1447]: WAN-Diag(ppp1): res-interfaces: Adding PD prefix 2a01:41e3:5100:400::/56 with lifetime 86390/86390 to interface ppp1
UDMPRO ubios-udapi-server[1447]: WAN-Diag(ppp1): prefix-delegation: Adding PD prefix 2a01:41e3:5100:400::/56 with lifetime 86390/86390 to interface ppp1
UDMPRO ubios-udapi-server[1447]: WAN-Diag(ppp1): res-interfaces: Provisioning IP6TNL parameters from DHCP: dslite||aftr.fra.purtel.com||
UDMPRO ubios-udapi-server[1447]: tunnel-controller: ip6tnl2 will resolve remote aftr.fra.purtel.com with known nameservers: 2a01:860::53 (ppp0), 2a01:860::153 (ppp0), 176.95.16.250 (ppp1), 176.95.16.251 (ppp1), 1.1.1.1 (lo) and applicable nameservers: 2001:4860:4860::8888
UDMPRO ubios-udapi-server[1447]: tunnel-controller: ip6tnl2 will resolve remote aftr.fra.purtel.com with known nameservers: 2a01:860::53 (ppp0), 2a01:860::153 (ppp0), 2a01:41e0:10::6 (ppp1), 2a01:41e1:ffff:f001::4 (ppp1), 1.1.1.1 (lo) and applicable nameservers: 2a01:41e0:10::6, 2a01:41e1:ffff:f001::4
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-8 (2a01:41e3:4000::1:500f) makes resolver DNSs: 2a01:41e0:10::6, 2a01:41e1:ffff:f001::4
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-11 (2a01:41e3:4000::1:500f) makes resolver DNSs: 2a01:41e0:10::6, 2a01:41e1:ffff:f001::4
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-12 (2a01:41e3:4000::1:500f) makes resolver DNSs: 2a01:41e0:10::6, 2a01:41e1:ffff:f001::4
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-13 (2a01:41e3:4000::1:500f) makes resolver DNSs: 2a01:41e0:10::6, 2a01:41e1:ffff:f001::4
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-8 (2a01:41e3:4000::1:500f) could not resolve ping.ui.com (aaaa): End of file
UDMPRO ubios-udapi-server[1447]: wan-failover-interfaces: wf-interface-ppp1 (2a01:41e3:4000::1:500f) is down [DDDdddd](no dns)
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-11 (2a01:41e3:4000::1:500f) could not resolve ping.ui.com (aaaa): End of file
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-12 (2a01:41e3:4000::1:500f) could not resolve www.microsoft.com (aaaa): End of file
UDMPRO ubios-udapi-server[1447]: wan-failover-monitors: wf-monitor-ppp1-13 (2a01:41e3:4000::1:500f) could not resolve google.com (aaaa): End of file
Alles anzeigen