Re: Airport at boot


Subject: Re: Airport at boot
From: Charlie Watts (cewatts@frontier.net)
Date: Mon Nov 12 2001 - 12:32:14 MST


/etc/rc.d/rc.local is the -last- thing to happen at boot-time.

Network is brought up before rc.local is run.

If it tries to bring up network before your airport has been configured,
I'm not surprised it doesn't work.

The low-rent fix for this would be to just restart the network in
/etc/rc.d/rc.local after your card has been configured.

I suspect you can fix it correctly with /etc/modules.conf, though. You
can hardcode modules options in there much as you can pass them on the
command line. I'm not sure if all of the necessary options can be passed
there.

It might be as simple as adding:

alias eth1 airport

So that when you try to load eth1, the airport module is installed. This
is sufficient for me, using either static addressing or DHCP. If you have
to pass options to it, you're on your own.

This is my /etc/modules.conf; It may not all be useful or appropriate. I
like building as much in my kernel as modules as possible, so I think some
of this isn't necessary with Dan's kernels.

# Came with the system ...
alias sound-slot-0 dmasound_pmac
alias sound-slot-1 dmasound_pmac
alias sound-service-0-0 dmasound_pmac
alias sound-service-0-3 dmasound_pmac
alias sound-service-1-0 dmasound_pmac

# Networking stuff. I don't remember what.
alias net-pf-17 af_packet
alias net-pf-4 null
alias net-pf-5 null

# Make sure requests for ethernet load
# the correct modules
alias eth0 gmac
alias eth1 airport

# These shouldn't both be necessary.
# I suspect the second one is correct.
# macserial automatically loads the i2c
# stuff I need on my iBook 2001
alias /dev/ttyS0 macserial
alias char-major-4 macserial

# I don't usually need USB, when I do it's for a mouse.
# this way I can just say "modprobe mouse" and get both
# components
probeall mouse hid usb-ohci

On Mon, 12 Nov 2001, Scott Kellogg wrote:

> Thank for replying.
>
> It looks like our setup is different, though. I'm not using encryption on
> my network, so issuing modprobe with the network name is sufficient to get
> the network running. I think the problem may be that it takes a little
> while for the DHCP server to hand out a lease, and rc.local doesn't want
> to wait to get one.
>
> If there a way to get rc.local to wait until it gets an IP to continue?
>
> /Scott
> On Mon, 12 Nov 2001, Joe Buczek wrote:
>
> >Here's what I added to rc.local that works for me. I'm
> >running YDL 2.1 on an Icebook 2001:
> >
> >##################################################
> ># Bring up the Airport card
> >##################################################
> > echo "Airport: initializing..."
> > /sbin/modprobe airport
> > iwconfig eth1 essid "MyNetwork"
> > echo "Airport: configured"
> >
> >I wasn't aware you could pass the essid to the airport
> >module when loading it, as you do. Perhaps my script
> >is braindead, but hey, it works on my machine!
> >
> >--Joe
> >
> >
> >--- Scott Kellogg <scott@kiva.net> wrote:
> >> Hello list -
> >>
> >> I am running kernel 2.4.10a (I think, I'm on a
> >> different box right now)
> >> and have successfully configured Airport. I did
> >> this by adding
> >>
> >> /sbin/modprobe airport network_name "MyNetwork"
> >>
> >> to /etc/rc.d/rc/local. Also,
> >> /etc/sysconfig/network-scripts/ifcfg-eth1 is
> >> associating the interface to a DHCP server.
> >>
> >> When I boot, during initialization of eth1, I get
> >> the message
> >> "Initialization delayed" and a red "failed" instead
> >> of a green "OK" in the
> >> status column.
> >>
> >> Once I get to level 5 login, I login and open a
> >> terminal. I can bring the
> >> network up by issuing "service network restart".
> >> What gives? I'd like
> >> the interface to receive an IP upon boot.
> >>
> >> Thanks,
> >> Scott Kellogg
> >> --
> >> The Grateful Dead was never five or six guys on a
> >> stage;
> >> it was everybody in the room.
> >>
> >>
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Find a job, post your resume.
> >http://careers.yahoo.com
> >
>
>

-- 
Charlie Watts
cewatts@frontier.net
Frontier Internet, Inc.
http://www.frontier.net/



This archive was generated by hypermail 2a24 : Mon Nov 12 2001 - 12:44:09 MST