28 Jul
2013
28 Jul
'13
6:40 p.m.
On Sun, Jul 28, 2013 at 1:51 AM, Marius Petrescu <marius(a)yo2loj.ro> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Just a small correction. Classic RIP uses the rip senders address as the
gateway...
To clarify it by example:
Let's take my own RIP entry coming via interface tun0 which has IP address
44.182.21.1:
IP address: 44.182.21.0 netmask: 255.255.255.0 nexthop: 89.122.215.236
metric: 1
Sender is 44.0.0.1
the convetional processing will give:
44.182.21.0/24 via 44.0.0.1 dev tun0 proto zebra metric 20
rip44d will create the following entry:
44.182.21.0/24 via 89.122.215.236 dev tun0 window 840
Marius, YO2LOJ
If the true next hop is known then why does ripd not use it? what is the
rfc compliant and thus proper behavior for how and where packets are sent
on to when using rip?
Eric