My wlan does not get IP from DHCP
Good Morning from Chicago! I have been trying to install a wireless network for a while under suse 9 pro, that I bought a few weeks ago. I'm having trouble getting my wireless card working. I had it working on madrake using madwifi drivers. In any case after trying madwifi (downloaded and the one that comes in the system), I never got and IP trough dhcp, nor I would be able to connect setting the parameters manually. So, I've decided to try linuxant driverloader with the same success rate, everything works card gets recognize, I can " iwlist wlan0 scan " and check my environment, iwconfig shows my card properly connected, and ifconfig shows my card, but without IP address: wlan0 Link encap:Ethernet HWaddr 00:0C:41:AD:D3:21 UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:7 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) this is my ifcfg_wlan0: BOOTPROTO='static' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' DHCLIENT_MODIFY_RESOLV_CONF='yes' DHCLIENT_SET_DEFAULT_ROUTE='yes' DHCLIENT_PRIMARY_DEVICE='yes' UNIQUE='' WIRELESS_ESSID='OhrockNet' WIRELESS_KEY='' WIRELESS_MODE='Ad-hoc' WIRELESS_NICK='' WIRELESS_NWID='' I also tried setting the mode as Managed, same result. I read somewhere that ISC dhclient worked better that dhcpcd, so I did try changing them, if exactly the same result. I also went out and bought a different card with a different chipset supported by linuxant driveloader, and to my dismay I got to the same point. I think that this is something related to suse...but I don't know where to look of how to troubleshoot the problem any further. Any suggestions, advise, etc will be more than welcome. Roberto
On Fri, 2004-01-02 at 11:12, Roberto wrote:
Good Morning from Chicago!
I have been trying to install a wireless network for a while under suse 9 pro, that I bought a few weeks ago. I'm having trouble getting my wireless card working.
snipped ---
this is my ifcfg_wlan0:
BOOTPROTO='static' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' DHCLIENT_MODIFY_RESOLV_CONF='yes' DHCLIENT_SET_DEFAULT_ROUTE='yes' DHCLIENT_PRIMARY_DEVICE='yes' UNIQUE='' WIRELESS_ESSID='OhrockNet' WIRELESS_KEY='' WIRELESS_MODE='Ad-hoc' WIRELESS_NICK='' WIRELESS_NWID=''
Change BOOTPROTO='static' to 'dhcp' Also if you are connecting to an AP then WIRELESS_MODE should be 'Managed' Here is what mine looks like. BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='' WIRELESS_ESSID='any' WIRELESS_KEY='' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' In case you are wondering setting ESSID to 'any' allows me to connect to any available open AP. Nice when you are traveling and the hotel has wireless access.
On Friday 02 January 2004 15:09, Chuck Stuettgen wrote:
Here is what mine looks like.
BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='' WIRELESS_ESSID='any' WIRELESS_KEY='' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID=''
In case you are wondering setting ESSID to 'any' allows me to connect to any available open AP. Nice when you are traveling and the hotel has wireless access.
But it requires you to set your ap to broadcast its ESSID, and with no key specified you are essentially running a wide open net. Great for travel (and "war driveing"), but bad for security. -- _____________________________________ John Andersen
On Fri, 2004-01-02 at 18:55, John Andersen wrote:
On Friday 02 January 2004 15:09, Chuck Stuettgen wrote:
Here is what mine looks like.
BOOTPROTO='dhcp' MTU='' REMOTE_IPADDR='' STARTMODE='onboot' UNIQUE='' WIRELESS_ESSID='any' WIRELESS_KEY='' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID=''
In case you are wondering setting ESSID to 'any' allows me to connect to any available open AP. Nice when you are traveling and the hotel has wireless access.
But it requires you to set your ap to broadcast its ESSID, and with no key specified you are essentially running a wide open net. Great for travel (and "war driveing"), but bad for security.
True. But there isn't anything on my home network that a hacker would
be interested in. We don't shop on the internet and we don't do online
banking. Additionally, the signal strength of my Linksys AP is so weak
that I can barely get a connection in the rooms I want it in. Walk
outside of the house and it dies.
I think I would notice a strange car parked in my driveway. :-)
Did you see my last post on the PCMCIA solution?
--
Chuck Stuettgen
On Friday 02 January 2004 16:52, Chuck Stuettgen wrote:
True. But there isn't anything on my home network that a hacker would be interested in. We don't shop on the internet and we don't do online banking. Additionally, the signal strength of my Linksys AP is so weak that I can barely get a connection in the rooms I want it in. Walk outside of the house and it dies.
I think I would notice a strange car parked in my driveway. :-)
Did you see my last post on the PCMCIA solution?
Apparently not. What did it say? -- _____________________________________ John Andersen
participants (3)
-
Chuck Stuettgen
-
John Andersen
-
Roberto