Page 30 of 30
Posted: Wed 01 Apr 2009, 19:50
by Dougal
Grenville Grimace wrote:Tested, but sorry to report that it doesn't fix the issue.
Well, I'm baffled...
I tried putting the relevant code into a separate script to test it -- and it worked ok.
So I tried using the wizard and setting up a WPA profile for my AP (which is open...), using your key -- and it worked fine:
Code: Select all
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="dlink"
scan_ssid=1
#psk="fyQ~xG\a@9zvoO7a[.]lY,f%0w_`0vj3kX<@~zTYnvNBbbEpob(0s:,/>-4`4=}"
psk=68d7d703eb492c5bac50a9bf8d25e01d04052358b349ae2a985a16158eaaf914
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
}
I
did find a couple of little bugs, which I fixed:
- the GUI actually got broken by your key, when refreshing (it didn't get quoted, so the '>' broke gtkdialog).
- when saving the wpa_profile, escaped chars got interpreted... so the "\a" in your key got confused fr "alert" (a terminal beep!).
I've uploaded the updated version, please try it and see if it works ok -- I can't see why it shouldn't work otherwise... (unless it's something like the locale?)
Posted: Wed 01 Apr 2009, 23:28
by Grenville Grimace
Dougal wrote:I've uploaded the updated version, please try it and see if it works ok -- I can't see why it shouldn't work otherwise... (unless it's something like the locale?)
Success! My eeepc is now on the internet.
Thanks
SIOCADDRT error message
Posted: Thu 02 Apr 2009, 05:58
by lightheaded1
I get thi message when I click on static to see what the settings are after using the network wizard.My netmask numbers dont match up as I am connecting thru LAN.When the prompt asks me if I am sure my numbers are correct it gives me the error message and will not connect.If I dont query the setting it connects . GO figure
Posted: Fri 03 Apr 2009, 10:13
by Dougal
Another update:
- fixed problem with funny chars in WPA key
- fix finding network profiles for devices using the prism2_* modules (fixes encrypted networks not connecting on startup, as reported by user pbrouwer).
- add detection of pcmcia card, to know if we need to wait a bit before scanning. Should make pcmcia cards work much more reliably (thanks to mbe's continued testing...).
Posted: Sat 04 Apr 2009, 20:14
by Dougal
Libretto100ct wrote:modprobe i82365
I was looking through a Gentoo udev rules file and noticed a comment that might be relevant here...
So maybe the problem is just i82365 being broken...
Posted: Wed 08 Apr 2009, 04:52
by Libretto100ct
Hey Dougal,
Turned out to be faulty hardware. IE: The 16 bit PCMCIA card. Confirmed it using several OS and laptops. The card would turn on, blink, throw back a hit every now and then and then finally no hits at at. The laptops would pick up the card and the LED would flash through all steps like normal. Very annoying. It's taken a week off working on my Libretto only pupplet,
That's always a potential issue with old hardware unfortunately.
I have replacements coming via eBay. The nice thing about old hardware is it's cheap, if not free to replace.
Thanks for all your help.
The tip about loading the module through the bootloader was great. No more need to mess with rc.local . i82365 module works fine on the Libretto 50, 70, 100, 110 laptops. The "# this driver is broken and should not be loaded automatically" is probably the reason why it's turned off in Puppy at boot up. Without it. PCMCIA is not detected at all.
Again thank you for your time and attention to this. You went well above and beyond.
Hopefully, some of the issues I posted above will help you troubleshoot faulty hardware as being the cause if it comes up again in the future.
Posted: Wed 29 Jul 2009, 09:56
by ttuuxxx
What I don't understand is why there isn't a download link on page 1 of this post with the latest version or on your last post, I looked around 10 of 40 pages here and nothing, not a single link.
ttuuxxx
Posted: Wed 29 Jul 2009, 10:33
by aragon
i think dougal removed it after some discussions with whodo. but you'll find the last updated version here:
http://www.murga-linux.com/puppy/viewtopic.php?t=40537
aragon
Posted: Wed 29 Jul 2009, 10:38
by ttuuxxx
thanks aragon
ttuuxxx
Posted: Sat 03 Oct 2009, 09:37
by edl
hi
I tried to read the whole thread, but I did not understand the exact procedure to be able to get that puppy 4.2(kernel 2.6.25.16) autoconect network wireless. Can someone help me figure out which files I need and what to do?
thank you
yes, some people use static ip with wireless
Posted: Mon 19 Oct 2009, 03:37
by imnotrich
Yes, some people do use static ip with wireless.
Fewer dropouts (no issues with dhcp lease renewals)
But also because I am sharing printers through my router to a Ubuntu desktop.
Re: yes, some people use static ip with wireless
Posted: Mon 19 Oct 2009, 21:41
by nic2109
imnotrich wrote:Yes, some people do use static ip with wireless.
Fewer dropouts (no issues with dhcp lease renewals)
But also because I am sharing printers through my router to a Ubuntu desktop.
Anyone who (shame on them) has to use Windoze will find it beneficial as 'doze will relinquish a lease if it goes offline (e.g. it hibernates) which is quite understandable, but then the problem comes when it is woken up again as it will try and use the same I/P address again. Meanwhile the Router may well have allocated it to another user and you have an immediate problem.
It must be feasible to configure it to not behave like this otherwise communities with a large number of users would encounter this all the time, but in my experience most 'doze versions misbehave like this out of the box.
I get round this by assigning the I/P address by MAC address in the Router, so the clients can use simple option to 'Let DHCP allocate the I/P address' and don't need to be any the wiser.
Posted: Mon 27 Sep 2010, 15:50
by mrd
Can anyone tell me what script or scripts need to be re-run after my laptop resumes from standby? I've been reading these long posts for days and I'm sure it is a simple answer...
Please help...
Posted: Mon 27 Sep 2010, 17:15
by rarsa
At risk of being outdated here is the answer I know:
Executing the startup script should do the trick.
/etc/rc.d/rc.network
Posted: Mon 27 Sep 2010, 17:26
by mrd
Thanks! I'll give it a shot when I get home!
Posted: Tue 28 Sep 2010, 01:22
by mrd
Works perfectly! Thanks very much!