All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Shaw" <chriss@watertech.com>
To: Yuval Kogman <nothingmuch@woobling.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] eth1394 interface support?
Date: Wed, 11 Aug 2004 16:56:53 -0700	[thread overview]
Message-ID: <078701c47ffe$e02b95b0$8805640a@chriss> (raw)
In-Reply-To: 20040811233614.GA17340@woobling.org

On Wed, Aug 11, 2004 at 13:48:17 -0700, Chris Shaw wrote:
> I shudder at the thought.... but... if you want bridging between 1394 and
> Ethernet or wireless interfaces, you can do it in W2K3 or WinXP...

Sadly.. ehm.I don't have windows.

=D

At first it occured to me that maybe some sort of NAT for mac
addresses may be implemented, but then I read your message that said

> You can also use ProxyARP which is a kludge but it can work, provided that
> 1394 under linux can do ARP in the usual 802 way...

Well, that just worked... Funky!

Now if i can only get routing to work "automatically"... Right now
that means messing with the host that forwards, adding specific
hosts to the firewire interface (because it's easier than the other
way), and flushing temporary routes on other hosts.

Maybe some scripting is in order, with unsolicitated arp happenning
for clients which join the firewire subnet, but it's late and i
don't want to get into another war right now.

> True hardware bridges/switches can bridge between wired/wireless,
> tokenring/Ethernet FDDI/Ethernet HIPPI/Ethernet, etc etc etc... It would
be
> cool if linux could do it for the firewalling capabilities and because
> hardware like that can be very expensive...

Check out a project called parprouted, it's a ProxyArp daemon that
automagically updates your ARP entries for you by using ARP queries from
other hosts! :)

    -Chris



      reply	other threads:[~2004-08-11 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 15:16 [Bridge] eth1394 interface support? Yuval Kogman
2004-08-11 16:28 ` 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 [this message]

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='078701c47ffe$e02b95b0$8805640a@chriss' \
    --to=chriss@watertech.com \
    --cc=bridge@lists.osdl.org \
    --cc=nothingmuch@woobling.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.