PUPEEE and wi-fi connection ad-hoc

[rino777]

Hi to all.
It's my first post here.

I have an EEEPC 701, i have tried some linux os and now I'm trying PUPEEE.

When I set my wireless card in ad-hoc mode by rutilt it say

An error occurred:
Can't set operating mode : Ad-Hoc
Code:22

when I do in terminal

iwconfig ath0 mode Ad-Hoc

Error for wireless request "SET MODE" (8b06)
SET failed on device ath0 : Invalid argument

Maybe that i have to install driver with ndiswrapper?

What can I do?

[tempestuous]

The iwconfig command should not include capital letters.

Code: Select all

iwconfig ath0 mode ad-hoc

[rino777]

Nothing to do.

iwconfig tell me the same message

Error for wireless request "SET MODE" (8b06)
SET failed on device ath0 : Invalid argument

Maybe that madwifi don't support ad-hoc connection?

I have tried with ndiswrapper but I don't know wery well Puppy
I've tried this command taken from Wiki-Ubuntu (I know only ubuntu)

Code: Select all

modprobe -r ath_pci
blacklist ath_pci
ndiswrapper -i net5211.inf
ndiswrapper -m
ndiswrapper -ma && sudo ndiswrapper -mi

But nothing is changed.

[rino777]

OK.
I've found the solution!!!

Code: Select all

~ # wlanconfig ath0 destroy
~ # wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
~ # iwconfig ath0 essid venom channel 2 

Now work fine.

Thank you tempestuous.
Thanks to all.

[paulski]

rino777

You must have a reason for ad hoc for Puppeee

I am trying to get my Puppee Eeepc to connect to my Puppy 4.00 Desktop using wifi without a wireless access point (ad hoc).

Perhaps your settings can help me.
Can you tell me what you are doing with your Pupeee to need an ad hoc setting and what your settings are?

[paulski]

No need - I've fixed it!

I used the tips from rino777 above to setup an Ad-Hoc (adhoc, ad hoc?) network between my desktop on Puppy 4.00 and my Eeepc on Pupeee (Puppy 3.01 based) without a router or access point. I just used the wireless card on the Desktop and the built in wireless in the Eeepc

