On Wed, 29 Jan 2003, Alex Chudnovsky wrote:

> On Wednesday 29 January 2003 21:42, David Harel wrote:
> > Alex,
> >
> > I posted a message to you and the group regarding my findings about the
> > cable modem (attached below)
> I saw it, I just had no time to answer, sorry.
> >
> > Since I did not receive any reply I presumed I failed to send it. Could you
> > verify that you got it and can you figure out how to help me in this
> > matter?
> >
> > The updated request.
> > Thanks everyone who replied, (it always gets me by a surprise that so many
> > people are kind enough to
> > spend their time and answer)
> >
> > OK, things are a little more difficult.
> >
> > To begin, with I failed to describe my machine. It is an HP omnibook
> > laptop. It has network card built
> > into it and a single USB port to which I hooked a USB HUB. I am running
> > Linux RH 8.0.
> > Since I jammed the linux installation I reinstalled everything from scratch
> > (while the cable modem is
> > connected to the USB via the HUB).
> > In the installation process I was prompted for eth0 only. I gave it IP
> > address 10.0.0.1
> >
> > It took me a while to figure out that after boot, eth0 is the USB cable
> > modem. I was not able to
> > reference eth1 at all.
> The following in /etc/modules.conf may help
>
> alias eth0 the_built_in_network_card_driver
> alias eth1 CDCEther

May, or may not.

Those aliases are used by RH and Mandrake in the networking startup.

/etc/init.d/network start calls 'ifup [interface]' for any interface that
should come up automatically
(/etc/sysconfig/network-scripts/ifcfg-[interfce] has ONBOOT=yes) . The
ifup script will first run 'modprobe [interface]' (e.g: 'modprobe eth0').

This can fail in a number of ways.

If you're having problems with that, create an additional init.d script
that has an empty 'stop' and 'restart' (maybe copy /etc/init.d.keytable )
that will load the relevant modules, by modprobe/insmod .

Alternatively, you can always edit /modules.conf and
/etc/sysconfig/network-scripts/ifcfg-eth*

Alternatively, don't havethem start ONBOOT . Have only loopback started
automatically. The ethernet adapters will be started later by your init.d
script. (this means, though, that this script is now responsible for
shutting them down). [messy, I know]

>
> >
> > What I do to make it work is:
> >
> >    1.Stop network operations by the command:  /etc/init.d/network stop
> >    2.Disconnect the cable modem from  the USB hub.
> >    3.Start eth0 manually by the command:  ifconfig eth0 10.0.0.1 netmask
> > 255.255.255.0 up

'ifup eth0' ?

May require 'ifdown eth0' beforehand.

> >    4.Reconnect the cable modem to the USB hub.
> >    5.I fiddle a little with the start/stop of /etc/init.d/network and
> > vualla. eth0 is the network card and
> >      eth1 is the usb cable modem.
> >
> > I would like it to go smoothly on boot time without fiddling that much.
> > Also I would like to figure out
> > which eth? is to which physical hardware thing.
>
> Driver that detects its hardware first ( meaning usually driver that is loaded
> first, except USB, PCMCIA and other hotplugs ), gets eth0. And I HATE THIS
> WAY, as it doesn't play well with hotplugging. This stupidity should have
> been improved before long.

How else can you identify eth0?

-- 
Tzafrir Cohen
mailto:[EMAIL PROTECTED]
http://www.technion.ac.il/~tzafrir


=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to