From: Yuval Kogman <nothingmuch@woobling.org>
To: bridge@lists.osdl.org
Subject: [Bridge] eth1394 interface support?
Date: Wed, 11 Aug 2004 18:16:31 +0300 [thread overview]
Message-ID: <20040811151631.GA12305@woobling.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
I have a linux box which sits in the living room and plays
ti^H^Hfreevo.
Among other things it also talks to the cable modem via interface
eth0, and does NAT transformations for eth1.
Yesterday i was sitting in the living room with my laptop, thinking
about the fact that my wireless access point will only arrive next
week, and then remembered they both the laptop and the linux boxhave
firewire. The plot thickens.
I enabled bridging support in the kernel, and i got to
brctl addbr br0
brctl addif br0 eth1 # LAN interface
brctl addif br0 eth2 # firewire interface
br_add_interface: Invalid argument
I reckon eth1394 is at fault, but I'd like to know what the bridge
code expects from it.
eth1394 on a different subnet works, and I can also manipulate the
routing table in funny ways. I'd like to not do that.
Thanks
--
() Yuval Kogman <nothingmuch@woobling.org> 0xEBD27418 perl hacker &
/\ kung foo master: /me sneaks up from another MIME part: neeyah!!!!!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-08-11 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 15:16 Yuval Kogman [this message]
2004-08-11 16:28 ` [Bridge] eth1394 interface support? Stephen Hemminger
2004-08-11 18:04 ` Yuval Kogman
2004-08-11 20:48 ` Chris Shaw
2004-08-11 23:36 ` Yuval Kogman
2004-08-11 23:56 ` Chris Shaw
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=20040811151631.GA12305@woobling.org \
--to=nothingmuch@woobling.org \
--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 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.