networking issues

[rkismet]

i did a pupget for firefox...after install and reboot, neither my wired nor wireless connection works.

OS installed on hd

symptoms:
network cards visible
dhcp returns a 169.x.x.x address
it will take a static address but will not browse out (url or ip)
if i use the livecd...the connections work

i'd reinstall, but i dont want to run into the issue if i install firefox again

any ideas?

[nipper]

rkismet,
There is a very good chance that the reason no has tried to answer you yet is because they could use some more information.

i did a pupget for firefox...after install and reboot, neither my wired nor wireless connection works.

Because there are so many possibilities, which version of Puppy? Which Firefox pet?

OS installed on hd

Just to make sure I understand, a full HD install, not a frugal one? A full install is somewhat different from the other ways of using Puppy but there are some experts here who have full installs and they might recognise a common issue.

symptoms:
network cards visible
dhcp returns a 169.x.x.x address

So, no IP address handed out by DHCP. What is supposed to be doing the DHCP, a router? If so, do any other machines receive DHCP correctly from the router?

it will take a static address but will not browse out (url or ip)
if i use the livecd...the connections work

Does that mean that you don't have to configure anything when you use the live CD? When doing this testing are you using the bootcode pfix=ram? Is the static address you are trying in the proper subnet for the router (if there is a router)?

i'd reinstall, but i dont want to run into the issue if i install firefox again

I'd suggest holding off on a reinstall until you've given a bit more information and maybe someone has an idea. I can't think of a reason why installing a pet of Firefox would cause this to not work, maybe someone else can.

If anything I've asked is obscure, don't hesitate to ask for clarification. You will find this to be a helpful and supportive forum. There are lots of people here all the time to help. Welcome.

[rkismet]

rkismet,
There is a very good chance that the reason no has tried to answer you yet is because they could use some more information.

i did a pupget for firefox...after install and reboot, neither my wired nor wireless connection works.

Because there are so many possibilities, which version of Puppy? Which Firefox pet?

Puppy4
firefox 4.0.0.2 (for the package manager)

OS installed on hd

Just to make sure I understand, a full HD install, not a frugal one? A full install is somewhat different from the other ways of using Puppy but there are some experts here who have full installs and they might recognise a common issue.

Full install

symptoms:
network cards visible
dhcp returns a 169.x.x.x address

So, no IP address handed out by DHCP. What is supposed to be doing the DHCP, a router? If so, do any other machines receive DHCP correctly from the router?

should be 192.168.1.x class c
all other nodes on the network recieve proper ip and can browse out

it will take a static address but will not browse out (url or ip)
if i use the livecd...the connections work

Does that mean that you don't have to configure anything when you use the live CD?

no configuration needed when using the livecd, dhcp/all defaults works fine.

When doing this testing are you using the bootcode pfix=ram? Is the static address you are trying in the proper subnet for the router (if there is a router)?

i dont know how to use the boot code for testing on a full hd install
as far as the subnet, gateway, dns, etc...all is correct
router router is the dhcp server.

Though the symptom showed itself after the firefox install im not convienced that it was the cause of the problem either...thats just when it showed itself; i dont think i did anything inbetween when i pulled down and installed the app and when i rebooted the box.

installed on a PIII 700 laptop w/256 mRAM
onboard nic and pcmcia 802.11b nic

Any help or ideas would be greatly aprishiated.

thanks!

[Aitch]

From some obscure blog;

Q: What is the equivalent of "ipconfig /release --> ipconfig /renew" in Linux?
A: From 'man dhclient'

dhclient -r eth0
dhclient eth0

