[B.A.T.M.A.N.] deactivated/reenabled interfaces needs batmand restart

[B.A.T.M.A.N.] deactivated/reenabled interfaces needs batmand restart

[Freifunk Dresden]

Hello again,


I'm running batman-experimental rev1023. Batman is running with two interfaces, one for wifi and one for
backbone. The backbone interface is created by tincd a vpn deamon. If I have an active vpn connection
batman recognizes the nodes at the other end of this connection. When the connection dead because the client
has closed the vpn connection, batman is still working correctly.

The problem occurres when the client re-creates the vpn connection. Batman ignores the interface. the log does not
show incomming packages from the vpn-client. If I just restart batmand with the two interfaces, batman shows
the packets within seconds and the node is reachable.

Is there a way that the inactive interfaces are reactivated and used automatically?

/Stephan

Re: [B.A.T.M.A.N.] deactivated/reenabled interfaces needs batmand restart

[Axel Neumann]

Hi,
I am aware of that problem and plan to port the interface-watchdog idea from 
batman-0.3 rv970/971 also to batman-exp. Just give me some time...

ciao,
axel


On Montag 05 Mai 2008, Freifunk Dresden wrote:
> Hello again,
>
>
> I'm running batman-experimental rev1023. Batman is running with two
> interfaces, one for wifi and one for backbone. The backbone interface is
> created by tincd a vpn deamon. If I have an active vpn connection batman
> recognizes the nodes at the other end of this connection. When the
> connection dead because the client has closed the vpn connection, batman is
> still working correctly.
>
> The problem occurres when the client re-creates the vpn connection. Batman
> ignores the interface. the log does not show incomming packages from the
> vpn-client. If I just restart batmand with the two interfaces, batman shows
> the packets within seconds and the node is reachable.
>
> Is there a way that the inactive interfaces are reactivated and used
> automatically?
>
> /Stephan
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n

Re: [B.A.T.M.A.N.] deactivated/reenabled interfaces needs batmand restart

[Axel Neumann]

On Montag 05 Mai 2008, Freifunk Dresden wrote:
> Hello again,
>
>
> I'm running batman-experimental rev1023. Batman is running with two
> interfaces, one for wifi and one for backbone. The backbone interface is
> created by tincd a vpn deamon. If I have an active vpn connection batman
> recognizes the nodes at the other end of this connection. When the
> connection dead because the client has closed the vpn connection, batman is
> still working correctly.
>
> The problem occurres when the client re-creates the vpn connection. Batman
> ignores the interface. the log does not show incomming packages from the
> vpn-client. If I just restart batmand with the two interfaces, batman shows
> the packets within seconds and the node is reachable.
>
> Is there a way that the inactive interfaces are reactivated and used
> automatically?

checkout rv 1062 !

best
/axel

>
> /Stephan
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n

Re: [B.A.T.M.A.N.] deactivated/reenabled interfaces needs batmand restart

[Freifunk Dresden]

Hi Axel,

> checkout rv 1062 !
thanks a lot. It is working as I like.

Regards
  Stephan