All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] broadcast over gre tunnel?
Date: Thu, 24 Jul 2003 14:49:43 +0000	[thread overview]
Message-ID: <marc-lartc-105905844709047@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105891587611071@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]


Hello,

Use vtund - vtun.sourceforge.net, it's quite more flexible than gre tunnels, 
and works fine with bridge-utils, too. You can use it to transport not only
IP, but other layer 3 protocols as well, it has compression and encryption.


On Thu, 24 Jul 2003 16:32:57 +0200
"Martin Klewitz" <martin@gamigo.de> wrote:

 : Hello Damion,
 : 
 : > There's some bridge howtos, and stuff in the kernel doco:
 : > http://www.tldp.org/HOWTO/HOWTO-INDEX/networking.html#NETBRIDGE
 : > linux/Documentation/networking/bridge.txt
 : The problem is, that bridge-utils don't work with a gre tunnel:
 : router:~ # brctl addbr br0
 : router:~ # brctl addif br0 eth1
 : router:~ # brctl addif br0 gre0
 : br_add_interface: Invalid argument
 : 
 : Is there any possibility to make bridge-utils work with a gre-tunnel?
 : Or are there any other bridging-methods?


-- 
________________________________________________________________________

So long, and thanks for all the fish!

Nickola

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-07-24 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 23:19 [LARTC] broadcast over gre tunnel? Martin Klewitz
2003-07-22 23:36 ` Damion de Soto
2003-07-23  8:59 ` Martin Klewitz [gamigo AG]
2003-07-23  9:38 ` Martin Klewitz
2003-07-23 23:39 ` Damion de Soto
2003-07-24 14:32 ` Martin Klewitz
2003-07-24 14:49 ` Nickola Kolev [this message]
2003-07-25  1:24 ` Damion de Soto

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-105905844709047@msgid-missing \
    --to=nikky@mnet.bg \
    --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.