Linux Web Browsing

[brian23]

Hi, I am looking for a linux distro that can be used for browsing the internet mainly, but the trick is that I need one that will run with Covenant Eyes installed in Windows on my PC. Should all Linux programs connect regardless of this program being installed? I tried Puppy 4.0 (Dingo) and could not get it to connect to the internet at all. Matter of fact Dingo didn't even show that there was an internet connection on the PC at all. I am not totally certain, but I think it was because of this program. It logs in on windows start up and unless it is "logged in" the internet is cut off. Will it block network access even when windows has not been booted up? Any help would be appreciated. Thanks!

[techieMoe]

Hi, I am looking for a linux distro that can be used for browsing the internet mainly, but the trick is that I need one that will run with Covenant Eyes installed in Windows on my PC. Should all Linux programs connect regardless of this program being installed? I tried Puppy 4.0 (Dingo) and could not get it to connect to the internet at all. Matter of fact Dingo didn't even show that there was an internet connection on the PC at all. I am not totally certain, but I think it was because of this program. It logs in on windows start up and unless it is "logged in" the internet is cut off. Will it block network access even when windows has not been booted up? Any help would be appreciated. Thanks!

I don't know of any software that will run by itself with no OS unless it's something set in your BIOS. This "Covenant Eyes" program looks like it's just a web filter that runs in the background on MS Windows. It wouldn't affect your Linux OS.

More likely Puppy just has issues with your internet connection. Is it wired or wireless? What method do you use to connect?

[brian23]

I am using an ethernet connection which works fine in windows. But when I tried to set up the connection in the Dingo wizard, it couldn't detect any connection. I guess I thought that somehow the program would sort of "shut off" the connection until it was logged in again.

[techieMoe]

I am using an ethernet connection which works fine in windows. But when I tried to set up the connection in the Dingo wizard, it couldn't detect any connection. I guess I thought that somehow the program would sort of "shut off" the connection until it was logged in again.

Unless Covenant Eyes makes changes to your router configuration, it wouldn't be able to block things for other operating systems. Have you tried any other versions of Linux?

[i92guboj]

The first thing we should do is to check

1.- which nic do you have (use lspci as root for that)
2.- if linux is loading the nic driver (lsmod)
3.- if linux is getting a valid ip via dhcp or with fixed values (if your sip gave you fixed values), probably with ifconfig.

If the nic is up and running, we can start worrying about the rest of the universe.

[brian23]

I have not tried any other linux program, but will try today (Unbutu and PClinuxOS).
i92guboj - you are way over my head. I am brand spankin' new to this, so I don't have much idea what you are talking about or how to accomplish it. Sorry. I was running puppy from a liveCD.

[i92guboj]

I have not tried any other linux program, but will try today (Unbutu and PClinuxOS).
i92guboj - you are way over my head. I am brand spankin' new to this, so I don't have much idea what you are talking about or how to accomplish it. Sorry. I was running puppy from a liveCD.

Sorry.

About 1. Open a terminal (xterm, konsole or whatever it's available). If it's a livecd you should be logged as root already I guess, so we can pass that. Type "lspci" on that terminal, a few lines describing your hardware should appear. If you don't know which of them is your NIC (network card) paste them all here.

About 2. Same procedure, but this time run "lsmod" into the xterm, instead of "lspci". Paste the output here so we can see if the correct module for the NIC detected in step 1 has been loaded.

About 3. Same thing, and run "ifconfig" this time. It should output the current config for all the NICs in your system. Paste the output here are well. This one is to make sure that the NIC is getting a valid ip address.

The purpose of all this things is to make sure that there's no problem in your distro and the NIC configuration. Only if all this three things are ok we should worry about the router. As long as any of these 3 things is not ok, the configuration of the router doesn't really matter at all. (unless the problem is on step3 and the dhcp serveris your router, but we will worry about that after seeing your configs).