[ale] assigning ip to second interface

[Ray Knight - Clientlink]

> -----Original Message-----
> From: owner-ale at ale.org [mailto:owner-ale at ale.org]On Behalf Of Wandered
> Inn
> Sent: Tuesday, August 15, 2000 1:18 PM
> To: ale at ale.org
> Subject: Re: [ale] assigning ip to second interface
>
>
> Okay, everyone slap me in the head.  Sure enough it is a typo.  I meant
> to type 192.168.55.230.  Every time I looked at it I saw 230.
> Fortunately I was too lazy to type the command in to the previous email,
> so the cut and paste put in the exact thing that was getting passed
> (320).  I've made it a valid ip, and now things are good.  Thanks for
> pointing out the obvious.. :)
>
> Cleveland Flowe wrote:
> >
> > Wandered Inn wrote:
> > >
> > > Here is how it's called from the network script in /etc/rc.d/init.d:
> > >
> > > ifconfig eth0 192.168.255.220 broadcast 192.168.255.255 netmask
> > > 255.255.255.0 up
> > >
> > > ifconfig eth1 "192.168.55.320 broadcast 192.168.55.255 netmask
> > > 255.255.255.0 up
> > >
> > For eth1, 192.168.55.320 is not a valid address is this a typo?  This
> > will give you the 'unknown host' error.
>
> --
> Until later: Geoffrey		esoteric at denali.atlnet.com
>
> Microsoft != Innovation
> --
> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in
> message body.

As a software developer for 15 years I can't tell you how many times I've
made a similar bone-headed error.  It's always nice to have someone else
look things over, just for those times when you see what you thought you
wrote, not what's there.

Ray Knight
audilvr at speakeasy.org


--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.