(old)Puppy Linux Discussion Forum

I have my IBM Thinkpad 600E with Puppy Linux 4.3 connected to my router using wired Ethernet.

ifconfig shows the eth0 has an address of 192.168.1.4

but I can't get to the internet using the web browser

what am I missing?

No DNS maybe? Can you ping anything? Do other computers have internet?

When I installed puppy on my neighbors computer in my room and then brought it back to him then we had my old IP address but no internet.

A phone call to the ISP support teached us that they lock the IP address for two hours to belong to the person having it last. Reason they gave was the rules from authority that isp must know which IP was connected to whom in case of sharing of copyrighed materials like music.

So to get lost one needed to do ifconfig and release of ip and such to get a new one.

maybe you have some other issue?

Firewalls can sometimes lock a browser.

I cannot ping.

The other computer on the router is a Windows XP laptop, and it works fine.


I tried and I got an error message
fopen '/etc/resolv.conf': To many levels of symbolic links
when on the second command.


What do I do now?

ieee488 wrote:fopen '/etc/resolv.conf': To many levels of symbolic links

Interesting.

What do you get for: When you set up networking did you choose Auto DHCP or Static IP?

Read here. The solution is on the second page.

rcrsn51 wrote:Read here. The solution is on the second page.

Thank you. That worked.


In that same discussion Béèm suggested running Roaring Penguin PPPoE, but that did not work for me. I use Verizon DSL which is apparently PPPoE and I know my username and password. Can you explain why it fails?

ieee488 wrote:

rcrsn51 wrote:Read here. The solution is on the second page.

Thank you. That worked.


In that same discussion Béèm suggested running Roaring Penguin PPPoE, but that did not work for me. I use Verizon DSL which is apparently PPPoE and I know my username and password. Can you explain why it fails?

In your case you didn't have a valid resolv.conf (not correctly accessible)

As for the other thread, the person had PPPoA and not PPPoE.
Different protocols.
Having DSL, you don't have a PPPoE connection either, so the roaring pinguin won't work.

I did a complete re-install of Puppy Linux 4.3.1 on the hard drive, and now it picks up the internet just fine. I didn't have to do anything with the resolv.conf file.

I also had a PCMCIA LAN card that I knew was Linux-compatible that wasn't being recognized; after the re-install it was.

Can't figure why the re-install worked.

I always do a full install.

ieee488 wrote:In that same discussion Béèm suggested running Roaring Penguin PPPoE, but that did not work for me. I use Verizon DSL which is apparently PPPoE and I know my username and password. Can you explain why it fails?

It can be a bit confusing. Yes, you have DSL service using PPPoE, but asking Puppy to connect using PPPoE won't work. Why not?

ieee488 wrote:I have my IBM Thinkpad 600E with Puppy Linux 4.3 connected to my router using wired Ethernet.

In this case it is your router that is speaking with Verison using PPPoE. Your Puppy should not speak PPPoE. Your Puppy PC just has to connect to your router by wired or wireless Ethernet.

Of course, you may have realized that and so tried connecting your Puppy PC directly to your DSL modem before running Roaring Penguin. Ideally that should have worked for you, but it didn't because of the "dueling symlinks" issue which can result from running Roaring Penguin on Puppy, and which you were able to correct thanks to rcrsn51 pointing you to Roaring Silence's solution.

(For more than you probably want to know about the Roaring Penguin "dueling symlinks" issue, see my recent post in this thread: Dingo, PPPOE, No DNS.)

ieee488 wrote:I did a complete re-install of Puppy Linux 4.3.1 on the hard drive, and now it picks up the internet just fine. I didn't have to do anything with the resolv.conf file.

After you re-installed Puppy you knew that Roaring Penguin was not what you wanted, so you didn't run it, and so it didn't mess with your resolv.conf file.