How to start a network connection automatically?

Using applications, configuring, problems
Post Reply
Message
Author
robert_m
Posts: 18
Joined: Tue 02 Feb 2016, 05:20
Location: Monterey Bay, California

How to start a network connection automatically?

#1 Post by robert_m »

I have installed Tahr 6.05 32 bit PAE (Frugal Install, Atom N280 thin client)

I have been able to save settings between boots, and now automatically start Pidgin, for example.

However, I still have to manually make a network connection every time I boot. It seems that saving after success in NETWORK CONNECTION WIZARD does not work.

I can start it from the command line

Code: Select all

$ ifconfig eth0 up
$ dhcpcd -d eth0
Any ideas how to make this work?
- Rob M.
Puppy in My Pocket
Top
musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#2 Post by musher0 »

Hi robert_m.

If right-clicking the network icon in the tray and then clicking "setup networking" does
not give you the result you want, make a little script out of your two lines above, make
it executable, and put it in /root/Startup?

Otherwise, which network connector are you using? I have always had good results
with frisbee.

Just a few thoughts. IHTH.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Top
User avatar
tallboy
Posts: 1760
Joined: Tue 21 Sep 2010, 21:56
Location: Drøbak, Norway

#3 Post by tallboy »

/root/Startup/README.TXT wrote:Any executable or scripts (or symlink to) placed in this directory
will be executed after the X desktop has loaded.

This is handy if you want something to run automatically.

You can easily create a "symlink" (symbolic link) to an executable.
For example, say that you wanted to run /usr/local/bin/rubix (a game)
everytime Puppy is started. Use ROX-Filer (the file manager) and open
two windows, one on /usr/local/bin, the other on /root/Startup.
Then just drag 'rubix' across and a menu will popup and ask if you want
to copy, move or link, and you choose to link.

Note, if you want to execute something at bootup and prior to X desktop
loading, edit /etc/rc.d/rc.local.
True freedom is a live Puppy on a multisession CD/DVD.
Top
phat7
Posts: 179
Joined: Fri 05 Jun 2015, 08:54

#4 Post by phat7 »

I take it for granted that all recent puppies connect automatically when booted, even without a pupsave file. I can't remember when I last had to use the connection wizard. Something broken in Tahr?
Top
foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#5 Post by foxpup »

@robert_m
The Puppy devs are looking into 'connection on startup'. EDIT: For wifi, not sure for wired connection, that mostly works ootb.
It fails in several Puppies on several machines. Better scripts are on the way.

For now, if you use SNS, you can put a link to /usr/local/simple_network_setup/rc.network in /root/Startup/
Top
User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#6 Post by bigpup »

In menu>System>Pup-Sysinfo>Devices>Network

Post what it gives for info.

I want to see what the device is exactly and what driver it uses.

Did you set it up to use auto DHCP or a static IP?

Auto DHCP works best, unless you have a network that requires a static IP.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)
Top
robert_m
Posts: 18
Joined: Tue 02 Feb 2016, 05:20
Location: Monterey Bay, California

#7 Post by robert_m »

real quick just to say I am still on this...
when I noticed that my results were erratic, 5puppy 5.7.1 just worked without doing anything, I started to think that the 30 second timeout on dhcpcd
it was starting automatically, but failing.
Bottom line, I have a crappy router in the path on my wrt54g, and when I bypassed ti, and booted 6.0.5 again, it connected .
I have to go but I will report back after I have time to A-B-A this a little more.

Thanks to all for suggestions
- Rob M.
Puppy in My Pocket
Top
s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:
Contact s243a

#8 Post by s243a »

phat7 wrote:I take it for granted that all recent puppies connect automatically when booted, even without a pupsave file. I can't remember when I last had to use the connection wizard. Something broken in Tahr?
I had an issue with older versions of tahrpup:
http://murga-linux.com/puppy/viewtopic.php?t=108614

I haven't had any such issues with tahrpup 6.0.6 yet.

My guess is that tharpup 6.0.6 has more divers for USB dongles.

Before that the issue I was having is that it wasn't scanning long enough for wireless connections.

Interestingly enough, I'm now having this issue with my Wii, now that our ISP has upgraded our router. I think that older hardware expected their to be wireless access points then we see today.

I suppose though this is all off topic.

Edit Looking again at the first post. Upgrading to tharpup 6.0.6 might help, if that's an acceptable solution.
Top
robert_m
Posts: 18
Joined: Tue 02 Feb 2016, 05:20
Location: Monterey Bay, California

