Hello; the system initialisation script appears to have have an error, or possibly an omission.
My laptop has both wireless and wired network interfaces. The wired interface is assigned eth0 with the wireless taking eth1. When I boot wired then eth0 initialises fine, but when I am un-wired eth1 is NOT initialised and I have to go through Setup again. Every time I save my settings in the hope that Puppy will use them next time (like he promises) but it doesn't happen.
I would like it to try eth1 if eth0 doesn't get an IP address, either because it's unplugged, or if I press enter to skip past eth0. Right now skipping eth0 always means I have to set up wireless manually via the wizard.
This feels to me like an error, but it may just be an ommission.
I am on 2.17.
I have also noticed once or twice when booting wired that both wired and wireless are initialised. This suggests to me that rc.sysinit script sometimes goes through a different path (when checking the files system every so many bootups, perhaps) which results in rc.network being called (via rc.local0) in a different state somehow.
Can anyone help? Thanks.
Network Initialisation Problem
I'm not sure exactly what you are doing, but here is my understanding of "How Puppy Works" (tm). When you tell Puppy to save the setting for your wireless card, he does. The next time he starts up, he tries to use it. If he it is not there (i.e. no wireless card is not plugged in or you have it turned off), he removes it from his saved settings.
Does that description apply to your situation, or is something else going on? I personally have not had the problem you describe, so I don't think it is Puppy, although it could be a bug that does not affect all people. Rarsa and Tempestuous are two of our network specialists, maybe they can help you more.
Does that description apply to your situation, or is something else going on? I personally have not had the problem you describe, so I don't think it is Puppy, although it could be a bug that does not affect all people. Rarsa and Tempestuous are two of our network specialists, maybe they can help you more.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
-
nic2109
- Posts: 405
- Joined: Mon 01 Jan 2007, 20:24
- Location: Hayslope, near Middlemarch, Midlands, England
Thanks; that certainly describes why my wireless settings repeatedly "disappear" and need to be re-entered to be used.SirDuncan wrote:When you tell Puppy to save the setting for your wireless card, he does. The next time he starts up, he tries to use it. If he it is not there (i.e. no wireless card is not plugged in or you have it turned off), he removes it from his saved settings.
However my basic problem of why it doesn't try to initialise eth1 (wireless) when eth0 (wired) isn't alive is still unexplained
; as is the secondary query as to why it sometimes initialises eth1 even when eth0 IS alive. A question comes to mind here: had I used wireless first, and then added wired afterwards; might it have been different?
I don't think that it is just a wireless problem; it seems to me more like a general issue with the scripts.
Sadly I'm insufficiently fluent to follow what they are doing, so I'll need some help to understand whether it should do what I want or whether that constitutes an enhancement.
-
jonyo
Net wiz gui setup doesn't always retain settings even if correct save buttons are punched. I don't understand the fixes but they are out there. The gui works great with some wifi combos but not with others. Sorry, i'm not clear on the other issue & not sure what you mean by this part?
"have also noticed once or twice when booting wired that both wired and wireless are initialised."
"have also noticed once or twice when booting wired that both wired and wireless are initialised."
-
jonyo
Re: Network Initialisation Problem
Ran across this & think its relevant.nic2109 wrote:
I have also noticed once or twice when booting wired that both wired and wireless are initialised. This suggests to me that rc.sysinit script sometimes goes through a different path (when checking the files system every so many bootups, perhaps) which results in rc.network being called (via rc.local0) in a different state somehow.
Can anyone help? Thanks.
http://www.murga-linux.com/puppy/viewtopic.php?t=19214
-
Wellesfargo
- Posts: 8
- Joined: Mon 21 May 2007, 17:08
- Location: Kyle, Saskatchewan Canada
Network Initialisation Problem
Puppy 220 is working fine for me so far. The only trouble I have is with the wireless networking during boot. It seems that during boot it turns the radio off and then it attempts to get an IP address and then it turns the radio back on. Needless to say the ip address it has is a self generated one. I have to run through the Network Wizard after every boot to get the Wireless working. Puppy 2.17 has the same issue. I have a Dell with a broadcom chipset.
Fixed.
I found that I had to modify the rc.network. All the lines with ifconfig were turning my wireless card off. This was stopping it from getting an IP. I simply changed all the lines with " ifconfig ${INTERFACE} down " to ifconfig ${INTERFACE} up # changed from down. Now my wireless is working perfectly.
Fixed.
I found that I had to modify the rc.network. All the lines with ifconfig were turning my wireless card off. This was stopping it from getting an IP. I simply changed all the lines with " ifconfig ${INTERFACE} down " to ifconfig ${INTERFACE} up # changed from down. Now my wireless is working perfectly.