I'm confused. I have a Dlink DWL-650+ card which is working fine if I use the start_net script that comes with the acx100 driver. However if I put in the card, it's all recognised fine but refuses to connect to the network. After much poking I found that if I manually run: iwconfig wlan0 essid BLAH enc BLAH Then it all works fine, dhcpcd kicks in, I get an IP address and off I go - pinging the LAN. I can surf locally fine. But then I find that resolv.conf is not being modified with the results from the dhcp request. The sysconfig files think they should be modifying resolv.conf and I have run SuSEconfig after changing these, just in case. laptop:/etc/sysconfig/network # grep -R MODIFY_ * config:MODIFY_RESOLV_CONF_DYNAMICALLY="yes" config:MODIFY_NAMED_CONF_DYNAMICALLY="yes" dhcp:DHCLIENT_MODIFY_RESOLV_CONF="yes" dhcp:DHCLIENT_MODIFY_NTP_CONF="no" dhcp:DHCLIENT_MODIFY_NIS_CONF="yes" ifcfg-wlan0:DHCLIENT_MODIFY_RESOLV_CONF='yes' I KNOW the dhcpc request returns at least one DNS server: laptop:/etc/sysconfig/network # dhcpcd-test wlan0 dhcpcd: MAC address = 00:80:c8:1f:8d:26 IPADDR=192.168.0.4 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BROADCAST=192.168.0.255 GATEWAY=192.168.0.1 DNS=192.168.0.2,213.232.93.107,212.159.13.50 INTERFACE='wlan0' Can anyone provide assistance as to why my resolv.conf isn't being modified when the wlan0 interface is brought up? This is my major problem. The secondary issue for me is making the ifup scripts automagically set the essid and WEP key. These are set in ifcfg-wlan0. Many thanks, Phil Sumner
On Tue, Sep 21, 2004 at 10:52:06PM +0100, Phil Sumner wrote:
I'm confused.
I have a Dlink DWL-650+ card which is working fine if I use the start_net script that comes with the acx100 driver. However if I put in the card, it's all recognised fine but refuses to connect to the network.
After much poking I found that if I manually run: iwconfig wlan0 essid BLAH enc BLAH
Then it all works fine, dhcpcd kicks in, I get an IP address and off I go - pinging the LAN. I can surf locally fine. But then I find that resolv.conf is not being modified with the results from the dhcp request.
The sysconfig files think they should be modifying resolv.conf and I have run SuSEconfig after changing these, just in case.
laptop:/etc/sysconfig/network # grep -R MODIFY_ * config:MODIFY_RESOLV_CONF_DYNAMICALLY="yes" config:MODIFY_NAMED_CONF_DYNAMICALLY="yes" dhcp:DHCLIENT_MODIFY_RESOLV_CONF="yes" dhcp:DHCLIENT_MODIFY_NTP_CONF="no" dhcp:DHCLIENT_MODIFY_NIS_CONF="yes" ifcfg-wlan0:DHCLIENT_MODIFY_RESOLV_CONF='yes'
I KNOW the dhcpc request returns at least one DNS server:
laptop:/etc/sysconfig/network # dhcpcd-test wlan0 dhcpcd: MAC address = 00:80:c8:1f:8d:26 IPADDR=192.168.0.4 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BROADCAST=192.168.0.255 GATEWAY=192.168.0.1 DNS=192.168.0.2,213.232.93.107,212.159.13.50 INTERFACE='wlan0'
Can anyone provide assistance as to why my resolv.conf isn't being modified when the wlan0 interface is brought up? This is my major problem.
The secondary issue for me is making the ifup scripts automagically set the essid and WEP key. These are set in ifcfg-wlan0.
Many thanks, Phil Sumner
Does DHCLIENT_PRIMARY_DEVICE=yes in the wlan's ifcfg file help? Peter
poeml@cmdline.net wrote:
Does DHCLIENT_PRIMARY_DEVICE=yes in the wlan's ifcfg file help? It does indeed. Now I know what to look for, it all seems so obvious.
And having dhcpcd modify resolv.conf appears to work much better now that I have named (bind8 RPM) installed... oopsie? Next question: Where is ifup-wireless called from, when and how? Or to put my question a better way, could someone explain to me the process that SuSE/linux in general goes through when I insert my PCMCIA card, through to loading the acx_pci module? I ask because when I insert the card, the module's loaded and the SSID appears to be set properly, but I still need to run ifup-wireless manually for it to connect to the base station, and for dhcpcd to get an IP... Many thanks, Phil
On Thu, Sep 23, 2004 at 01:31:15AM +0100, Phil Sumner wrote:
poeml@cmdline.net wrote:
Does DHCLIENT_PRIMARY_DEVICE=yes in the wlan's ifcfg file help? It does indeed. Now I know what to look for, it all seems so obvious.
And having dhcpcd modify resolv.conf appears to work much better now that I have named (bind8 RPM) installed... oopsie?
depends on what "better" means exactly
Next question: Where is ifup-wireless called from, when and how? Or to put my question a better way, could someone explain to me the process that SuSE/linux in general goes through when I insert my PCMCIA card, through to loading the acx_pci module?
kernel triggers hotplug event -> hotplug script is executed -> depending on the device type hotplug might load modules or trigger other actions set up via /etc/hotplug/* -> e.g. ifup ifup calls ifup-wireless, or ifup-dhcp, or whatever seems appropriate from the configuration.
I ask because when I insert the card, the module's loaded and the SSID appears to be set properly, but I still need to run ifup-wireless manually for it to connect to the base station, and for dhcpcd to get an IP...
Maybe you need to add WIRELESS=yes to the ifcfg file. Peter
On Tue, 2004-09-28 at 11:32, poeml@cmdline.net wrote:
On Thu, Sep 23, 2004 at 01:31:15AM +0100, Phil Sumner wrote:
poeml@cmdline.net wrote:
Does DHCLIENT_PRIMARY_DEVICE=yes in the wlan's ifcfg file help? It does indeed. Now I know what to look for, it all seems so obvious.
And having dhcpcd modify resolv.conf appears to work much better now that I have named (bind8 RPM) installed... oopsie?
depends on what "better" means exactly
Matters not whether you have bind (named) running locally or not, only that the resolv.conf is properly setup and you have a DNS server properly setup. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2) * PLEASE only reply to the list *
participants (3)
-
Ken Schneider -
Phil Sumner -
poeml＠cmdline.net