Hood-status April 2018

hood-status@lists.ffnw.de

2 participants
3 discussions

Re: [fastd] problem in Hood oldenburg2: fastd tunnel cannot be established

by Simon Kurka

Testen bitte woanders. <alert(a)ffnw.de> schrieb am Mo., 23. Apr. 2018, 12:21: > Mon Apr 23 12:17:24 2018 daemon.info fastd[23055]: resolved host ` > ol01.sn.ffnw.de' successfully > Mon Apr 23 12:17:24 2018 daemon.info fastd[23055]: resolved host ` > ol01.sn.ffnw.de' successfully > Mon Apr 23 12:17:25 2018 daemon.notice netifd: Interface 'mesh_vpn' is now > up > Mon Apr 23 12:17:25 2018 kern.info kernel: [744948.106901] batman_adv: > bat0: Adding interface: mesh-vpn > Mon Apr 23 12:17:25 2018 kern.info kernel: [744948.114689] batman_adv: > bat0: The MTU of interface mesh-vpn is too small (1312) to handle the > transport of batman-adv packets. Packets going over this interface will be > fragmented on layer2 which could impact the performance. Setting the MTU to > 1532 would solve the problem. > Mon Apr 23 12:17:25 2018 kern.info kernel: [744948.148984] batman_adv: > bat0: Interface activated: mesh-vpn > Mon Apr 23 12:17:25 2018 daemon.err odhcp6c[23103]: Failed to send DHCPV6 > message to ff02::1:2 (Address not available) > Mon Apr 23 12:17:26 2018 daemon.info fastd[23055]: sending handshake to > <mesh_vpn_backbone_peer__10002>[5.9.56.26:10002]... > Mon Apr 23 12:17:26 2018 daemon.info fastd[23055]: received handshake > response from <mesh_vpn_backbone_peer__10002>[5.9.56.26:10002] using > fastd v18 > Mon Apr 23 12:17:26 2018 daemon.info fastd[23055]: 5.9.56.26:10002 > authorized as <mesh_vpn_backbone_peer__10002> > Mon Apr 23 12:17:26 2018 daemon.notice fastd[23055]: connection with > <mesh_vpn_backbone_peer__10002> established. > Mon Apr 23 12:17:26 2018 daemon.info fastd[23055]: new session with > <mesh_vpn_backbone_peer__10002> established using method `salsa2012+umac'. > Mon Apr 23 12:17:26 2018 daemon.err odhcp6c[23103]: Failed to send DHCPV6 > message to ff02::1:2 (Address not available) > Mon Apr 23 12:17:26 2018 kern.info kernel: [744949.455482] br-client: > port 2(local-port) entered forwarding state > Mon Apr 23 12:17:26 2018 kern.info kernel: [744949.481987] br-client: > port 1(bat0) entered forwarding state > Mon Apr 23 12:17:27 2018 daemon.info respondd[23191]: unable to read > providers from '/usr/lib/respondd', ignoring > Mon Apr 23 12:17:33 2018 daemon.notice netifd: Interface 'client' is now up > Mon Apr 23 12:17:34 2018 user.notice firewall: Reloading firewall due to > ifup of client (br-client) > Mon Apr 23 12:17:34 2018 daemon.warn fastd[23055]: sendmsg: Operation not > permitted > Mon Apr 23 12:17:34 2018 daemon.info respondd[23341]: unable to read > providers from '/usr/lib/respondd', ignoring > > > _______________________________________________ > Hood-status mailing list -- hood-status(a)lists.ffnw.de > To unsubscribe send an email to hood-status-leave(a)lists.ffnw.de >

5 years, 1 month

[l2tp] problem in Hood landkreis-wittmund: l2tp tunnel cannot be established

by alert＠ffnw.de

Mon Apr 23 11:28:01 2018 daemon.warn td-client: Received error response from broker! Mon Apr 23 11:28:01 2018 daemon.err td-client: Connection to wtm01.sn.ffnw.de lost. Mon Apr 23 11:28:02 2018 daemon.info td-client: Performing broker selection... Mon Apr 23 11:28:03 2018 daemon.debug td-client: Broker usage of wtm01.sn.ffnw.de:9000: 0 Mon Apr 23 11:28:03 2018 daemon.info td-client: Selected wtm01.sn.ffnw.de:9000 as the best broker. Mon Apr 23 11:28:04 2018 daemon.warn td-client: Received error response from broker! Mon Apr 23 11:28:04 2018 daemon.err td-client: Connection to wtm01.sn.ffnw.de lost. Mon Apr 23 11:28:04 2018 daemon.info td-client: Performing broker selection... Mon Apr 23 11:28:05 2018 daemon.debug td-client: Broker usage of wtm01.sn.ffnw.de:9000: 0 Mon Apr 23 11:28:05 2018 daemon.info td-client: Selected wtm01.sn.ffnw.de:9000 as the best broker. Mon Apr 23 11:28:06 2018 daemon.warn td-client: Received error response from broker! Mon Apr 23 11:28:06 2018 daemon.err td-client: Connection to wtm01.sn.ffnw.de lost. Mon Apr 23 11:28:06 2018 daemon.info td-client: Performing broker selection... Mon Apr 23 11:28:07 2018 daemon.debug td-client: Broker usage of wtm01.sn.ffnw.de:9000: 0 Mon Apr 23 11:28:07 2018 daemon.info td-client: Selected wtm01.sn.ffnw.de:9000 as the best broker. Mon Apr 23 11:28:08 2018 daemon.warn td-client: Received error response from broker! Mon Apr 23 11:28:08 2018 daemon.err td-client: Connection to wtm01.sn.ffnw.de lost. Mon Apr 23 11:28:08 2018 daemon.info td-client: Performing broker selection... Mon Apr 23 11:28:09 2018 daemon.debug td-client: Broker usage of wtm01.sn.ffnw.de:9000: 0 Mon Apr 23 11:28:09 2018 daemon.info td-client: Selected wtm01.sn.ffnw.de:9000 as the best broker.

5 years, 1 month

test

by alert

test

5 years, 1 month

2023

2022

2021

2020

2019

2018

Hood-status April 2018