PuppyThis forum is for the discussion of Puppy Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have just tried Puppy 4.1 and I could not connect to the internet.
Puppy correctly detected my eth0 and I ran the connection wizard and I was able to use the same driver that I use in SuSE 10.0 (e100) and it was able to use DHCP and I got a message that said that all was ok and I could obtain an IP address. I thought that would be automatic. Then I tried to go to a webpage but SeaMonkey could not connect to the internet.
We have DSL and use a router to connect to the internet. The SuSE 11.1 live CD had no trouble connecting. I wonder what else I have to do to get Puppy to connect?
I will try those out next time I boot into it, thanks!
btw, what is the best way to get the live CD out so that I can boot back into SuSE? Not knowing, I had to choose "shut down completely", not restart, and had to use a pin to force open the CD drawer to take Puppy out. I'm sure there must be a better way than that.
Well I tried the connection wizard and all went well, I even got an ip address but for some reason, I still cannot browse the internet.
When I check with ifconfig, all looks right. I checked with the various other status monitors that Puppy has and they too say that all is well.
Why can't I browse the internet then? What could be wrong? SuSE has no problem (I'm running that now) and Ubuntu has no problem (my son-in-law can just plug his computer into our router and go!) and since Puppy is being run from the same computer that runs SuSE and can connect, I don't understand what the problem might be.
Ok, I just tried to look at /etc/resolv.conf and it was a link to /etc/ppp/resolv.conf. When I clicked on /etc/ppp/resolv.conf to take a look, I got a message that it did not exist or Puppy could not access it. The same thing happened when I tried the /etc/resolv.conf file.
So, I wonder what's wrong with my Puppy?
Lately now, I've been getting these "incorrect shutdown" messages when I start Puppy. I just wait though and it starts up fine. I wonder what I'm doing wrong to cause these messages?
I'm running Puppy from a CD/DVD drive and my settings were saved to my usb stick.
One time when I was shutting Puppy down, I forgot and took the stick out too soon, before Puppy could save my data. But I have since then made sure to wait until Puppy had saved the session. Is this what caused the "improper shut down" messages? (Which have continued to show up btw.)
So, for the /etc/resolv.conf file, do I have to make one? Or is it already there, and I would have to somehow make it accessible to Puppy? I took a look at SuSE's /etc/resolv.conf file and wrote the info down.
When I mentioned my connection problem to a friend of mine, he was telling me something about iptables and how it was giving him a problem on one of the distros that he was running. I don't remember if he said he had to delete it or what to get it working. He mentioned that the iptables can prevent access to the internet if configured wrong. Is this a possibility?
I think I will try that since I am getting very annoyed with not being able to connect.
If I do get everything working right, would Puppy just save the new stuff over the old or do I have to delete the old saved settings?
I just booted it without the saved stuff and the first thing I did was to try the connection wizards (the DSL one and the PPPOE one) and it finally worked! I'm definitely saving these settings when I shut down. I'm very happy now.