ripd, multicast and route to 224.0.0.0/4

From: Eugene Grosbein (eugen_at_kuzbass.ru)
Date: 04/29/04

  • Next message: Karim Fodil-Lemelin: "Re: ipsec ipcomp between FreeS/WAN 2.04 and FreeBSD 5.2"
    Date: Thu, 29 Apr 2004 20:50:16 +0800
    To: net@freebsd.org
    
    

    Hi!

    Who is guilty: ripd or FreeBSD kernel? Or I am?

    My router has default route via its em4 interface (and there is eBGP session)
    and has to announce default route using RIPv2 to the network reachable
    through em3.

    So T configure ripd:

    router rip
      version 2
      network em3
    ! Just to be sure: em3 is configured as 172.20.2.75/24
      network 172.20.2.0/24
      default-information originate
      redistribute kernel
      redistribute static
      redistribute connected
    !

    It seems that ripd (I tried zebra and quagga from fresh ports) will
    send its multicast announces using the interface that a route to
    224.0.0.0/4 points to. So, ripd sends its RIPv2 multicast packets
    to my uplink network via em3 if the router does not have a specific
    route to 224.0.0.0/4 pointing to em3. Why? And what should I do
    if I will need to send RIPv2 to em0, em1, em2 and em3?

    Eugene Grosbein
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"


  • Next message: Karim Fodil-Lemelin: "Re: ipsec ipcomp between FreeS/WAN 2.04 and FreeBSD 5.2"

    Relevant Pages

    • Re: Second ISP
      ... make sure that the second ISP router does not have a better default ... All of this can be done with show ip route ... Does this require a routing ... but I would recommend a routing protocol. ...
      (comp.dcom.sys.cisco)
    • Re: Problem with IP Masquerade + routed internal network (pretty newbie question)
      ... The network looks like this: ... > other way to define routes other than typing route add... ... If you have a proper router set up, each box on each subnet should only ... would route everything to our factory WAN over frame relay. ...
      (comp.os.linux.networking)
    • Re: T43 Networking fix question.
      ... Try a static route to the router. ... I can PING the ZyXel router on 192.168.1.1 just fine that way. ... But then, no matter what combination of HOST or NET route addressing I create in the fixed address tables in the TCP/IP configuration panels, I can never ping anything other than the 192.168.1.1 private address side of the ZyXel router. ... When you go to look at the documents in the supplied Broadcom driver package, in their 'PROTOCOL.INI' sample, they provide for additional 'fields' at the bottom of it in the driver section. ...
      (comp.os.os2.misc)
    • Re: Routing through two DD-WRTs
      ... a lousy term for blocking any wireless to wireless traffic. ... I can happily route packets from hosts on .111 to .110 and .112, ... IP table are for firewall rules, not for routing. ... gateway (IP address of remote router). ...
      (alt.internet.wireless)
    • Re: Routing for Verizon FIOS -- Reward for answer
      ... The problem we have is this:  Verizon's gateway is 70.x.x.1. ... address for our router ...  What do we use as an address for the outside interface ... route outbound through the gateway. ...
      (comp.dcom.sys.cisco)