I'm having a problem with DNS name resolution, and I need help resolving it. I'm running a 2-subnet LAN with a 3d NIC facing the Internet; the 2 subnets must go through the 3d NIC to get access to the Net (which access they currently have). When I run host <FQDN ServerName> I get back "host ServerName not found: 3(NXDOMAIN)." I understand that this means that the system thinks there are no A records for ServerName. The problem is that this worked yesterday (the command returned ServerName's IP address), and I've done nothing in the interim (that I know of) to change this. I've confirmed that winbindd, dhcpd, and named all are running. My named.conf and associated zone files all are unchanged from yesterday. I can ping ServerName just fine with only hosts = dns in my nsswitch file. For what should I look to correct this? Thanks for our help. Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell
I installed ndiswrapper and loaded the driver, and ndiswrapper reports: Installed ndis drivers: bcmwl5 driver present, hardware present ndiswrapper -m Loads the module. iwconfig displays: wlan0 IEEE 802.11g ESSID:"linksys" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:2A:BB:7E Bit Rate:54 Mb/s Tx-Power:25 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-41 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I go into yast and select "network card" it does not detect the wireless card. I've tried a number of options to set it up manually but nothing worked. If I do a /etc/init.d/network restart I get: Shutting down network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) eth0 configuration: eth-id-00:c0:9f:cc:df:15 done wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 No configuration found for wlan0 Nevertheless the interface will be shut down. wlan0 configuration: done Shutting down service network . . . . . . . . . . . . . done. Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) eth0 configuration: eth-id-00:c0:9f:cc:df:15 eth0 (DHCP) . IP/Netmask: 192.168.2.111 / 255.255.255.0 done wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 No configuration found for wlan0 unused Setting up service network . . . . . . . . . . . . . . done. So I'm guessing I need to set the configuration for the wlan0 device, however since yast doesn't seem to do much for it, I don't know how. Any suggestions as to what to do next? Thanks, Jim.
Jim wrote:
I installed ndiswrapper and loaded the driver, and ndiswrapper reports:
Installed ndis drivers: bcmwl5 driver present, hardware present
ndiswrapper -m Loads the module.
iwconfig displays: wlan0 IEEE 802.11g ESSID:"linksys" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:2A:BB:7E Bit Rate:54 Mb/s Tx-Power:25 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-41 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
When I go into yast and select "network card" it does not detect the wireless card. I've tried a number of options to set it up manually but nothing worked. If I do a /etc/init.d/network restart
I get: Shutting down network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) eth0 configuration: eth-id-00:c0:9f:cc:df:15 done wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 No configuration found for wlan0 Nevertheless the interface will be shut down. wlan0 configuration: done Shutting down service network . . . . . . . . . . . . . done. Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) eth0 configuration: eth-id-00:c0:9f:cc:df:15 eth0 (DHCP) . IP/Netmask: 192.168.2.111 / 255.255.255.0 done wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 No configuration found for wlan0 unused Setting up service network . . . . . . . . . . . . . . done.
So I'm guessing I need to set the configuration for the wlan0 device, however since yast doesn't seem to do much for it, I don't know how. Any suggestions as to what to do next?
Thanks, Jim.
A bit more info. Some more output after I tried to put a configuration together. ifup wlan0 wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 Startmode is 'manual' linux:/etc/sysconfig/network # cat ifcfg-wlan0 BOOTPROTO='dhcp' MTU='' NAME='Ethernet Network Card' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='yes' 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='static-0' And now I get this when I restart the network: wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 Startmode is 'manual' skipped Setting up service network . . . . . . . . . . . . . . done. dhcpcd tells me: dhcpcd wlan0 /sbin/modify_resolvconf: line 245: /etc/init.d/lwresd: No such file or directory linux:/etc/sysconfig/network # wlan0 device: Broadcom Corporation: Unknown device 4318 (rev 02) wlan0 Startmode is 'manual' lspci shows that wlan0 is talking to the right card... ... 0000:05:02.0 Network controller: Broadcom Corporation: Unknown device 4318 (rev 02) ... I then changed the _nm_name to look like the one in eth0, substituting the numbers from the lspci line, but that didn't work either. It all boils down to the startmode is "manual" message. I don't seem to be able to figure out how to "start" it manually. I searched for the startmode is manual in google and didn't get anything I could use. Jim.
Jim wrote:
I installed ndiswrapper and loaded the driver, and ndiswrapper reports:
Installed ndis drivers: bcmwl5 driver present, hardware present
ndiswrapper -m Loads the module.
iwconfig displays: wlan0 IEEE 802.11g ESSID:"linksys" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:2A:BB:7E Bit Rate:54 Mb/s Tx-Power:25 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-41 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
When I go into yast and select "network card" it does not detect the wireless card. I've tried a number of options to set it up manually but nothing worked. What are you looking for when you look, in YaST, for the network card? You don't state which version of SuSE you are using, VERY important. In 10.0 after you go into YaST-->Network Card, (and then select Add) one of
On Tue, 2006-01-24 at 16:43 -0500, Jim wrote: the choices in the pull down list is wireless, select it. For the module name select ndiswrapper (ignore -Select from List- as it won't be there and the list is only for supplied drivers) and select next. Setup the rest of your settings and select Next. Fill in the rest of your settings for your wireless setup and you should then be good to go. If this is a hot-pluggable card select there is a place to select that as well. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
On Tue, 2006-01-24 at 16:43 -0500, Jim wrote:
Jim wrote:
I installed ndiswrapper and loaded the driver, and ndiswrapper reports:
Installed ndis drivers: bcmwl5 driver present, hardware present
ndiswrapper -m Loads the module.
iwconfig displays: wlan0 IEEE 802.11g ESSID:"linksys" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:2A:BB:7E Bit Rate:54 Mb/s Tx-Power:25 dBm RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-41 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
When I go into yast and select "network card" it does not detect the wireless card. I've tried a number of options to set it up manually but nothing worked.
What are you looking for when you look, in YaST, for the network card? You don't state which version of SuSE you are using, VERY important. In 10.0 after you go into YaST-->Network Card, (and then select Add) one of the choices in the pull down list is wireless, select it. For the module name select ndiswrapper (ignore -Select from List- as it won't be there and the list is only for supplied drivers) and select next. Setup the rest of your settings and select Next. Fill in the rest of your settings for your wireless setup and you should then be good to go. If this is a hot-pluggable card select there is a place to select that as well.
I'm running 9.3. In yast, I select "network Card" The automatic detect does not find the card. I have tried both configure other and add options. They both resolve to the same place. I did select wireless, and set module name to ndiswrapper. This is a built-in broadcom wireless network card. I even changed the static-0 to reflect the exact configuration as reported by lspci using the working eth0 as a model, in the ifcfg-wlan0 configuration file. Jim.
Jim wrote:
I'm running 9.3. In yast, I select "network Card" The automatic detect does not find the card. I have tried both configure other and add options. They both resolve to the same place. I did select wireless, and set module name to ndiswrapper. This is a built-in broadcom wireless network card. I even changed the static-0 to reflect the exact configuration as reported by lspci using the working eth0 as a model, in the ifcfg-wlan0 configuration file.
Jim.
Jim, I looked back through your posts, and much of your information looks to be the same as mine. Also, by the looks of your iwconfig output, you may very well be set up right. Have you started Kinternet to connect to your wireless router to test or are you just looking in YaST to see if it works? I initially thought that mine was not working until I started up Kinternet and connected to my router. Also, where did you get the bcmwl5 driver? Are you sure that is the correct one? Are you dual booting Windows, and got it from there? I can private-mail you the bcmwl5a driver if you like, it works great on Suse 9.3 as a PCMCIA card in my laptop. My best suggestion is to remove the card in YaST, remove ndiswrapper, and start over. Make sure you follow the directions exactly, (which I am sure you did the first time), make sure you have correctly identified your hardware and have the correct driver, and make sure you start up Kinternet. In Kinternet I have to select the wireless connection and click on connect before I can use it. Good luck! - James W
It turns out that the problem is with dhcp. It does not want to give this interface an IP address. When I configured the interface by hand, via ifconfig wlan0 192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0 up It worked find. However dhcp thinks it has to be done this way. That's apparently where the error message "Startup is manual" is coming from. So I proceeded to tear ifup appart and see what makes it tick. While screwing around with that, I found a utility called ifup-dhcp. Hey, nothing else works, so why not? It worked. Man ifup-dhcp does nothing. I have no idea what it is, but all I know is that when I did a ifup-dhcp wlan0 -o debug,auto dhcp assigned an address to wlan0 . Go figure, thanks everyone Jim.
Jim wrote:
It turns out that the problem is with dhcp. It does not want to give this interface an IP address. When I configured the interface by hand, via
ifconfig wlan0 192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0 up
It worked find. However dhcp thinks it has to be done this way. That's apparently where the error message "Startup is manual" is coming from. So I proceeded to tear ifup appart and see what makes it tick. While screwing around with that, I found a utility called ifup-dhcp. Hey, nothing else works, so why not?
It worked. Man ifup-dhcp does nothing. I have no idea what it is, but all I know is that when I did a ifup-dhcp wlan0 -o debug,auto dhcp assigned an address to wlan0 .
Go figure, thanks everyone
Jim.
Jim, I have the Linksys WMP54G v.3 set up on 2 different machines running SuSE 9.3. I have followed the instructions to the tee on this site: nextgen.no-ip.org/~andrew/linux/ndiswrapper/ndiswrapperinfo.php with the following exceptions: ****************** Follow instructions through Up, Up, and Away! (For me this is what is needed! You may be able to use a newer version of ndiswrapper and the driver.)***Use ndiswrapper-1.3rc1 and rt2500 driver from the Linksys cd - THESE WORK!!!*** ***Remember to set the correct Access Point in YAST - net card setup "advanced" (Do ndiswrapper -m; modprobe ndiswrapper; depmod -a) AFTER updating the Kernel via YOU, remove the ndiswrapper module, uninstall the driver, uninstall ndiswrapper, then do make install in ndiswrapper directory, reinstall the driver, then do modprobe ndiswrapper. ****************** I tried forever to setup my card through iwconfig, ifup/down, etc., but always wound up with problems, including hard kernel crashes. The setup through Yast only is the best and easiest for me. I had to delete the configs for the card, as well as the ndiswrapper.ko file and start from scratch using ONLY Yast, and following the info, step-by-step on the website above. I did wind up trying a couple of different versions of ndiswrapper and the driver before it worked for me, but using Yast only, made it really easy. Once set up, start KInternet and configure it to your liking. For me, an icon at the bottom of the desktop is a lot easier to deal with than CLI. Left click, and I connect or disconnect; right click, and I can check all my settings, dns, signal quality, etc. YMMV Bernd
participants (5)
-
bernd -
Eric Hines -
James Wright -
Jim -
Ken Schneider