You know, Collins, it was pretty weird, and it went something like this: Suppose the
network was
down. Then if i tried to bring up the card with 'ifconfig eth1 netmask 255.255.255.0
192.168.1.1'
then the FIRST time i tried that it would reply with something like "SIOCSIFADDR:
Cannot assign
address" (i forget, it's been a long while). Then, i would do the exact command again,
right away,
and the SECOND time i did it, it would work! I still don't understand that one. That's
happened
to me a few times and usually after awhile it just settles in and starts working. Very
strange.
Any ideas?
j
PS. yes i am familiar with restarting various services, run levels, etc, and i love
not rebooting
my linux machine. I always get several opportunities to either roll my eyes back and
sigh or just
laugh when i'm over at my friend's, who always runs/crashes Windows 98 (not even 2k).
--- Collins Richey <[EMAIL PROTECTED]> wrote:
> On Tue, 3 Apr 2001 14:57:35 -0700 (PDT)
> John Wolford <[EMAIL PROTECTED]> wrote:
>
> <snips>
>
> > rebooted the linux machine (mdk
> > 7.1). For some CRAZY
> > reason, this worked and all of a sudden we were able to ping accross the
> > network. I"m convinced it
> > had something to do with the network card and linux not brining it up
> > properly (despite its
> > claims).
> >
> > If i were you i would:
> > 1. Configure everything the way it should be and if it doesn't work
> > reboot both machines to let
> > hte changes settle in.
>
> Unless you have some crazy kind of intermittent irq conflict with the NIC,
> you should never need to reboot linux to redrive the network
> configuration. Just
>
> su
> /etc/rc.d/init.d/network restart
>
>
>
>
> --
> Collins Richey
> Denver Area
>
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
