xiamin wrote:

> On Sun, 20 Jul 1997, Colin Wood wrote:
> > 2) The same way you got the first one up and running ;-)
> Ummmm, it just sort of worked... ;)

Really?  How strange.  I thought that you always needed something to get
it going (I certainly did).

> sn0 is the built in, I assume ae0 is the card.

Yes, ae0 is probably the card, unless you have a SONIC-based card, in
which case, sn1 will be the card.

> > Depending on what version of the /etc/netstart scripts you're running, you
> > probably have either a:
> > 
> > hostname.ae0  (the old way)
> > 
> > file or an:
> > 
> > ifconfig.ae0  (the new way)
> > 
> > file.  All you need to do is create the sn0 interface file and give it an
> > IP address in some way.  So, you'll wind up with:
> Hmmmm, I have neither of those, on the howto page, I can find the way to 
> do hostname.ae0, but as far as I can see, you just do
> inet name netmask
> But you don't set the ip address...

True, although I think you can.  I believe that it uses something like the
resolver to map the IP address to the name you give on the line above.

> sn0 is configured with dhclient, ae0 should be 10.0.0.1 or something.

Probably so.

> BTW ifconfig -l doesn't list ae0.

Hmmm...I assume that ae0 does show up in the autoconf messages at boot
time?  If so, it might be that ifconfig is broken.  Do you have an
sn1 show up at boot instead?  Perhaps you should file a bug with send-pr?
Can anyone else verify such behavior??

Later.

Colin