12 Jun
2015
12 Jun
'15
10:38 a.m.
Marc, that is a completely different case.
The problem is the fact that first of all, IPIP tunnels can not be point to
multipoint (you get an error if the remote tunnel endpoint is not
specified).
Second, on Mikrotik, the route can not be bound to a specific interface lik
in 'ip route' since it does not have the 'dev' parameter. Destination is
either an IP or an interface. One can not have both.
And third, if the gateway is not resolvable by a previous specific route
(like in your example), then the system will issue an ARP, get no response
and mark the route inactive.
On linux systems, this is solved by adding the parameter "onlink" to the
route, which is not possible on RouterOS.
And of course, there is the big issue, if all those could be solved, does
the IPIP driver consider the route an endpoint directive (like on regular
Linux) or just an ordinary route, but this is of no importance right now -
it probably does since it is a modern kernel.
Marius, YO2LOJ
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Marc,
LX1DUC
Sent: Friday, June 12, 2015 11:28
To: AMPRNet working group
Subject: Re: [44net] Strange Broadcasts...
(Please trim inclusions from previous messages)
_______________________________________________
RouterOS cannot handle this, but Linux can. E.g.:
node has subnet 44.137.40.0/23 and has address 44.137.41.254
user has subnet 44.137.41.96/28 and has address 44.137.41.110 on eth0
then:
ip route add 44.0.0.0/8 dev eth0 gw 44.137.41.254 onlink
To do this in RouterOS (and in many other routers) you need to set the
subnet mask
to /23 on the eth0, but that means it will try to contact the others
directly, not routing via the node.
This will work when the local area is switching/bridging.
Otherwise you will need to have a node address in everyone's subnet.
The same situation occurs when setting up the P2MP IPIP tunnel
interface: you assign it the
subnet of your local system, so all the routes are outside the
interface's subnet and need
the "dev" and "onlink" parameters. RouterOS does not support them.
But Linux does.
You might not have found the solution yet. But RouterOS DOES support PtP
addressing on PtMP interfaces.
/ip address add 44.137.41.110/32 network=44.137.41.254 interface=ether1
/ip route add dst-address=44.0.0.0/8 gateway=44.137.41.254
73 de Marc, LX1DUC
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net