Wireless Madness!
Summary:
I've got an old laptop running SuSE 9.2, no GUI. It's got a wireless card that works like a champ and is currently serving as my file server.
Often, when I try to ssh (or fish) into it from my desktop box (SuSE 9.2, KDE 3.4) it tells me it cannot connect to that host. So I ping it. No love. Destination host unreachable.
I go to the file server and open it up. The screen is missing about 60% of the LCD display, so working from the screen is fun. Very fun.
I can't ping out. I ifdown and ifup the device a few times, checking ifconfig before, during and after. All times, it's connected just fine. After a few cycles of this, it's working perfectly from both local and remote logins.
Here's my question: is there some reason it would be shutting off the network interface? It's set to not do anything drastic, power-control-wise, through the ACPI stuff. Should I reboot, having reset the ACPI and power management info the other day, or would those settings take effect immediately? Here's the ifcfg for that particular interface.
BOOTPROTO='static'
BROADCAST='192.168.1.255'
IPADDR='192.168.1.***'
MTU=''
NETMASK='255.255.255.0'
NETWORK='192.168.1.***'
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='***'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID=''
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:07:00.0'
I've got an old laptop running SuSE 9.2, no GUI. It's got a wireless card that works like a champ and is currently serving as my file server.
Often, when I try to ssh (or fish) into it from my desktop box (SuSE 9.2, KDE 3.4) it tells me it cannot connect to that host. So I ping it. No love. Destination host unreachable.
I go to the file server and open it up. The screen is missing about 60% of the LCD display, so working from the screen is fun. Very fun.
I can't ping out. I ifdown and ifup the device a few times, checking ifconfig before, during and after. All times, it's connected just fine. After a few cycles of this, it's working perfectly from both local and remote logins.
Here's my question: is there some reason it would be shutting off the network interface? It's set to not do anything drastic, power-control-wise, through the ACPI stuff. Should I reboot, having reset the ACPI and power management info the other day, or would those settings take effect immediately? Here's the ifcfg for that particular interface.
BOOTPROTO='static'
BROADCAST='192.168.1.255'
IPADDR='192.168.1.***'
MTU=''
NETMASK='255.255.255.0'
NETWORK='192.168.1.***'
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='***'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID=''
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:07:00.0'
