Puppy Linux Discussion Forum

rarsa · Last edited by rarsa on Sun 14 Jan 2007, 00:44; edited 1 time in total

I'm in the process of improving the Ethernet wizard (Network connection wizard).

The problem is that I have acces to a limited number of computers and network cards and cannot test all the different combinations.

I will release the changes in small increments, always as a finished product so it can be released at any time Barry deems appropriate.

I'm releasing it as a dotpup for easy installation.
http://www.murga.org/~puppy/viewtopic.php?p=26778#26778

Please do not limit your test to the areas of change identified in the task list or change log. If you have comments or sugestions add them there and I will add them to the task list to be prioritized.

Please include in all posts the version number of the networksetup-upgrade package you used to test.

Thanks in advance

rarsa · Posted: Mon 23 Oct 2006, 01:37 Post subject:

New functionality added, please test it.

It is safe to test. It has an uninstaller that will restore to the previous version.

Get it from here!

klhrevolutionist · Joined: 08 Jun 2005 Posts: 1122

rarsa: Tested on puppy-2.10 with 3c59x driver module successfully.

Wi

Flash · Posted: Sat 28 Oct 2006, 22:55 Post subject:

Rarsa, I intend to test your new wizard by using it to set up my Netgear WG311 wifi card, as soon as I can find the time. There's a lot in my food bowl at the moment. Smile

rarsa · Posted: Sun 29 Oct 2006, 02:10 Post subject:

tony_rosano · Joined: 03 Oct 2006 Posts: 12

sounds like a great idea. i downloaded your dotpup and installed. mybe i missed something and im in hte worng place. did this add options to the already existing ethernet/network wizard? or is it a whole new wizard?

what ever the case. I have numerus computers/network cards that i can try for you.

rarsa · Posted: Mon 30 Oct 2006, 14:34 Post subject:

It is adding functionality to the existing ethernet/network wizard.

Thank you for testing.

It'll be awesome if you can test wireless too.

I want to compare this latest version with something that I'm planning to do in the next couple of days.

I may be integrating rutilt to replace the wireless configuration portion of the wizard. I just needed some changes to rutilt so I contacted the developer, he just replied with a new version that has the required changes.

I will test them tonight and if it is what I was looking for then integrate them tomorrow night.

Then I will compare which one works better, if the current functionality or the rutilt integration (I am expecting that rutilt will be better than what we have).

ting · Joined: 01 Sep 2005 Posts: 7 Location: Sandvika, Norway

I think I found a bug

When using the new method of connecting to the wireless (in the setup menu). My atheros card gives me problems. Ive had it before so I think I know the problem:
The new madwifi drivers gives you two interfaces wifi and ath0. The setup wizard uses the wifi, when it's supposed to use ath0. Hence it's trying to connect with a non existent interface. Wag works with out any problems, so it's probably just a problem with the setup aplication.

Hope this helps Wink

BlackAdder · Joined: 22 May 2005 Posts: 382

When using the network wizard with ndiswrapper I have been puzzled why the configuration does not persist, even though the files /etc/wlan0wireless and /etc/wlan0mode have been created.
The cause seems to be that the network wizard does not know that ndiswrapper is to be used. A quick and not very elegant fix is to add the following commands to rc.local. This assumes that the interface created by ndiswrapper is wlan0.

BarryK · Posted: Mon 01 Jan 2007, 07:44 Post subject:

BlackAdder, I think it is in /etc/rc.d/rc.network that they are supposed to be read, but I haven't checked that script for sometime.

BlackAdder · Joined: 22 May 2005 Posts: 382

Barry,
Yes, in the ndiswrapper case wlan0wireless and wlan0mode would be run from within rc.network, but without the driver being loaded they do not work successfully. Since rc.network runs before rc.local, they have to be run again after the driver is loaded via modprobe ndiswrapper.
Works for me anyway.
I had thought of modifying rc.network to test for the existence of wlan0wireless and doing a modprobe ndiswrapper if it is there, but that might confuse the issue if wlan0wireless was created by another driver.
edit:
I suppose an alternative would be to modify wlan0wireless to load ndiswrapper. Will fumble about in the scripts later to see if there is an easy way to get the wizard to do it.

brantfordbandit · Joined: 01 Jan 2007 Posts: 2

i have both desktop and laptop connected with hardwire i can't get my wireless to work on laptop

BarryK · Posted: Mon 01 Jan 2007, 18:24 Post subject:

rarsa · Posted: Tue 02 Jan 2007, 00:50 Post subject:

laptopnewbee · Joined: 19 Aug 2006 Posts: 165

downloaded 2.13 beta 01-01-07 early in the am. i was very happy with how your wizard worked while using the live cd, but when i did a full hdd install the wizard started acting as bad or worse than the troubles i had with 2.12, and i could not make a manual linkup work any better. i think there is something going on during the hdd install operation that is doing this.

after reinstalling puppy i copied my ndiswrapper directory from my 2.11 partition, and did a manual connection with excellent results. this supports my belief that something in the install is going wrong. does the live cd use different copies from the ones that get installed?

anyway if the connection wizard worked as well for the hdd install as it did for the live cd i would call it wonderful.