05-08-07 06:13 PM
On May 7, 10:08 am, Hans Poppe <hpo...@online.no> wrote:
> Hi, thanks for the suggestion. I've tried to remove eth1394 and reboot, no
> change. This is a laptop that doesn't have FireWire, and thus this should
> not have been "dicovered" during installation(?).
I guess it is discovered during boot, prob. It isn't in "lsmod" list,
is it?
I would guess that it is not the problem that your WiFi wasn't
discovered during installation. I guess that it's becouse Debian
can't distribute the firmware for it. So the WiFi didn't (couldn't)
work during installation. But this is speculation, as I don't have any
laptop with ipw22000 to test on.
Any way, it shouldn't be any problems with having eth0 like this. I
have this in my laptop, and have no problems with it, what so ever. I
plug and play with both wired and wireless lan without that disturbing
anything (unless you try to start eth0 from /etc/network/interfaces
which obvious is wrong in this case). I am running Etch on HP
Pavillion zd8000 model.
> Anyway, is there a reason for FireWire to use this, obviously, incorrect M
AC
> address? If it were in a network using ieee1394, would ARP-ing for this
> machine work?
Don't know. I have not tried to use FIreWire net, no cabel or other
computer to test on. But that should beat the crap out of USB2 for
file transfer any way (if it works :-) )
I have READ that it exists a profile that should work like a network
over FireWire (or am I mixing this up with bluetooth :-) )
> Regards
>
> Hans Poppe
Anyway, IF you want to rename your interfaces, you can do that in "/
etc/udev/rules.d/z25_persistent-net.rules", which is the Debian way.
(search in http://wiki.debian.org/)
But be carefull! Wrong naming and/or not updating your configurations
(like /etc/network/interfaces or /etc/ethers), you will have problems
starting networks on your machine.
I would recommend naming your wired ethernet (now eth2) to "lan" and
your wireless to (now eth1) "wlan" and your FireWire (now eth0) to
"firewire" or something like that. So you can easy identify them in
logs and so on.
By the way, if you are running true portable (different nets now and
then) and using Gnome (ro KDE, but not tested), you rather get network-
manager set up your network for you, works REALY smooth. You need
package network-manager-gnome or network-manager-kde for this to work.
On stational machines and servers you should NOT install this package,
as it needs a user to be logged in to start a connection. And that
would be bad in those cases, as with a webserver :-)
Good luck
[ Post a follow-up to this message ]
| 
