im Terminal stand:
Segmentation fault
-------- Weitergeleitete Nachricht -------- Betreff: problem in Hood lohne: VPN-tunnel cannot be established Datum: Thu, 21 Dec 2017 23:08:44 +0100 Von: alert@ffnw.de An: alert@ffnw.de
Thu Dec 21 23:05:16 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Thu Dec 21 23:05:16 2017 kern.info kernel: [10385.983231] batman_adv: bat0: Adding interface: mesh-vpn Thu Dec 21 23:05:16 2017 kern.info kernel: [10385.983938] 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. Thu Dec 21 23:05:16 2017 kern.info kernel: [10385.987229] batman_adv: bat0: Interface activated: mesh-vpn Thu Dec 21 23:05:16 2017 daemon.info respondd[27036]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:22 2017 daemon.notice netifd: Interface 'client' is now up Thu Dec 21 23:05:22 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client) Thu Dec 21 23:05:22 2017 daemon.info respondd[27172]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:33 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client) Thu Dec 21 23:05:37 2017 daemon.notice netifd: bridge 'br-client' link is down Thu Dec 21 23:05:37 2017 daemon.notice netifd: Interface 'client' has link connectivity loss Thu Dec 21 23:05:37 2017 kern.info kernel: [10407.145466] br-client: port 2(local-port) entered disabled state Thu Dec 21 23:05:37 2017 kern.info kernel: [10407.146494] br-client: port 1(bat0) entered disabled state Thu Dec 21 23:05:37 2017 daemon.warn td-client: Got termination signal, shutting down tunnel... Thu Dec 21 23:05:37 2017 daemon.notice netifd: Network device 'mesh-vpn' link is down Thu Dec 21 23:05:37 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity loss Thu Dec 21 23:05:37 2017 kern.info kernel: [10407.176797] batman_adv: bat0: Interface deactivated: mesh-vpn Thu Dec 21 23:05:37 2017 kern.info kernel: [10407.178595] batman_adv: bat0: Removing interface: mesh-vpn Thu Dec 21 23:05:37 2017 daemon.info respondd[27518]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:37 2017 daemon.err respondd[27518]: join_mcast: no valid interface given Thu Dec 21 23:05:37 2017 daemon.notice netifd: Interface 'mesh_vpn' is disabled Thu Dec 21 23:05:37 2017 daemon.info respondd[27546]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:38 2017 daemon.err odhcp6c[26860]: Failed to send DHCPV6 message to ff02::1:2 (Permission denied) Thu Dec 21 23:05:38 2017 daemon.notice netifd: bridge 'br-client' link is up Thu Dec 21 23:05:38 2017 daemon.notice netifd: Interface 'client' has link connectivity Thu Dec 21 23:05:38 2017 daemon.notice netifd: Interface 'client' is setting up now Thu Dec 21 23:05:38 2017 daemon.info td-client: Performing broker selection... Thu Dec 21 23:05:38 2017 kern.info kernel: [10408.212489] br-client: port 2(local-port) entered forwarding state Thu Dec 21 23:05:38 2017 kern.info kernel: [10408.213256] br-client: port 2(local-port) entered forwarding state Thu Dec 21 23:05:38 2017 kern.info kernel: [10408.213936] br-client: port 1(bat0) entered forwarding state Thu Dec 21 23:05:38 2017 kern.info kernel: [10408.214572] br-client: port 1(bat0) entered forwarding state Thu Dec 21 23:05:39 2017 daemon.err odhcp6c[27597]: Failed to send DHCPV6 message to ff02::1:2 (Address not available) Thu Dec 21 23:05:40 2017 kern.info kernel: [10410.209651] br-client: port 1(bat0) entered forwarding state Thu Dec 21 23:05:40 2017 kern.info kernel: [10410.211403] br-client: port 2(local-port) entered forwarding state Thu Dec 21 23:05:43 2017 daemon.info td-client: Selected vec01.sn.ffnw.de:9002 as the best broker. Thu Dec 21 23:05:46 2017 daemon.info td-client: Tunnel successfully established. Thu Dec 21 23:05:46 2017 daemon.notice netifd: Interface 'mesh_vpn' is enabled Thu Dec 21 23:05:46 2017 daemon.notice netifd: Network device 'mesh-vpn' link is up Thu Dec 21 23:05:46 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity Thu Dec 21 23:05:46 2017 daemon.notice netifd: Interface 'mesh_vpn' is setting up now Thu Dec 21 23:05:46 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Thu Dec 21 23:05:46 2017 kern.info kernel: [10416.488867] batman_adv: bat0: Adding interface: mesh-vpn Thu Dec 21 23:05:46 2017 kern.info kernel: [10416.489587] 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. Thu Dec 21 23:05:46 2017 kern.info kernel: [10416.493042] batman_adv: bat0: Interface activated: mesh-vpn Thu Dec 21 23:05:46 2017 daemon.info respondd[27771]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:47 2017 kern.info kernel: [10417.431010] traps: logread[27777] general protection ip:7f26553a783e sp:7ffefa0eac00 error:0 in libc.so[7f2655355000+68000] Thu Dec 21 23:05:52 2017 daemon.notice netifd: Interface 'client' is now up Thu Dec 21 23:05:52 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client) Thu Dec 21 23:05:52 2017 daemon.info respondd[27908]: unable to read providers from '/usr/lib/respondd', ignoring Thu Dec 21 23:05:54 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
Hi,
das weis Lorenz wohl nur :D
Sowohl per fastd als auch l2tp funktioniert der tunnel - hab es selber mit Routern von Sem getestet.
VG
Stefan
Am 22.12.2017 um 10:21 schrieb Jan-Tarek Butt via Dev:
On 12/21/17 23:12, alert via Dev wrote:
im Terminal stand:
Segmentation fault
wann genau trat das auf ?
Log sieht soweit gut aus.
vg Tarek
Dev mailing list -- dev@lists.ffnw.de To unsubscribe send an email to dev-leave@lists.ffnw.de
Hi,
das weis Lorenz wohl nur :D
@lorenz: hast du da was?
Sowohl per fastd als auch l2tp funktioniert der tunnel - hab es selber mit Routern von Sem getestet.
Ja das hab ich in den logs gesehen.
vg Tarek
ja:
---------------------8<--------------------- Datum: Thu, 21 Dec 2017 23:08:44 +0100 --------------------->8---------------------
um diese Zeit, hat der betroffene Router mir die mail geschickt und unmittelbar darauf (23:12) hatte ich sie auch schon weitergeleitet. Hilft das?
LG aus Leipzig Lorenz
Am 23.12.2017 um 23:29 schrieb Jan-Tarek Butt via Dev:
Hi,
das weis Lorenz wohl nur :D
@lorenz: hast du da was?
Sowohl per fastd als auch l2tp funktioniert der tunnel - hab es selber mit Routern von Sem getestet.
Ja das hab ich in den logs gesehen.
vg Tarek
Dev mailing list -- dev@lists.ffnw.de To unsubscribe send an email to dev-leave@lists.ffnw.de
Hi,
um diese Zeit, hat der betroffene Router mir die mail geschickt und unmittelbar darauf (23:12) hatte ich sie auch schon weitergeleitet. Hilft das?
Ah, ich dachte du hättest mehr infos zum seg fault. Z.b. bei welchem Prozess das auftrat oder so. Ohne nähere infos können wir das Segmentation fault so gut wie nicht finden, da es so gesehen jede Software auf dem gerät sein kann.
LG aus Leipzig
Ich möchte auch :´´-(
Schöne Grüße Tarek