"Just Works" Configuration of Ethernet at bootup

Message

tubby · #31 Post by **tubby** » Sun 24 Jan 2010, 18:33

Well this pensioner has done some digging and there is an autoconnect.pet already in the ibiblio reps.
Surely this could be your starting point.

mikeb · #32 Post by **mikeb** » Sun 24 Jan 2010, 20:55

Well this pensioner has done some digging and there is an autoconnect.pet already in the ibiblio reps.

yes someone did do this recently but my dodgy memory could not remember who or where...from what I remember he made a remaster with it included it it was working just fine.

mike

Puppyt · #33 Post by **Puppyt** » Mon 25 Jan 2010, 00:14

tubby wrote:Try adding to your /startup dir
dhclient
dhclient-script
dhcpcd (symlink to dhclient)
dhcpd
All downloadable from the ibiblio packages.
Worked ok for me on a frugal install, found and connected to ETH0.
You may not need all of the above but i went for belt and braces.

Great stuff, tubby! I'll test it soon.

I want to make an idiot-proof Puppy (spot the Catch-22). Something that works out of the box for new computer users - "age" be damned - with no interest or inclination to command-line or scripting (or wizards), will resume intact after improper shutdowns (yay Silver Puppy's thread and pet - sorry off-topic) etc etc.
Regarding nooby's request for a compromise in automatic ethernet at bootup - just how hard would it be to include the option in the typical live-cd startup options of keyboard, locale, Xorg and mouse?

ecomoney · #34 Post by **ecomoney** » Mon 25 Jan 2010, 00:15

Is this for ethernet, I believe its a program for automatically connecting to wireless

sunburnt · #35 Post by **sunburnt** » Mon 25 Jan 2010, 00:38

Hi ecomoney; How`s it going?
LanPuppy did exactly this, it got the gateway config from the router
wrote it to /etc/resolv.conf , and did auto-setup of networking at boot.

Puppyt · #36 Post by **Puppyt** » Mon 25 Jan 2010, 00:43

sunburnt wrote:LanPuppy did exactly this, it got the gateway config from the router...

Thanks sunburnt! Downloading now - missed my radar completely but is now much appreciated.

mikeb · #37 Post by **mikeb** » Mon 25 Jan 2010, 02:50

Is this for ethernet, I believe its a program for automatically connecting to wireless

nope Lan routers/modems...by the nature of the roaming beastie i don't think auto wireless would be quite as feasible.....mainly due to the common use of encrypted networks.

mike

Puppyt · #38 Post by **Puppyt** » Mon 25 Jan 2010, 16:28

shinobar at the Puppy Linux Japanese Team has released this little gem for puppy4 (http://www.murga-linux.com/puppy/viewtopic.php?t=51630) - is this what you were thinking, nooby and ecomoney, for automatic LAN connection?

shinobar wrote:It automatically starts up the desktop with 800x600 screen size, Universal timezone, us-English keyboards.
You can change the first setup with one window.
The network connection is also automatic in case an eth0 interface is found and DHCP is available.

Quick setup Puppy is easy to make up based on any Puppy v4.x.
Download firstsetup-0.4en.pet from here.
Follow the document.

jemimah · #39 Post by **jemimah** » Mon 25 Jan 2010, 23:50

The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

01micko · #40 Post by **01micko** » Mon 25 Jan 2010, 23:55

jemimah wrote:The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

I think as Pwireless2 matures it will become the default networking app in Puppy/Quirky. It is coming along nicely.

mikeb · #41 Post by **mikeb** » Tue 26 Jan 2010, 01:16

The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

yer can't beat good software

mike

#42 Post by **ttuuxxx** » Tue 26 Jan 2010, 04:35

jemimah wrote:The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. All you need to to is start it and it will know which interfaces have a carrier and automatically request an IP - no configuration necessary, works on both wired or wireless networks.

Can we have a version we could toss in the startup folder without a gui, so it does that in the background unknown to users. And if users want to manually set they could run the default Pwireless2 GUI?
ttuuxxx

jemimah · #43 Post by **jemimah** » Tue 26 Jan 2010, 04:45

Actually, you could already do that with the latest version. Just delete gtrayicon from the startup folder. The frontend and backend are completely separate. I experimented this version with putting the Pwireless2 daemon startup in /etc/init.d but I think I'm going to move it back to /root/Startup because for some reason it adds like 15 seconds to shutdown time, at least on my machine.

mikeb · #44 Post by **mikeb** » Tue 26 Jan 2010, 10:43

Pwireless2 daemon startup in /etc/init.d but I think I'm going to move it back to /root/Startup because for some reason it adds like 15 seconds to shutdown time, at least on my machine

the /startup stuff would get killed along with other X apps but init.d daemons are left running (part of the reason for dirty shutdowns on full installs.)

mike

jemimah · #45 Post by **jemimah** » Tue 26 Jan 2010, 15:06

I tried kill -9ing them in the shutdown scripts, but that was ineffective. Probably further research is necessary, since it would be nice if restarting X didn't take you offline.

nooby · #46 Post by **nooby** » Tue 26 Jan 2010, 15:58

The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd.

sounds nice but as a noob I have no clue on what it is.

using google it says it is something in the terminal that one call up writing Dhcpcd

I should write that down on a paper and test it then.

Just now I try to trippleboot so will take some time.

Patriot · #47 Post by **Patriot** » Tue 26 Jan 2010, 16:16

Hmmm .....

mikeb wrote: the /startup stuff would get killed along with other X apps but init.d daemons are left running (part of the reason for dirty shutdowns on full installs.)

Not necessarily all startup stuffs will be ... daemonized ones without display hooking won't be (ex: daemonized wpa_supplicant doesn't get killed) ... I did have an idea a couple of moons ago to resolve dirty shutdowns for all cases of installs ... Maybe we can pursue it after our next little project is done ?

jemimah,
Startup and init.d scripts are handled differently. For startup scripts, you can just specify-n-forget ... but you may want to implement re-entrant possibility for daemons should X is restarted. For init.d, they should have (minimum) start & stop option flags to be handled by rc.sysinit and rc.shutdown. Please look at CUPS init.d script as an example ... Most of my newer scripts with auto-start ability are able to handle both Startup and init.d invocation ...

Rgds

jemimah · #48 Post by **jemimah** » Tue 26 Jan 2010, 16:39

Yep that's likely what the problem is - needs a stop option. Back to work for me...

[Edit - yup, that solves it. Thanks for the hint - I should have realized that...

]

mikeb · #49 Post by **mikeb** » Tue 26 Jan 2010, 17:34

Actually I do find a little quirk in that I have a mini script to check battery status in startup but even though exec and & is used delayedrun hangs around

mike

ps I fix the dirtiness for full installs but for frugal although this is handled the union prevents cleanliness

#50 Post by **ttuuxxx** » Tue 26 Jan 2010, 23:19

jemimah wrote:The secret of Puppeee and Pwireless2 is to use the latest Dhcpcd. .

The thing about the thing, lol Ok i'll stop messing around, to compile the latest Dhcpcd in 2.14X I would have to update glibC, I was lucky enough to do it once, when I changed it from 2 series to 3 series, but anything past that I think I would be pushing it, So that means no auto start for 2,3 series, hmmmm I think we need a different work around for this.
ttuuxxx

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

"Just Works" Configuration of Ethernet at bootup