From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] broadcast over gre tunnel?
Date: Tue, 22 Jul 2003 23:36:57 +0000 [thread overview]
Message-ID: <marc-lartc-105891714112142@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105891587611071@msgid-missing>
Martin Klewitz wrote:
>
> I think the routing is ok. For example I can ping 192.168.1.86 from
> 192.168.2.21 and the other way round, too.
> But I want to enable all lan features - the window boxes should find the
> window boxes in the other network in their "network neighborhood".
> What do I have to do, to implement this "feature"?
> Is this even possible?
>
You're half-way there - you just need to change your subnets, and use bridging.
You need to bridge your lan interfaces to the gre interface on both ends,
and then you also need both networks the same.
Then all PCs at both ends should think they're on the same network,
and broadcast packets will go everywhere.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-22 23:36 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 [this message]
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
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-105891714112142@msgid-missing \
--to=damion@snapgear.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.