Re: ipv4 over firewire
- From: Maxim Levitsky <maximlevitsky gmail com>
- To: Dan Williams <dcbw redhat com>
- Cc: "networkmanager-list gnome org" <networkmanager-list gnome org>
- Subject: Re: ipv4 over firewire
- Date: Sat, 08 Aug 2009 14:32:49 +0300
On Fri, 2009-08-07 at 17:06 -0500, Dan Williams wrote:
> On Fri, 2009-08-07 at 03:26 +0300, Maxim Levitsky wrote:
> > Hi,
> >
> >
> > For debugging purposes, I have set up a firewire connection between my
> > desktop and laptop. But it so happens, that it is nice to use it as a
> > network link, and it has about 12 Mbytes/s rates, more that enough for
> > me. (ethernet port on desktop is used for main network connection, and
> > laptop connected wirelessly)
> >
> > It seems that NM ignores the firewire eth1394. and newer firewire-net.
> >
> >
> > Is that true?
>
> Probably. There's nothing that says we couldn't add support for it, but
> I think there's just some missing bits for recognizing the bus type or
> something.
>
> Got a pointer guide on how to set it up in Linux that I could take a
> look at? I might at least be able to narrow down where NM is ignoring
> the device.
I have used this:
http://howto.krisbuytaert.be/FireWireClustering/x57.html
First I load eth1394 on both systems (it is blacklisted by default)
then, just
ifconfig eth1 10.0.0.1/24 up
Notes:
1 - eth1394 doesn't report the link status, in fact it doesn't support
any ethernet extensions (ethtool).
2 - eth1394 doesn't recover from link failure (eg if you unplug the
cable), thus I use ifconfig down , then up to recover, on one of the
sides, second one recovers automaticly.
3 - nether this driver support suspend/resume. I have to reload
ohci1394, to recover.
Newer, very new driver firewire-net, doesn't have problem #2, maybe #3,
but still doesn't report link status (it is unstable - low speeds, and
oopses now)
Best regards,
Maxim Levitsky
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]