this typed in a console [assuming it's eth0, change if not] should tell the router to re-issue the IP lease

Failing that unplug the power to the router with all network outputs disconnected then after the lights on the router settle, reconnect

you may need to reboot using DHCP in network wizard

If that doesn't work

type ifconfig in a console & see if it's still issuing a 169

repost result

Aitch

[rkismet]

From some obscure blog;

Q: What is the equivalent of "ipconfig /release --> ipconfig /renew" in Linux?
A: From 'man dhclient'

dhclient -r eth0
dhclient eth0

dhclient ... command not found....


Ok,
so i got a little frustrated tring to figure this one out. i figured it would only take 30/45 minutes to reinstall and get fresh install back to where it needed to be. i wouldnt learn anything but it seemed to be the easier way out...i've already put quite a few hours into trying to resolve the network issue.

sooo... (below is a 40min step-by-step...i did not deviate from these steps)
i booted from cd (just downloaded the iso yesterday, puppy4)
i blew away the full install
repartationed/formated the drive 9 gb ext3 + 1gb swap
installed full again
the new clean install booted fine
picked up an address after using the network wizard
verified with local router webpage then with yahoo.com
rebooted, all still good
installed firefox from the package manager 4.0.0.2
promptly rebooted
!did not open firefox!
just took a look to see the address from the cli
169.x.x.x again!!!!!!!!

i didnt really think it was the firefox install before...this time i didnt do anything else...

any help or guidence would be much apprishiated
thanks!!

[HairyWill]

ifconfig
will give the active interfaces
ifconfig -a
will give you all interfaces
dhcpcd eth0
will request a dhcp assigned IP for eth0 if it complains that dhcpcd is already running then note the PID process id it gives then do
kill PID
dhcpcd eth0

and
ifconfig
again to check the state of the active interfaces

[Aitch]

Ok try again

console

ifconfig eth0 down
ifconfig eth0 up

should reset it

if not then you have to use the network wizard

& give it your router ip address, which you can find from one of your other PCs
[I think you said 192.168,1.x class c?, therefore make your gateway 192.168.1.1 & your dns server]

also you said you had 2 network interfaces
onboard & pcmcia
Check which i/f its using &
make sure its not using the pcmcia one and then dropping it on reboot for the onboard one

have you tried modprobing or lspci?

Aitch
edit: sorry Will, it happened again, I was editing and didn't get a new post warning

[rkismet]

dhcpcd eth0
will request a dhcp assigned IP for eth0 if it complains that dhcpcd is already running then note the PID process id it gives then do
kill PID
dhcpcd eth0

and
ifconfig
again to check the state of the active interfaces

killed PID
dhcpcd eth0 timed out - gave 169 address again

[rkismet]

ifconfig eth0 down
ifconfig eth0 up[/i]

should reset it

came back with 169. address

if not then you have to use the network wizard

& give it your router ip address, which you can find from one of your other PCs
[I think you said 192.168,1.x class c?, therefore make your gateway 192.168.1.1 & your dns server]

static did not work either
when clicking on test eth0 in the wizard it say it is "live"

also you said you had 2 network interfaces
onboard & pcmcia

removed PCMCIA before install to ease trobleshooting...did not put it back in...just have the onboard one for now.

have you tried modprobing or lspci?

i guess this is where i fall short...not sure what either is...

thanks for the help guys!!

[nipper]

rkismet,
Well the symptoms you describe definitely do look as if on subsequent boots there is no longer a connection between your router and network interface eth0.

Try that command that HarryWill suggested, ifconfig -a and post the results.

Which version of Dingo, the 2.6.21 kernel or the 2.6.25 kernel? If you didn't have a choice it's probably the former.

[roganty]

I'm having the same problem as rkismet, on first boot of puppy 4 I managed to get a network connection, then on subsequent boots nothing!

dhcpcd is returning a 169. address.
In resolv.conf the name server is set as my router ip address, and it was automatically created by dhcpcd!

I'm going to try some of these commands to try and get wireless back up!

[erikson]

An IP address in the 169.x.x.x range is indicative of a failed dhcp acquisition.

Here are some general (not Puppy-specific) hints:
http://www.pctechbytes.com/computer/article-8.html

[roganty]

I've managed to get it connected again!

What I did was I disabled WEP encryption and unhide the network ssid

Then I used "pwireless wireless scanner" program to connect to the network and it connected and gave me a (correct) ip address

Then I re-enabled WEP (with the same key) connected to the network in the same way and its still connected!

I have also re-hidden the ssid.

Only the next re-boot will tell! lol!

[rkismet]

rkismet,
Well the symptoms you describe definitely do look as if on subsequent boots there is no longer a connection between your router and network interface eth0.

Try that command that HarryWill suggested, ifconfig -a and post the results.

Which version of Dingo, the 2.6.21 kernel or the 2.6.25 kernel? If you didn't have a choice it's probably the former.

if i use a static address i cant ping out to something local on the network...even if i hosed the gateway and dns, i should be able to ping out or ping it.
while on the latop in question, it can ping itself (w/ lookback and the static address).
i am positive that nothing outside of the laptop is to blame...works before firefox install...still works with the live cd w/ both static and DHCP for both wired and wireless.

not sure where to find the kernel ver... could you let me know where to find or what line i can use in the console?

thanks!!

[MU]

# uname -r
2.6.21.7

Or look in /lib/modules, how the kernel-folder is numbered.
Mark

[rkismet]

ok
so i decided to take a different approch...
i used the livecd (that i dwonloaded and burned 2 nights ago) w/ no config file...
network works fine...
installed firefox 4.0.0.2 using the package manager
saved the session/rebooted
network hosed again....


any thoughs?
thanks!!

[rkismet]

# uname -r
2.6.21.7

Or look in /lib/modules, how the kernel-folder is numbered.
Mark

thanks!!
yes, it is 2.6.21.7

[rkismet]

anyone else have any thoughts?

[rcrsn51]

I don't know what version of Firefox is numbered 4.0.0.2, but perhaps you should download the current version 2.0.0.14 directly from Mozilla. It comes as a tar.gz which you can extract and save anywhere. The simplest place would be in /root. To run it, just go into the Firefox folder and run the executable from there.

You might also want to delete your Firefox profile in the hidden folder .mozilla in case it is causing a problem. It's the folder with the funny name.

[Bruce B]

At first

I thought it was a coincidence.


Then

After strike two, I thought as rcrsn51, get the Firefox from Mozilla.

If that works

Let us know if you don't mind.