All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dror Goldstein" <drgoldst@cisco.com>
To: lartc@vger.kernel.org
Subject: [LARTC] transport multicast traffic through  a gre tunnel.
Date: Thu, 15 Mar 2001 09:27:27 +0000	[thread overview]
Message-ID: <marc-lartc-98465965412741@msgid-missing> (raw)

Hi All,

As it is written in the "Linux 2.4 Advanced Routing HOWTO"  GRE tunneling
has some benefits compare to IP-in-IP, on of it benefits is the ability to
transport multicast traffic through a GRE tunnel.
I used the  mrouted daemon and I know that the daemon supports tunneling but
I don't want to use its tunneling method.

Assuming I have gre0 as my tunneling device I did the following:

1. declare the following rules:
Ip rul add iif eth0 table 100 prio 100
Ip rul add to 240.0.0.0/4 table 101 prio 101

2. declare the following routing table
ip route add default dev gre0 tab 100
ip route add 224.0.0.0/4 dev gre0 tab 101

The result was that all multicast traffic was routed via the gre tunnel, but
the multicast traffic was not.

Can someone help me with that problem?
Did I do any mistake?
Is it possible to do that using Linux OS? As I saw in the ipv4 code handling
the multicast traffic is done before looking and the routing tables and
rules is it true?

Is it possible to transport also broadcast traffic to the tunnel?

Actually what I really want is to forward all the traffic (unicast,
multicast, and broadcast) that came from eth0 to tunnel gre0, is it
possible? If yes then how?

Thanks
Dror G.



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-03-15  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  9:27 Dror Goldstein [this message]
2001-03-15 11:35 ` [LARTC] transport multicast traffic through a gre tunnel bert hubert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-98465965412741@msgid-missing \
    --to=drgoldst@cisco.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.