Skip navigation.
Home
Now Shipping Version 7.0

Guarddog


Posts: 11

I have a connection problem with the internet and local network

Firefox reports "the proxy server is refusing connections" but it isn't. It will connect every third time I boot my computer.

email and weather go the same way. Everything connects on the third bootup.

My local network , A linux machine and a windows machine also do not connect through their separate network card (eth1)until the Linux machine connects to the main server

My main Internet connection is via VSat modem and is set up as a network login with an address and port that the network card (eth0 )is set to .

Anyone got any sugestions please? I've fiddled inside Guarddog quite a bit to try and fix. Nothing seems to affect the results.

Update

The service provider repeatedly assures me that once my Satellite modem shows connected then I am. End of story

So it must then be something done by Guardog . It can be open on the first boot or can need rebooting up to three times before a connection to the internet is open.

Varies all the time
Had this for three months now and have looked at pretty well everything

Jon Du Quesne's picture

More Info Please

Tytower, can you please give us more information on your hardware (brand and model of computer, brand and model of your broadband modem)? Since you have multiple computers, I'm assuming that you have a router of some sort, or are you using one of your computers as your router? Please give us more info on that.

Also, when in Mepis, open a konsole, and enter the command "ifconfig" and post the results here. Do you have similar problems when you try to run just Windows?

Jon

SimplyMEPIS Value CD: $17.95
Amount saved not buying Windows Vista Ultimate: $399
Experience gained learning Mepis and helping others: Priceless

tytower@1[~]$ ifconfigeth0

tytower@1[~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:E6:13:51:86
inet addr:10.16.26.10 Bcast:10.16.26.255 Mask:255.255.255.252
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10090 errors:0 dropped:0 overruns:0 frame:0
TX packets:8497 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3887576 (3.7 MiB) TX bytes:1193293 (1.1 MiB)
Interrupt:3 Base address:0xd400

eth1 Link encap:Ethernet HWaddr 00:40:F4:98:8D:C5
inet addr:192.168.0.1 Bcast:192.168.79.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:14037 (13.7 KiB)
Interrupt:4 Base address:0xaf00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:293 errors:0 dropped:0 overruns:0 frame:0
TX packets:293 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21316 (20.8 KiB) TX bytes:21316 (20.8 KiB)

I have a windows and a linux machine joined by direct null cable. Two NIC 's in Linux machine and eth0 addressed to ISP's network via Satellite modem

Effectively the modem is always connected to the ISP's network. When I switch on eth0 connects directly to that

The other NIC eth1 is addressed 192.168.0.1 and the windows machine is .02 This should not interfere in any way.

Machines are just 1.7Meg generic clones 6x86 500Meg memory 200Gig drives - you know the stuff Sound modem and Graphics on board shared graphics memory of 8Meg modems disabled

Please delete

Please delete

Clearing Out

For anyone coming after this did not get resolved. The Mepis distro is to blame I am pretty sure and not Guarddog.

As soon as I went to Puppy Linux and Suse10.2 and others the problem disappeared so so did the distro of Mepis -in the bin

warren's picture

This thread is a good example...

of how to NOT be helpful to oneself or others.

Guarddog is a firewall script and GUI. Anyone who knew enough to connect together a network as described in this thread would have known to disable Guarddog immediately to see if it really was causing a problem. That would have provided positive proof whether the Guarddog configuration was at fault.

And either way, then tytower could have worked with the moderators to figure out what was really going on. Maybe there was a solution for him, and maybe it would have benefited everyone. We'll never know,

As is, this thread is a silly waste of everyone's time.

So let's say aloha to tytower and get on with helping people who want to be helped.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.