• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Fedora: How to setup a firewire network connection?

S

statik213

Golden Member
I've got firewire controllers on both machines windows is seeing the firewire card as a network connection. On the fedora machine the firewire controller is detected but does not show up as a ethernet connection, I'm seeing only eth0 and lo. How do I create a firewire network connection? I'm using FC3, planning on wiping the machine an upgrading to FC4, figured I'd learn how to do this before I upgraded (in case the steps involve screwing the machine up).

TIA

 
Originally posted by: n0cmonkey
modprobe eth1394

?
Click to expand...

ok it did not do anything, no ouput.... ifconfig does not show a new adapter either.

tried this:

[root@phoenix ~]# modprobe -v eth1394
got:
install /bin/true

umm, what next?

 
[root@phoenix ~]# lsmod | grep 1394
ohci1394 39129 0
ieee1394 309145 1 ohci1394
[root@phoenix ~]# !mod
modprobe -v eth1394
install /bin/true
[root@phoenix ~]# lsmod | grep 1394
ohci1394 39129 0
ieee1394 309145 1 ohci1394


any ideas? dang it, i need to go to class.
will look into modprobe in detail when i get back.

thx n0cmonkey!
 
I donno about Fedora... I never tried to do firewire network connection, ever.

But I am using Debian unstable with 2.6.13 kernel. On my audigy sound card there is a firewire port...

It automaticly setup a eth* device for it. Just by default.

from this command:
ifconfig -a
output:
eth0 Link encap:Ethernet HWaddr 00:07:E9:0C:FA😀1
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe0c:fad1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:502690 errors:0 dropped:0 overruns:0 frame:0
TX packets:374811 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:542021767 (516.9 MiB) TX bytes:35687696 (34.0 MiB)
Base address:0xa800 Memory:e2000000-e2020000

eth1 Link encap:Ethernet HWaddr 00:E0:4C:A9:26:0A
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:193 Base address:0xc400

