Re: ipv6 host routes

On Mon, Oct 02, 2006 at 05:19:12PM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
I should have looked at it much earlier (sorry about the delay), but I
don't this change is correct. This will easily bother statically
installed route (especially) on a point-to-point interface.

No problem if I can get your help now. :-)

The key point here is whether the route is statically created or not.
And, if I understand your intent correctly, the host route you want to
install is not really "static" in that it can (or should) be removed
when it's detected to be unreachable, right?

Maybe I should state what I want to achieve again.

What I'm trying to do is to add a host route to a machine directly
connected. It sounds stupid because you normally don't need it, but
I'm busy porting net/olsrd to FreeBSD/IPv6. Currently it only have
linux ipv6 support. Olsrd is a mesh routing protocol used in adhoc
wireless networks. The one reason you want to add these routes is
because you might have more than one wireless interface on the
same subnet, covering different areas. So you need to add a route
to the interface that can talk to the host. So after some struggling
and questions on freebsd-net, I came up with code that do the
equivalent of: "route add -inet6 <dest_ip> <my_ip_on_that_if> -interface
-ifp <ifname> -llinfo -nostatic" in olsrd and this patch. If there
is an easier way, I would love to use it. I would have liked if
something simple like "route add -inet6 <dest_ip> -interface <ifname>"
did work on "normal" interfaces like ethernet and wireless interfaces
too.

Olsrd will remove the route again when it isn't needed or correct
anymore, so there is no need for it to be removed by the OS. It
probably shouldn't be marked static either because routing deamons
do not normally do that.

John
--
John Hay -- John.Hay@xxxxxxxxxxxxxxxxx / jhay@xxxxxxxxxxx
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Cant send packets via WiFi (possibly route issue)
    ... I think that this WiFi device should route all ... it should *all* be routed to the eth1 interface. ... Wireless is much like a point-to-point link using ... The connection between the two networks is the "Wifi AP". ...
    (comp.os.linux.networking)
  • RE: Running public IPs inside an RFC 1597 network
    ... > I'm running a typical Class C RFC 1597 network in my lab. ... know or care if we humans designate a subnet as public or private. ... is the absolute most general route there is for a machine. ... In a correctly configured system when you define an interface, ...
    (freebsd-questions)
  • Equal cost paths from separate OSPF Processes
    ... the network statements are valid in all OSPF processes. ... interface Serial0.300 point-to-point ... router#sh ip route ospf ... connected, includes subnets in redistribution ...
    (comp.dcom.sys.cisco)
  • Re: panic in rt_check_fib()
    ... It dropped a the lock on one route while it went off an did something ... then brings up the wired interface of my laptop. ... echo '## Bringing up network interface.' ... With your version of rt_check_fibI have no panics so far. ...
    (freebsd-current)
  • kludgily solved: bridge with access on both interfaces
    ... address on each interface that is only accessible ... from its own interface side of the bridge - which is actually what we ... there are some checks in the ARP code ... wound up having better luck with route, though it was still a struggle ...
    (freebsd-net)