Difference between revisions of "Talk:Ad-Hoc Networking"
(Fixing formatting from less wiki-minded editors.) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 9: | Line 9: | ||
=Touchpad= | =Touchpad= | ||
It seems the HP Touchpad uses wpa_supplicant, similar to Android, rather than wifidriver, as the previous did. Any workarounds? [[User:Breakingspell|Breakingspell]] 05:11, 23 August 2011 (UTC) | It seems the HP Touchpad uses wpa_supplicant, similar to Android, rather than wifidriver, as the previous did. Any workarounds? [[User:Breakingspell|Breakingspell]] 05:11, 23 August 2011 (UTC) | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
Has anyone been able to connect to an adhoc? I have a Windows box running NAT32 and an adhoc access point. I had some difficulty configuring WEP security through iwconfig but finally got it to configure. Still, no DHCP lease. So, I disabled WEP security on the Windows box and left the AP open. I configure the eth0 interface like this: | Has anyone been able to connect to an adhoc? I have a Windows box running NAT32 and an adhoc access point. I had some difficulty configuring WEP security through iwconfig but finally got it to configure. Still, no DHCP lease. So, I disabled WEP security on the Windows box and left the AP open. I configure the eth0 interface like this: | ||
| Line 15: | Line 19: | ||
checking iwconfig eth0, all of the parameters are there. I try for a dhclient eth0 and still no go. I don't even see any DHCP attempts on the Windows NAT32 console. | checking iwconfig eth0, all of the parameters are there. I try for a dhclient eth0 and still no go. I don't even see any DHCP attempts on the Windows NAT32 console. | ||
| + | [[User: MSG|MSG]] | ||
Latest revision as of 07:49, 7 September 2011
I go the following error when trying to set Ad-Hoc Mode:
root@palm-webos-device:/# iwconfig eth0 mode Ad-Hoc iwconfig eth0 mode Ad-Hoc Error for wireless request "Set Mode" (8B06) :
SET failed on device eth0 ; Invalid argument.
Touchpad
It seems the HP Touchpad uses wpa_supplicant, similar to Android, rather than wifidriver, as the previous did. Any workarounds? Breakingspell 05:11, 23 August 2011 (UTC)
Has anyone been able to connect to an adhoc? I have a Windows box running NAT32 and an adhoc access point. I had some difficulty configuring WEP security through iwconfig but finally got it to configure. Still, no DHCP lease. So, I disabled WEP security on the Windows box and left the AP open. I configure the eth0 interface like this:
iwconfig eth0 mode ad-hoc essid "ssid name"
checking iwconfig eth0, all of the parameters are there. I try for a dhclient eth0 and still no go. I don't even see any DHCP attempts on the Windows NAT32 console. MSG