strange kernel log errors

Home Page Forums Network Management ZeroShell strange kernel log errors

This topic contains 3 replies, has 0 voices, and was last updated by  tim 12 years, 2 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #40517

    tim
    Member

    I keep getting the following errors in the kernel log, while the interface is never down…
    Also in network settings I have “Unknown link status” for BOND00…

    05:43:38  bonding: BOND00: link status down again after 3300 ms for interface VPN01.
    05:43:40 bonding: BOND00: link status down again after 2900 ms for interface VPN00.
    05:43:40 bonding: BOND00: link status up for interface VPN01, enabling it in 7000 ms.
    05:43:42 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:43:43 bonding: BOND00: link status down again after 3000 ms for interface VPN01.
    05:43:45 bonding: BOND00: link status up for interface VPN01, enabling it in 7000 ms.
    05:43:49 bonding: BOND00: link status definitely up for interface VPN00.
    05:43:52 bonding: BOND00: link status definitely up for interface VPN01.
    05:46:06 bonding: BOND00: link status definitely down for interface VPN00, disabling it
    05:46:07 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:10 bonding: BOND00: link status down again after 3000 ms for interface VPN00.
    05:46:12 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:15 bonding: BOND00: link status down again after 3400 ms for interface VPN00.
    05:46:17 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:20 bonding: BOND00: link status down again after 3200 ms for interface VPN00.
    05:46:22 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:25 bonding: BOND00: link status down again after 2300 ms for interface VPN00.
    05:46:27 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:30 bonding: BOND00: link status down again after 3500 ms for interface VPN00.
    05:46:32 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:35 bonding: BOND00: link status down again after 3100 ms for interface VPN00.
    05:46:37 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:41 bonding: BOND00: link status down again after 3300 ms for interface VPN00.
    05:46:43 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:46 bonding: BOND00: link status down again after 3500 ms for interface VPN00.
    05:46:48 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:46:51 bonding: BOND00: link status down again after 2400 ms for interface VPN00.
    05:46:53 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    05:47:00 bonding: BOND00: link status definitely up for interface VPN00.
    06:08:05 bonding: BOND00: link status definitely down for interface VPN00, disabling it
    06:08:35 bonding: BOND00: link status up for interface VPN00, enabling it in 7000 ms.
    06:08:42 bonding: BOND00: link status definitely up for interface VPN00.

    (edit: log was incomplete)

    #45041

    imported_fulvio
    Participant

    I think the vpn VPN00 is not stable. Check the openvpn logs to know why.
    Don’t worry for the “Unknown link status” for BOND00 in the networking settings because I have not write the procedure which checks the Bond link status yet.

    Regards
    Fulvio

    #45042

    tim
    Member

    indeed I have errors in the openvpn log,

    however I dont really understand why… both hosts are up all the time…

    09:16:23  WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
    09:16:23 LZO compression initialized
    09:16:23 TUN/TAP device VPN01 opened
    09:16:23 UDPv4 link local (bound): 10.1.1.2:7000
    09:16:23 UDPv4 link remote: xxx.xxx.xxx.xxx:7000
    09:16:26 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=113)
    09:16:26 [UNDEF] Inactivity timeout (--ping-restart), restarting
    09:16:26 SIGUSR1[soft,ping-restart] received, process restarting
    09:16:28 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
    09:16:28 LZO compression initialized
    09:16:28 TUN/TAP device VPN01 opened
    09:16:28 UDPv4 link local (bound): 10.1.1.2:7000
    09:16:28 UDPv4 link remote: xxx.xxx.xxx.xxx:7000
    09:16:31 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=113)
    09:16:31 [UNDEF] Inactivity timeout (--ping-restart), restarting
    09:16:31 SIGUSR1[soft,ping-restart] received, process restarting

    and at the server side:

    18:03:26  TUN/TAP device VPN01 opened
    18:03:26 UDPv4 link local (bound): xxx.xxx.xxx.xxx:7000
    18:03:26 UDPv4 link remote: yyy.yyy.yyy.yyy:7000
    18:03:31 [UNDEF] Inactivity timeout (--ping-restart), restarting
    18:03:31 SIGUSR1[soft,ping-restart] received, process restarting
    18:03:33 LZO compression initialized
    #45043

    imported_fulvio
    Participant

    Are you sure that the Internet connection is ok?
    Try to ping yyy.yyy.yyy.yyy from xxx.xxx.xxx.xxx
    Then I notice your client peer is on private network (ip: 10.1.1.2). Try to not specify the remote host in the vpn server configuration.

    #45044

    tim
    Member

    Well the connection seems to work because I can access the internet 🙂

    However – the DSL provider does not allow to ping to the IPs …

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.