From: armin langhofer <office@langhofer.at>
To: bridge@lists.osdl.org
Subject: [Bridge] bridge with ppp0, ppp1,..
Date: Sat, 18 Dec 2004 21:32:21 +0100 [thread overview]
Message-ID: <41C493D5.4080404@langhofer.at> (raw)
hi there
i found your project and tried to bridge two ppp devices.
you say (http://bridge.sourceforge.net/faq.html) that this is possible:
... "Linux bridging is very flexible; the LAN's can be either
traditional Ethernet device's, or pseudo-devices such as PPP, VPN's or
VLAN's. The only restrictions are that the devices:" ...
i tried this but got "br_add_interface: Invalid argument" when adding a
ppp device to the bridge. adding an ethernet device works perfectly!
00:07:21 protector ~ # brctl addbr br0
00:07:22 protector ~ # brctl addif br0 eth2
00:07:30 protector ~ # brctl addif br0 ppp0
br_add_interface: Invalid argument
the ppp's are done with pppd and pptpd (poptop)
00:09:39 protector ~ # pppd --version
pppd version 2.4.2
00:09:44 protector ~ # pptpd --version
PoPToP v1.1.4-b4
any ideas?
best regards, armin.
--
armin langhofer
snail: fischer von erlachstr. 29
snail: a-5020 salzburg
phone: +43 699 11648495
email: office@langhofer.at
gnupg: http://langhofer.at/pubkey.txt
reply other threads:[~2004-12-18 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41C493D5.4080404@langhofer.at \
--to=office@langhofer.at \
--cc=bridge@lists.osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox