16 May
2013
16 May
'13
8:45 a.m.
On Thursday 16 May 2013 09:43:49 Axel Neumann wrote:
1) the support of bidirectional tunnel (currently bmx6
uses two
unidirectional (one-way tunnels) for
gw and network (anycast like) routing over the unicast end-to-end
routing between each gw-client to gw peer.
These tunnels are setup on-demand (only when gw-client's user traffic is
send) and
a benefit here would be that gw-client nodes could trigger the setup of
these tunnels in both direction
and according to the best path perceived by the client.
so at moment just the tunnel from client to gw is according client perspectve
and the one from gw to client is according to gw perspective?
It is not a good thing ?
2) to support virtual (overlay) links on top of an
existing network by
specifying a remote ip address instead of a interface for meshing.
This way, it would be easily possible to interconnect clouds that have
no direct link between each other (eg over the internet, similar to what
tinc or other VPNs are doing).
This would be very good and give to bmx6 a lot of advantages in respect to
other routing protocol :D