Re: in.c autoadding prefix route

From: Vladimir Grebenschikov (vova_at_fbsd.ru)
Date: 11/17/04

  • Next message: Ruslan Ermilov: "Re: in.c autoadding prefix route [PATCH]"
    To: Max Laier <max@love2party.net>
    Date: Wed, 17 Nov 2004 19:50:32 +0300
    
    

    В чт, 11/11/2004 в 21:24 +0100, Max Laier пишет:
    > All,
    >
    > I know I have sent this a couple of times before, but never got anywhere. This
    > time I am set to commit!
    >
    > The attached patch (http://people.freebsd.org/~mlaier/in.c.patch) derived from
    > WIDE via OpenBSD in.c, rev 1.21 improves the handling of automatic prefix
    > routes.
    >
    > Right now you can't have two legs into the same network. If you want to, you
    > must give on of the interfaces a host address only (netmask /32). This way it
    > is not possible to hand over the route if one of the interfaces is
    > "removed" (however this is done in the special case).
    >
    > The patch allows to add more than on IPv4 address with the same prefix. In the
    > case that there is a route already, we leave it alone and add the new address
    > without the IFA_ROUTE flag. When we remove an address later on, that has a
    > route associated, we try to find an alternative address to use for the route
    > and hand it over.
    >
    > This is required for CARP, but should be helpful for other situations as well.
    >
    > Any objections?

    This change actually broke one simple thing:

    # ifconfig lo0 alias 10.0.16.111/32
    # ping 10.0.16.111
    PING 10.0.16.111 (10.0.16.111): 56 data bytes
    ping: sendto: No route to host
    ^C
    #

    You should (anyway should) add routing of interface address itself to
    loop-back interface, like it usually done in all other cases.

    Please fix.

    -- 
    Vladimir B. Grebenchikov
    vova@fbsd.ru
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
    

  • Next message: Ruslan Ermilov: "Re: in.c autoadding prefix route [PATCH]"

    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: Win 2003
      ... ping the outside interface of the router ... Server is a member of the domain. ... IPv4 Route Table ... Interface List ...
      (microsoft.public.windows.server.general)
    • Re: sent an invalid ICMP type 11, code 0 error to a broadcast: 0.0.0.0 on lo?
      ... > If you ping an IP address on your computer, ... > the lo route filtering altogether. ... ICMP packet, with source address on this same box. ... IF that packet comes from the interface where the default ...
      (Linux-Kernel)
    • 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)