#9 Post by robert_m »

I am now quite certain that the problem is/was the inability of dhcp to establish a connection.
This morning, I tried to reproduce the problem, starting with booting using a direct connection to the router which runs DNS. After that, I could not make the connection fail: I brought eth0 down & up and it reconnected. I moved the cable to put the Netger GB switch (not as crappy as I had thought) between my system and the DNS Router, it just worked, I stopped the connection and restart, it worked.
Only after I cold booted did it fail to connect. The system log:

Code: Select all

Jan 30 00:54:17 puppypc2515 user.info kernel: tg3.c:v3.136 (Jan 03, 2014)
Jan 30 00:54:17 puppypc2515 user.info kernel: libphy: tg3 mdio bus: probed
Jan 30 00:54:17 puppypc2515 user.info kernel: [drm] Memory usable by graphics device = 2048M
Jan 30 00:54:17 puppypc2515 user.debug kernel: i915 0000:00:02.0: irq 43 for MSI/MSI-X
Jan 30 00:54:17 puppypc2515 user.info kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Jan 30 00:54:17 puppypc2515 user.info kernel: [drm] Driver supports precise vblank timestamp query.
Jan 30 00:54:17 puppypc2515 user.info kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jan 30 00:54:17 puppypc2515 user.info kernel: [drm] Skipping LVDS initialization for Hewlett-Packard t5745
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: Tigon3 [partno(BCM57780) rev 57780001] (PCI Express) MAC address 9c:8e:99:c5:6e:19
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: attached PHY driver [Broadcom BCM57780] (mii_bus:phy_addr=400:01)
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Jan 30 00:54:17 puppypc2515 user.info kernel: fbcon: inteldrmfb (fb0) is primary device
Jan 30 00:54:17 puppypc2515 user.info kernel: input: PS/2 Logitech Mouse as /devices/platform/i8042/serio1/input/input4
Jan 30 00:54:17 puppypc2515 user.info kernel: Console: switching to colour frame buffer device 128x48
Jan 30 00:54:17 puppypc2515 user.info kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Jan 30 00:54:17 puppypc2515 user.info kernel: i915 0000:00:02.0: registered panic notifier
Jan 30 00:54:17 puppypc2515 user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Jan 30 00:54:17 puppypc2515 user.info kernel: floppy0: no floppy controllers found
Jan 30 00:54:17 puppypc2515 user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5
Jan 30 00:54:17 puppypc2515 user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jan 30 00:54:17 puppypc2515 user.debug kernel: snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
Jan 30 00:54:17 puppypc2515 user.info kernel: input: PC Speaker as /devices/platform/pcspkr/input/input6
Jan 30 00:54:17 puppypc2515 user.debug kernel: tg3 0000:04:00.0: irq 45 for MSI/MSI-X
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: Link is down
Jan 30 00:54:17 puppypc2515 user.debug kernel: tg3 0000:04:00.0: irq 45 for MSI/MSI-X
Jan 30 00:54:17 puppypc2515 user.debug kernel: tg3 0000:04:00.0: irq 45 for MSI/MSI-X
Jan 30 00:54:17 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: Link is down
Jan 30 00:54:26 puppypc2515 user.debug kernel: tg3 0000:04:00.0: irq 45 for MSI/MSI-X
Jan 29 09:54:26 puppypc2515 daemon.info dhcpcd[5951]: version 6.7.1-dropwait starting
Jan 30 00:54:26 puppypc2515 user.info kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan 29 09:54:26 puppypc2515 daemon.warn dhcpcd[5951]: all: IPv6 kernel autoconf disabled
Jan 29 09:54:26 puppypc2515 daemon.debug dhcpcd[5951]: /proc/sys/net/ipv6/conf/all/accept_ra: No such file or directory
Jan 29 09:54:26 puppypc2515 daemon.warn dhcpcd[5951]: eth0: IPv6 kernel autoconf disabled
Jan 29 09:54:26 puppypc2515 daemon.debug dhcpcd[5951]: /proc/sys/net/ipv6/conf/eth0/accept_ra: No such file or directory
Jan 29 09:54:26 puppypc2515 daemon.info dhcpcd[5951]: eth0: adding address fe80::9e8e:99ff:fec5:6e19
Jan 29 09:54:26 puppypc2515 daemon.debug dhcpcd[5951]: eth0: pltime infinity, vltime infinity
Jan 29 09:54:26 puppypc2515 daemon.err dhcpcd[5951]: if_addaddress6: Operation not supported
Jan 29 09:54:26 puppypc2515 daemon.debug dhcpcd[5951]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jan 29 09:54:27 puppypc2515 daemon.debug dhcpcd[5951]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
Jan 29 09:54:27 puppypc2515 daemon.info dhcpcd[5951]: eth0: waiting for carrier
Jan 29 09:54:36 puppypc2515 user.notice powerapplet: Abort, unable to open /proc/acpi/battery
Jan 30 00:54:38 puppypc2515 user.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 29 09:54:52 puppypc2515 daemon.info dhcpcd[5951]: eth0: carrier acquired
Jan 30 00:54:52 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: Link is up at 100 Mbps, full duplex
Jan 30 00:54:52 puppypc2515 user.info kernel: tg3 0000:04:00.0 eth0: Flow control is on for TX and on for RX
Jan 29 09:54:52 puppypc2515 daemon.warn dhcpcd[5951]: all: IPv6 kernel autoconf disabled
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: /proc/sys/net/ipv6/conf/all/accept_ra: No such file or directory
Jan 29 09:54:52 puppypc2515 daemon.warn dhcpcd[5951]: eth0: IPv6 kernel autoconf disabled
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: /proc/sys/net/ipv6/conf/eth0/accept_ra: No such file or directory
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jan 29 09:54:52 puppypc2515 daemon.info dhcpcd[5951]: DUID 00:01:00:01:21:ff:50:c7:9c:8e:99:c5:6e:19
Jan 29 09:54:52 puppypc2515 daemon.info dhcpcd[5951]: eth0: IAID 99:c5:6e:19
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: eth0: delaying IPv4 for 0.6 seconds
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: eth0: using hwaddr 9c:8e:99:c5:6e:19
Jan 29 09:54:52 puppypc2515 daemon.info dhcpcd[5951]: eth0: soliciting a DHCP lease
Jan 29 09:54:52 puppypc2515 daemon.debug dhcpcd[5951]: eth0: sending DISCOVER (xid 0x9a23df9), next in 4.6 seconds
Jan 29 09:54:53 puppypc2515 daemon.info dhcpcd[5951]: eth0: offered 192.168.1.101 from 192.168.1.1
Jan 29 09:54:53 puppypc2515 daemon.debug dhcpcd[5951]: eth0: sending REQUEST (xid 0x9a23df9), next in 4.8 seconds
Jan 29 09:54:53 puppypc2515 daemon.debug dhcpcd[5951]: eth0: acknowledged 192.168.1.101 from 192.168.1.1
Jan 29 09:54:53 puppypc2515 daemon.debug dhcpcd[5951]: eth0: probing for 192.168.1.101
Jan 29 09:54:53 puppypc2515 daemon.debug dhcpcd[5951]: eth0: ARP probing 192.168.1.101 (1 of 3), next in 1.0 seconds
Jan 29 09:54:54 puppypc2515 daemon.debug dhcpcd[5951]: eth0: ARP probing 192.168.1.101 (2 of 3), next in 1.6 seconds
Jan 29 09:54:56 puppypc2515 daemon.debug dhcpcd[5951]: eth0: ARP probing 192.168.1.101 (3 of 3), next in 2.0 seconds
Jan 29 09:54:57 puppypc2515 daemon.err dhcpcd[5951]: timed out
Jan 29 09:54:57 puppypc2515 daemon.info dhcpcd[5951]: exited
Jan 29 09:55:43 puppypc2515 daemon.info dhcpcd[7256]: version 6.7.1-dropwait starting
Jan 29 09:55:43 puppypc2515 daemon.warn dhcpcd[7256]: all: IPv6 kernel autoconf disabled
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: /proc/sys/net/ipv6/conf/all/accept_ra: No such file or directory
Jan 29 09:55:43 puppypc2515 daemon.warn dhcpcd[7256]: eth0: IPv6 kernel autoconf disabled
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: /proc/sys/net/ipv6/conf/eth0/accept_ra: No such file or directory
Jan 29 09:55:43 puppypc2515 daemon.info dhcpcd[7256]: eth0: adding address fe80::9e8e:99ff:fec5:6e19
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: eth0: pltime infinity, vltime infinity
Jan 29 09:55:43 puppypc2515 daemon.err dhcpcd[7256]: if_addaddress6: Operation not supported
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Jan 29 09:55:43 puppypc2515 daemon.info dhcpcd[7256]: DUID 00:01:00:01:21:ff:50:c7:9c:8e:99:c5:6e:19
Jan 29 09:55:43 puppypc2515 daemon.info dhcpcd[7256]: eth0: IAID 99:c5:6e:19
Jan 29 09:55:43 puppypc2515 daemon.debug dhcpcd[7256]: eth0: delaying IPv4 for 1.0 seconds
Jan 29 09:55:44 puppypc2515 daemon.debug dhcpcd[7256]: eth0: using hwaddr 9c:8e:99:c5:6e:19
Jan 29 09:55:44 puppypc2515 daemon.info dhcpcd[7256]: eth0: soliciting a DHCP lease
Jan 29 09:55:44 puppypc2515 daemon.debug dhcpcd[7256]: eth0: sending DISCOVER (xid 0xfa11f8e), next in 4.2 seconds
Jan 29 09:55:45 puppypc2515 daemon.info dhcpcd[7256]: eth0: offered 192.168.1.101 from 192.168.1.1
Jan 29 09:55:45 puppypc2515 daemon.debug dhcpcd[7256]: eth0: sending REQUEST (xid 0xfa11f8e), next in 3.3 seconds
Jan 29 09:55:45 puppypc2515 daemon.debug dhcpcd[7256]: eth0: acknowledged 192.168.1.101 from 192.168.1.1
Jan 29 09:55:45 puppypc2515 daemon.debug dhcpcd[7256]: eth0: probing for 192.168.1.101
Jan 29 09:55:45 puppypc2515 daemon.debug dhcpcd[7256]: eth0: ARP probing 192.168.1.101 (1 of 3), next in 1.5 seconds
Jan 29 09:55:47 puppypc2515 daemon.debug dhcpcd[7256]: eth0: ARP probing 192.168.1.101 (2 of 3), next in 1.7 seconds
Jan 29 09:55:49 puppypc2515 daemon.debug dhcpcd[7256]: eth0: ARP probing 192.168.1.101 (3 of 3), next in 2.0 seconds
Jan 29 09:55:51 puppypc2515 daemon.info dhcpcd[7256]: eth0: leased 192.168.1.101 for 86400 seconds
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7256]: eth0: renew in 43200 seconds, rebind in 75600 seconds
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7256]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7256]: eth0: adding IP address 192.168.1.101/24
Jan 29 09:55:51 puppypc2515 daemon.info dhcpcd[7256]: eth0: adding route to 192.168.1.0/24
Jan 29 09:55:51 puppypc2515 daemon.info dhcpcd[7256]: eth0: adding default route via 192.168.1.1
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7256]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' BOUND
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7256]: forking to background
Jan 29 09:55:51 puppypc2515 daemon.info dhcpcd[7256]: forked to background, child pid 7367
Jan 29 09:55:51 puppypc2515 daemon.debug dhcpcd[7367]: eth0: ARP announcing 192.168.1.101 (1 of 2), next in 2.0 seconds
Jan 29 09:55:53 puppypc2515 daemon.debug dhcpcd[7367]: eth0: ARP announcing 192.168.1.101 (2 of 2)
The time stamps show that my hardware time clock is messed up and the log starts at 00:accurate minutes: seconds