Both are setup through the network wizards to connect to the internet. To do the ad-hoc network I must temporarily kill these settings (can't have both with no access point if wireless is also being used for internet!)

Step 1. Setting up the connection
A simple script on each machine did the "killing" and setup task:

For the desktop:

Code: Select all

 #!/bin/sh
iwconfig wlan0 mode Ad-Hoc
iwconfig wlan0 essid "myname" 

The desktop is already set to static ip address 192.168.2.2 with gateway 192.168.2.1 through the network wizard for the internet access so no need to change the ip addresses here. On the EeePC I needed to be a little more forceful to set the ip and the gateway and force ad hoc mode.

For the EeePC thanks to the previous posts:

Code: Select all

#!/bin/sh
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
iwconfig ath0 essid "myname" channel 11
ifconfig ath0 192.168.2.3 netmask 255.255.255.0
route add -net default gw 192.168.2.1 

Running both scripts on each machine works.
Testing with
ping 192.168.2.3
on the desktop shows it works
and
ping 192.168.2.2
on the Eeepc shows they can talk to each other.

I set up Samba according to the hints in this post:
http://www.murga-linux.com/puppy/viewto ... 84&t=22363

The big trick on the desktop was setting the IP settings first, then starting samba.
I made a script for that, removed the entry for automatic samba startup in rc.local and then everything worked sweet.

On the EeePc in LinNeighbourhood I just had to specify the workgroup name (from smb.conf) and the IP address of the server (desktop) 192.168.2.2 and it all worked!

I can just restart to restore the internet access or use some scripts I made to return things to normal.

Thanks rino777 for the tip I needed to make this work!

[orest]

Hallo,

I have an EeePC 701 and Puppy 4.3.

When I do in terminal

wlanconfig ath0 destroy

Error "bash: wlanconfig: command not found"

I am trying to get my Puppy EeePC with the tool JoikuSpot to connect to my Nokia 95 with internet.

What can I do?

[paulski]

I'm still using Puppy 4.20 based PupEEE
I have not checked if there is a new one.
wlanconfig is in this 4.20 version, but I don't think a standard puppy has it.
You may find it useful to find the latest version of a Puppy that is adapted to suit the EeePC, or download a .pet that adds the functionality.

Does your phone connection need an adhoc network at all? Perhaps another thread might help you.

[orest]

Hello,

Do you know the tool JoikuSpot for Nokia? It turns the Nokia phones to a wifi hotspot with a ad-hoc connection.
I use the freeware light version with Eeebuntu und Windows XP.

Why work it not with Puppy 4.3? What can I do?

[paulski]

Joikuspot running on your phone looks just like a normal hotspot to the EEEpc using puppy or any other system.
The manual for Joikuspot light says:
"Some laptops....may require that you allow "Computer-to computer (ad-hoc) networks only for JoikuSpot. This is NOT the normal case...".

That statement has more to do with hardware than software.
If it works without ad-hoc in Eeebuntu than you don't need ad-hoc in Puppy either.

Try the autoconnect programs in Puppy's Network menu

If all else fails general Puppy tips on hotspot access will help you out
Try putting "hotspot" in at
http://wellminded.com/puppy/pupsearch.html

and search the forum.

[orest]

Hello paulski,

the autoconnect programs find JoikuSpot, but connect not to the internet with Nokia.

This is the iwconfig from Eeebuntu with JoikuSpot:

wlan0 IEEE 802.11bg ESSID:"JoikuSpot_0022FD68FC3B"
Mode:Ad-Hoc Frequency:2.462 GHz Cell: 66:C6:8A:52:06:E2
Tx-Power=20 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Eeebuntu works. You see, there is a ad-hoc modus. I think, it ist a driver-problem with Puppy.

[orest]

The iiwconfig Puppy with JoikuSpot shows:

ESSID: "Joikuspot ....."

Mode: Managed AccessPoint: Not-Associated


I think, the ath5k-driver works not in ad-hoc Mode.

[paulski]

Puppy has the right "driver" or module, its just how it gets setup using a standard Puppy distribution with an EeePC.
Its all about turning the ath0 module on and off at the right time
EeUnbuntu has that already ironed out. A newer PupEE has it already okay.

Okay to persist with this Unbuntu has given you all the clues to set up iwconfig and ifconfig
Try this:

Download wlanconfig from my gzip file I uploaded
put it in /usr/local/bin/

Then either make this script below or type in the commands line by line in a terminal

Code: Select all

#!/bin/sh
wlanconfig ath0 destroy
wlanconfig ath0 create wlandev wifi0 wlanmode adhoc
iwconfig ath0 essid "JoikuSpot_0022FD68FC3B" freq 2.462 GHz

you may need to do ifconfig in unbuntu to see if the ip address information is fixed or flexible. See the previous posts where ifconfig is mentioned and try to use an ifconfig to make the same setup in Puppy.

If all else fails try again with PupEEE distro like Pupee4.2
http://www.murga-linux.com/puppy/viewtopic.php?t=40644

[tempestuous]

orest and paulski, you are talking at cross purposes.

PupEEE has the older 2.5.25.16 kernel and includes the ath_pci driver as standard.
Those adhoc commands relate specifically to this driver ("wlanconfig" is unique to the ath_pci driver).

Puppy 4.3 with the 2.6.30.5 kernel does not contain the ath_pci driver as standard, since it's deprecated in favour of the new ath5k driver. That's been under discussion on this forum for more than a year.

One solution would be to install the ath_pci driver for the new kernel which I provided here -
http://www.murga-linux.com/puppy/viewto ... 455#346455

But a more straightforward solution would be to investigate the correct adhoc commands for the ath5k driver ...
these should be as arguments passed to the iwconfig wifi configuration application. It should be something like -

Code: Select all

iwconfig eth1 mode ad-hoc
iwconfig eth1 channel 4
iwconfig eth1 essid MY_SSID
iwconfig eth1 key 1234567890

Now assign an IP address which is compatible with your phone
(let's say your phone's IP address is 192.168.0.1)

Code: Select all

ifconfig eth1 up
ifconfig eth1 192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0
route add default gw 192.168.0.1 eth1

[tempestuous]

Having explained adhoc connections, however, I make two further remarks:

- Joikuspot apparently turns your phone into a full wifi access point, so adhoc should not be necessary.
The Puppy computer should be able to connect as a normal network client, with IP address assigned automatically.

- Joikuspot should not be necessary at all.
There are quite a number of Puppy forum members who use their 3G phones as modems, with no special software needed on the phone.
The connections discussed on the forum have been direct USB and bluetooth, but there's no reason why wifi wouldn't be possible unless the phone deliberately blocks internet access via wifi.

[orest]

Hello, tempestuous,

I tested JoikuSpot with EeePC 701 and other computers. It works with Eeebuntu and windows XP, but not with Puppy and only in ad-hoc-modus.

[tempestuous]

Sure. So follow the advice I provided about ad-hoc wifi configuration with Puppy.

But it remains true that Puppy can access the internet via a 3G phone without any special software on the phone.
Several forum members have successfully done so.

[orest]

Hello tempestuous,

I start Puppy 4.3 with" iwconfig eth1 mode ad-hoc" but the console shows

Error for wireless request "Set Mode"(8B06) :
.....Set failed on device eth1; No such device

What must I do?

[tempestuous]

I only used "eth1" in my explanation as an example.
You need to replace this with the correct name of your wifi interface.

Are you using the standard ath5k driver in Puppy 4.3?
Or have you installed the ath_pci driver instead?

[orest]

Hello,

I think, Puppy 4.31 do not support an ad-hoc-connection.

Now I use the Nokia with Puppy as modem. I works very well.

Many thanks on paulski and tempestuous.