The saga continues...
My external interface is a breezecom wireless card, in an ISA - PCMCIA
adapter board. The internal interface is an NE2000 compatible (ISA). PCI
did not exist when this box was built!
The problem I have is that the external interface gets loaded as eth1 rather
than eth0. The way I see it, the problem can't be corrected by changing the
load order in modules.conf because the following seems to be the course of
events:
boot process
modules.conf is read
modules for PCMCIA support are loaded (wireless card not yet loaded!)
module for NIC is loaded (becomes eth0)
modules.conf read is completed
card services for PCMCIA is run
wireless card module is loaded (wireless card is assigned eth1)
card services is completed
rest of boot
What I would need to do is have card services do it's thing before the NIC
gets loaded. But it can't happen until after the modules for PCMCIA are
loaded - this is a chicken-egg sort of thing!
This would mean either:
A) causing this to happen *during* the modules.conf process (between the
PCMCIA support and NIC load) or
B) not loading the NIC in modules.conf and doing it manually (with a script
I guess) after card services run.
I'm certainly no expert (!!!) but I would think the first idea is way too
tough to even contemplate. Perhaps the second is possible? If so, could
someone offer a suggestion as to how this would happen? I could probably
come up with the insmod information in the script if push came to shove, but
I don't know how to have the script called! Is this relatively straight
forward?
Perhaps this makes no difference - I've got the thing going in this reverse
fashion by changing the occurrences of eth0 to eth1 and vice versa in
network.conf. But the logging seems to be going full tilt now and I suspect
this reversal is the problem (?). It would be nice to fix it without
re-inventing the LRP wheel.
Thanks,
R Brock Nanson
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
