-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
another feature i forgot in the last mail :)
It would be great if batman allows to dynamic add and remove announced networks via the unix socket interface.
for example # adds new announced network batmand -c -a someip/mask # removes some announced network batmand -c -A someip/mask
why ? we are working on the posibility to give a computer in the mesh a unique ip, besides the network the node is serving. if you assign a unique ip to a computer, and get a dhcp lease of another node, the node would then add your ip as a hostroute announcement to batman, which would overwrite the default place: your home network. this would mean real mobile ip without the overhead of sending the traffic to your home router and then forward to your actual position.
besides this, it would allow better integration into bgp by simply spawning a script to add/remove routes via zebra.
kindly regards daniel
On Friday 15 June 2007 18:54, Daniel Poelzleithner wrote:
Hi,
another feature i forgot in the last mail :)
It would be great if batman allows to dynamic add and remove announced networks via the unix socket interface.
for example # adds new announced network batmand -c -a someip/mask # removes some announced network batmand -c -A someip/mask
I agree, and in terms of implementation complexity it shouldnt be too difficult. At least less painfull than dynamically adding and removing network interfaces. BTW: you can issue a ticket in TRACK ( https://dev.open-mesh.net/batman/newticket ) so that its not forgotten too fast and somebody is using this fancy tool.
why ? we are working on the posibility to give a computer in the mesh a unique ip, besides the network the node is serving. if you assign a unique ip to a computer, and get a dhcp lease of another node, the node would then add your ip as a hostroute announcement to batman, which would overwrite the default place: your home network. this would mean real mobile ip without the overhead of sending the traffic to your home router and then forward to your actual position.
Thats interesting but seems too complex for me, can you explain the approach in more detail.
From my understanding, Mobile ip means that a node is reachable by a unique
and not-changing IP address and independent from the current point of attachment to an access network. I do not understand how your mobile node can maintain TCP scessions with corresponding nodes in the GBI while switching the MESH-GBI GW.
ciao, axel
besides this, it would allow better integration into bgp by simply spawning a script to add/remove routes via zebra.
kindly regards daniel _______________________________________________ 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Axel Neumann wrote:
why ? we are working on the posibility to give a computer in the mesh a unique ip, besides the network the node is serving. if you assign a unique ip to a computer, and get a dhcp lease of another node, the node would then add your ip as a hostroute announcement to batman, which would overwrite the default place: your home network. this would mean real mobile ip without the overhead of sending the traffic to your home router and then forward to your actual position.
Thats interesting but seems too complex for me, can you explain the approach in more detail.
we here in leipzig freifunk will soon assign a network to people as house networks. we will later make it possible to assign ips to mac addresses. with the new dnsmasq you can run scripts, which would check the mac list. if he finds a mac, he will assign this ip, add a hostroute and would notify batman that this host is here via the interface i proposed. some checking must be done to remove those networks later, but thats a minor problem.
because hostroutes have higher priority then network routes, the notebook will be available as it should be.
the only problem i see so far is the growth of the routing table, but i think if this problem acutally makes impact, this could be fixed with using different routing tables. i never looked at the routing table implementation, if it would perform better if a ip rule + secound table or one big table is faster. i guess the first one.
From my understanding, Mobile ip means that a node is reachable by a unique
and not-changing IP address and independent from the current point of attachment to an access network. I do not understand how your mobile node can maintain TCP scessions with corresponding nodes in the GBI while switching the MESH-GBI GW.
i don't know if mobile ip means roaming without breaking tcp connections, i think this is much harder. i think the posibilty that a computer is reachable through one ip in the complete network without useless routing is at least better then all the mobile ip stuff i have seen so far.
besides this, it would allow better integration into bgp by simply spawning a script to add/remove routes via zebra.
i looked at quagga but didn't found the posibility to add routes that way, so a small cron job/daemon will have to do this job...
b.a.t.m.a.n@lists.open-mesh.org
-
Axel Neumann -
Daniel Poelzleithner