This is totally confusing: the connection is not yet established, but it seams to be "Calling CRDA to update world regulatory domain". Huh?

Code: Select all

Jan 30 00:54:26 puppypc2515 user.debug kernel: tg3 0000:04:00.0: irq 45 for MSI/MSI-X
Jan 29 09:54:26 puppypc2515 daemon.info dhcpcd[5951]: version 6.7.1-dropwait starting
Jan 30 00:54:26 puppypc2515 user.info kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan 29 09:54:26 puppypc2515 daemon.warn dhcpcd[5951]: all: IPv6 kernel autoconf disabled
then (referring to the full log) it tries to connect, fails at 09:54:57 then at 09:55:43 and finally acquires a lease at 09:55:51

It will work now even with a cold boot, and it will continue to because, at the end of the log we see
  • adding IP address 192.168.1.101/24
    adding route to 192.168.1.0/24
    adding default route via 192.168.1.1
I am done with this, at least for now. I think that shutting down and properly saving the session will keep this from happening again.

Finally s243a, "off topic" ? How could we know if something is off topic until we finally get to the root cause of a problem? Oh, I didn't select Tahr 6.0.6 because I didn't see a PAE version. Thanks for posting,

Regards,
- Rob M.
Puppy in My Pocket
Top
Post Reply

Return to “Users ( For the regulars )”