eth2 Link encap:UNSPEC HWaddr 00-02-3C-00-31-03-A7-2D-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7467588 errors:0 dropped:0 overruns:0 frame:0
TX packets:7467588 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2264854170 (2.1 GiB) TX bytes:2264854170 (2.1 GiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


Eth0 is my intel 10/100/1000 pci card.
Eth1 is my onboard 10/100 via device
Eth2 is my firewire network device
lo is loopback (ie 127.0.0.1)
sit0 is something like ipv6 over ipv4

the only active interface that I have right now is...
~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:07:E9:0C:FA😀1
inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe0c:fad1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:502698 errors:0 dropped:0 overruns:0 frame:0
TX packets:374819 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:542022315 (516.9 MiB) TX bytes:35688244 (34.0 MiB)
Base address:0xa800 Memory:e2000000-e2020000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7467948 errors:0 dropped:0 overruns:0 frame:0
TX packets:7467948 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2264963790 (2.1 GiB) TX bytes:2264963790 (2.1 GiB)


The driver/kernel module for the firewire do-dad is eth1394
and that sets up the eth* device for the firewire connection.

In order to then use it you'd just have to configure it like you would thru any normal ethernet device. In my system it's autodetected and is ready to be used in that fasion.

Hope that helps. If you don't have eth1394 maybe try upgrading your kernel with a newer fedora kernel, if that doesn't help or your completely up-to-date then try to get help in the fedoraforum.org or some other fedora-specific place. Recompiling the kernel would be a last resort.


edit:

If you don't know which eth* device is which you have to use the the dmesg command.

Dmesg command outputs the recently outputed kernel logs... so if you have rebooted recently you can find out stuff about how the hardware is setup.. If you haven't rebooted in a while then the logs from when the system was setup will be to old to be found by the dmesg command. In that case the logs will be found in /var/log and the file is called messages. In order to prevent the files from being to big their is a log rotation that goes on that automaticly copies the log file to a different name.

So you can do things like:

sudo dmesg |grep eth

or
sudo cat /var/log/messages |grep eth
sudo cat /var/log/messages.0 |grep eth
sudo zcat /var/log/messages.1.gz |grep eth

(the last file was compressed with gzip to save space.)

By at leaste grepping thru the /var/log/messages you will find out what eth device goes to what physical device.

Hope that helps.
 
Well, I added my firewire card after installing Fedora. The firewire controller isn't showing up as a nework device, see:
[root@phoenix ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10😀C:C8:6F:83
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210😀cff:fec8:6f83/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4060 errors:0 dropped:0 overruns:0 frame:0
TX packets:7506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1183757 (1.1 MiB) TX bytes:6305323 (6.0 MiB)
Interrupt:11 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4060 errors:0 dropped:0 overruns:0 frame:0
TX packets:4060 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4873528 (4.6 MiB) TX bytes:4873528 (4.6 MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Click to expand...

I can configure it if it comes up as en eth* device, but I don't know how to get it to become an eth* device.
Any ideas?
 
The driver/kernel module for the firewire do-dad is eth1394
and that sets up the eth* device for the firewire connection.

In order to then use it you'd just have to configure it like you would thru any normal ethernet device. In my system it's autodetected and is ready to be used in that fasion.

Hope that helps. If you don't have eth1394 maybe try upgrading your kernel with a newer fedora kernel, if that doesn't help or your completely up-to-date then try to get help in the fedoraforum.org or some other fedora-specific place. Recompiling the kernel would be a last resort.
Click to expand...
 
[root@phoenix ~]# !mod
modprobe -v eth1394
install /bin/true
[root@phoenix ~]
Click to expand...

According to that it never loaded the module, it ran /bin/true instead. RH/FC must disable the module by default for some reason. Most likely it's in /etc/modprobe.conf or /etc/modprobe.d/*
 
Originally posted by: Nothinman
[root@phoenix ~]# !mod
modprobe -v eth1394
install /bin/true
[root@phoenix ~]
Click to expand...

According to that it never loaded the module, it ran /bin/true instead. RH/FC must disable the module by default for some reason. Most likely it's in /etc/modprobe.conf or /etc/modprobe.d/*
Click to expand...


Good catch..

I think that's a common hack people do so that the firewire device doesn't accidently grab eth0 device during bootup and confuse the users/network scripts.
 
I think that's a common hack people do so that the firewire device doesn't accidently grab eth0 device during bootup and confuse the users/network scripts.
Click to expand...

And it's really dumb, they should just use /etc/iftab and ifrename to change the interface name to fweth0 or something.
 
Originally posted by: Nothinman
I think that's a common hack people do so that the firewire device doesn't accidently grab eth0 device during bootup and confuse the users/network scripts.
Click to expand...

And it's really dumb, they should just use /etc/iftab and ifrename to change the interface name to fweth0 or something.
Click to expand...


yes. yes it is. But fedora has been known to stupid crap like that time to time. There should be a way to use udev or sysfs or whatnot in a clever way to make sure the device numbering stays consistent also.. not that I'd know how to do it or anything like that.

The offending line to look for would be:
install eth1394 /bin/true

or something similar.

either in the /etc/modprobe.conf or one of the files in /etc/modprobe.d/ directory, like you said. If that's what FC4 uses. By commenting that out it should cause the modprobe eth1394 to work now.
 
[root@phoenix ~]# cd /etc/
[root@phoenix etc]# cat modprobe.conf
1 alias eth0 forcedeth
2 alias snd-card-0 snd-intel8x0
3 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || :
4 remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
5 alias usb-controller ehci-hcd
6 alias usb-controller1 ohci-hcd
7 alias ieee1394-controller ohci1394
[root@phoenix etc]#
Click to expand...

don't see anything in there abt eth1394.

I ran kudzu and it asked me if it should install the IEEE1394 controller, I said yes, restarted and stuff... still no change.
any ideas?
 
Originally posted by: n0cmonkey
grep -r 1394 /etc/*

Maybe we'll find out where it's remapping that module or something.
Click to expand...



/etc/firmware/microcode.dat:0x7a9ad6c9, 0x53afb816, 0x58694a97, 0xb13942 97,
/etc/firmware/microcode.dat:0x9e861394, 0x075d4c73, 0xa569faf6, 0x396bae 73,
/etc/hotplug/ieee1394.agent:# IEEE1394-specific hotplug policy agent.
/etc/hotplug/ieee1394.agent:# This should handle 2.4.10 (or later) IEEE1394 hotplugging, with a
/etc/hotplug/ieee1394.agent:# Kernel IEEE1394 params are:
/etc/hotplug/ieee1394.agent:# $Id: ieee1394.agent,v 1.12 2004/03/13 18:49:45 ukai Exp $
/etc/hotplug/ieee1394.agent:MAP_CURRENT=$MODULE_DIR/modules.ieee1394map
/etc/hotplug/ieee1394.agent: mesg Bad IEEE1394 agent invocation
/etc/hotplug/ieee1394.agent:# stdin is "modules.ieee1394map" syntax
/etc/hotplug/ieee1394.agent:ieee1394_map_modules ()
/etc/hotplug/ieee1394.agent:# What to do with this IEEE1394 hotplug event?
/etc/hotplug/ieee1394.agent: LABEL="IEEE1394 product 0x$VENDOR_ID/0x$SPECIFIER_ID/0x$VERSION"
/etc/hotplug/ieee1394.agent: load_drivers ieee1394 $MAP_CURRENT "$LABEL"
/etc/hotplug/ieee1394.agent: ieee1394_map_modules < $MAP_CURRENT
/etc/hotplug/ieee1394.agent: if [ -x $HOTPLUG_DIR/ieee1394/$MODULE ]; then
/etc/hotplug/ieee1394.agent: $HOTPLUG_DIR/ieee1394/$MODULE
/etc/hotplug/ieee1394.agent: debug_mesg "IEEE1394 '$ACTION' event not supported"
Binary file /etc/hotplug.d/default/05-wait_for_sysfs.hotplug matches
/etc/hotplug.d/default/default.hotplug:# Examples: usb, pci, isapnp, net, ieee1394, printer, disk,
grep: /etc/httpd/run/iiim/.iiimp-unix/9010: No such device or address
grep: /etc/httpd/run/sdp: No such device or address
grep: /etc/httpd/run/dbus/system_bus_socket: No such device or address
grep: /etc/httpd/run/.iroha_unix/IROHA: No such device or address
grep: /etc/httpd/run/acpid.socket: No such device or address
Binary file /etc/ld.so.cache matches
/etc/makedev.d/linux1394:# video1394 devices, from http://www.linux1394.org/video1394.php
/etc/makedev.d/linux1394:c $ROOT 171 0 1 1 raw1394
/etc/makedev.d/linux1394:c $ROOT 171 16 1 4 video1394/%d
/etc/makedev.d/linux1394:# dv1394 devices, from http://www.linux1394.org/dv1394.php
/etc/makedev.d/linux1394:c $ROOT 171 32 4 4 ieee1394/dv/host%d/NTSC/in
/etc/makedev.d/linux1394:c $ROOT 171 33 4 4 ieee1394/dv/host%d/NTSC/out
/etc/makedev.d/linux1394:c $ROOT 171 34 4 4 ieee1394/dv/host%d/PAL/in
/etc/makedev.d/linux1394:c $ROOT 171 35 4 4 ieee1394/dv/host%d/PAL/out
/etc/makedev.d/linux1394:# amdtp, from http://www.linux1394.org/amdtp.php
/etc/makedev.d/linux-2.6.x:# 171 is used by various ieee1394 drivers. See http://www.linux1394.org/ for
/etc/modprobe.conf:alias ieee1394-controller ohci1394
/etc/modprobe.conf.dist:install eth1394 /bin/true
/etc/pcmcia/ieee1394.opts:# IEEE1394/FireWire Device Configuration
/etc/pcmcia/ieee1394.opts: INFO="Sample IEEE1394/FireWire setup"
/etc/pcmcia/ieee1394.opts: LOAD_1394RAW=yes
/etc/pcmcia/ieee1394:# ieee1394 1.00 2000/09/07 21:02:09 (Albrecht Dre\uffff)
/etc/pcmcia/ieee1394:# Initialize or shutdown a IEEE1394/FireWire device
/etc/pcmcia/ieee1394: if is_true $LOAD_1394RAW ; then
/etc/pcmcia/ieee1394: modprobe raw1394
/etc/pcmcia/ieee1394: if is_true $LOAD_1394RAW ; then
/etc/pcmcia/ieee1394: modprobe -r raw1394
Binary file /etc/prelink.cache matches
/etc/readahead.files:/usr/share/applications/kde/kcmview1394.desktop
/etc/sane.d/coolscan2.conf:# For an IEEE 1394 scanner, use the SBP2 protocol (under Linux, use the
/etc/security/console.perms:[raw1394]=/dev/raw1394 ***
/etc/security/console.perms:[console] 0600 [raw1394] 0600 root ***
/etc/sysconfig/hwconf:driver: ohci1394
/etc/sysconfig/hwconf:desc: "VIA Technologies, Inc. IEEE 1394 Host Controller"

*** The sqr brackets shud be angle brackets, changed b/c fusetalk throws a hissy fit when it sees html like tags.
 
Ok, etc/modprobe.conf.dist:install eth1394 /bin/true . In the file /etc/modprobe.conf.dist, try commenting out the line install eth1394 /bin/true .

EDIT: Remember to modprobe the driver afterwards though.
 
Originally posted by: n0cmonkey
Ok, etc/modprobe.conf.dist:install eth1394 /bin/true . In the file /etc/modprobe.conf.dist, try commenting out the line install eth1394 /bin/true .

EDIT: Remember to modprobe the driver afterwards though.
Click to expand...



eth0 Link encap:Ethernet HWaddr 00:10😀C:C8:6F:83
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210😀cff:fec8:6f83/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5998 errors:0 dropped:0 overruns:0 frame:0
TX packets:10085 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1304816 (1.2 MiB) TX bytes:9068792 (8.6 MiB)
Interrupt:11 Base address:0xe000

eth1 Link encap:UNSPEC HWaddr 13-94-04-09-22-00-10-6D-00-00-00-00-00-00-00-00
inet addr:192.168.1.201 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:188 (188.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2694 errors:0 dropped:0 overruns:0 frame:0
TX packets:2694 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3393613 (3.2 MiB) TX bytes:3393613 (3.2 MiB)
Click to expand...
thx n0cmonkey, eth1394 is showing up now but the machines aren't talking with each other yet.
I:\Documents and Settings\KZ>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : chimera
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes

Ethernet adapter Bluetooth Network:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physical Address. . . . . . . . . : 00-E0-98-FD-B8-D8
Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Unibrain 1394 FireNet Adapter
Physical Address. . . . . . . . . : 00-49-4E-55-4E-49
Click to expand...
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-A7-80-FB
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Click to expand...
windows says that the cable is unplugged.... aaargh...
but getting close.... thx guys!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top