But things are still not working now. Before where at least 1 NIC was
working, now both interfaces are not showing up in netstat -i.
Not only that, the loopback device is also gone!
All i see in netstat -i is 'atl0' device.
I checked /etc/tcp and see that it has proper ifconfig statements.
The ifconfig call gives me 'ioctl SIGIOCGI...'
Please:
[a] How can the devices be successfully scanned by the os with mac
addresses and then disappear for ifconfig?
[b] How can the loopback device be gone?
Something has happened to SCO tcpip services. Does anyone recognize
these strange symptoms?
--
If possible please cc: response posts to jo...@adm.com as I do not always have
access to a news server; thanks!
Disclaimer: opinions expressed my own and not representative of my employers
[a] the /etc/strcf script is failing on 'net1'
Where does this link to?
What does strcf depend on in terms of defining
the device/interface?
[b] More than that, when i try to remove /add the interface
in SCO's 'netconfig' the kernel rebuild fails; ks???gen failed
to rebuild kernel. So things are not in sync now. It removed/
added a device, but can't tell itself about it somehow, and
yet part of the os is trying to find it.
SCO old-timers give me a hand please
thanks
On Thu, 19 Aug 1999, joeh wrote:
> New info:
>
> [a] the /etc/strcf script is failing on 'net1'
> Where does this link to?
> What does strcf depend on in terms of defining
> the device/interface?
>
> [b] More than that, when i try to remove /add the interface
> in SCO's 'netconfig' the kernel rebuild fails; ks???gen failed
> to rebuild kernel. So things are not in sync now. It removed/
> added a device, but can't tell itself about it somehow, and
> yet part of the os is trying to find it.
>
> SCO old-timers give me a hand please
> thanks
>
> joeh wrote:
>
Maybe its time to nuke the network configuration (at least
down to the point where a kernel will relink) and start
from scratch. Then grab fresh drivers from
ftp://ftp.sco.com/pub/drivers/OSR505/network/pro100b
What is the error you get when you relink the kernel?
-
Barrett