SOLVED: Slow internet connection

Submitted by lads on Fri, 04/13/2007 - 04:42. Networking
Posts: 8

Hi, just installed Mepis 6.0, it looks good but I’ve several problems, the worst being a useless slow internet connection.

My adapter is a VIA VT6105 Rhine III, and works ok on XP. The adapter seems to be recognized by the SO and it works – at a maximum download rate of 500 b/s. I can only open Google’s webpage (although the Google image takes several minutes to appear) and nothing else. GAIM doesn’t work; a ping command will simply hung up.

Can anyone help? Thanks.

» login or register to post comments

see if this helps:

Submitted by carlops on Fri, 04/13/2007 - 05:16.
Posts: 2299

see if this helps: http://www.mepis.org/docs/en/index.php/Disable_IPv6

Newbie or not Newbie, there's always a question

» login or register to post comments

I checked the variable in

Submitted by lads on Fri, 04/13/2007 - 06:59.
Posts: 8

I checked the variable in Firefox and it was already set to true. I then tried the command line, but the problems continue.

Thanks anyway.

» login or register to post comments

Do you have a proxy or a

Submitted by carlops on Fri, 04/13/2007 - 07:27.
Posts: 2299

Do you have a proxy or a router or something?

Start checking with the firewall disabled (menu > internet > security)

Newbie or not Newbie, there's always a question

» login or register to post comments

Hello again, After your

Submitted by lads on Fri, 04/13/2007 - 11:01.
Posts: 8

Hello again,

After your second post I lost X and had to go for another install - this time with 6.5.

With 6.5 traffic can sometimes go up to 3 Kb/s but keeps mainly below 1 Kb/s. Some web pages now partially load if I wait 10 minutes or more. With 6.5 instead of all packages going wrong on a ping (say to www.google.com) I get 2 or 3 responses per 100 queries.

I'm connecting through a LAN that is behind a firewall. Sometime back I managed to connect without problems through this same LAN using Debian.

As an interface Mepis looks really good, but this kind of problems makes it ineffective. Any more feedback on this would be appreciated.

» login or register to post comments

Just to add that I disabled

Submitted by lads on Fri, 04/13/2007 - 11:29.
Posts: 8

Just to add that I disabled the Mepis Firewall - no improvements.

» login or register to post comments

I can understand this makes

Submitted by carlops on Fri, 04/13/2007 - 11:50.
Posts: 2299

I can understand this makes it ineffective for you. But I am baffled because the connection exists yet gives so many problems.

I woild like to know a bit more of your setup. What exactly is the infrastructure from the card in your PC to the outside world?

It looks to me as though several routes exist to the same network, which would cause the timeouts. Do you have more than one network device in your machine?

Can you give me the result of these commands:
- ifconfig
- route
- tracepath www.google.com
- ping localhost
- if possible, ping the gateway address behind the line that starts with 'default' when you enter the route command

Newbie or not Newbie, there's always a question

» login or register to post comments

Just something I stored

Submitted by eadwine on Fri, 04/13/2007 - 11:58.
Posts: 244

Just something I stored long ago.. don't know if it is applicable still:

If you are suffering from a broadband connection that is running too slow, you can solve this one by commenting out the first DNS address (nameserver) in /etc/resolve.conf by putting a # in front of it.

Can't hurt to try, you can always reverse it.

» login or register to post comments

Those commands

Submitted by lads on Fri, 04/13/2007 - 13:04.
Posts: 8

Thank you once more for your tips.

First I tried eadwine’s comment, without result. I checked again the interfaces and in fact there where two working, wireless on eth0 and wired on eth1. I then disabled eth0 (I don’t use it) and gave it another try – no changes.

I’m connected to a LAN that is a sub-network of a larger infrastructure (sorry I’m not savvy on this). You’ll see that my LAN gateway is 192.168.2.254 (MasterPriv.firewall) but I go through another gateway to the outside world on 193.136.139.254.

Here are the outputs of those commands:

lads@2[~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0E:35:25:15:5F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x6000 Memory:e0001000-e0001fff

eth1 Link encap:Ethernet HWaddr 00:40:D0:58:12:82
inet addr:192.168.2.228 Bcast:192.168.79.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1106 errors:0 dropped:0 overruns:0 frame:0
TX packets:266 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:153305 (149.7 KiB) TX bytes:24716 (24.1 KiB)
Interrupt:3 Base address:0xc000

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:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7072 (6.9 KiB) TX bytes:7072 (6.9 KiB)

lads@2[~]$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
default MasterPriv.fire 0.0.0.0 UG 0 0 0 eth1

lads@2[~]$ tracepath www.google.com
1: psig-abrantes.firewall (192.168.2.228) 0.131ms pmtu 1500
1: MasterPriv.firewall (192.168.2.254) 21.389ms
2: 193.136.139.254 (193.136.139.254) 24.407ms
3: no reply
4: no reply
5: no reply
6: no reply
7: no reply
8: no reply
9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500

lads@2[~]$ ping localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.028 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=3 ttl=64 time=0.030 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=4 ttl=64 time=0.031 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=5 ttl=64 time=0.034 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=6 ttl=64 time=0.032 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=7 ttl=64 time=0.030 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=8 ttl=64 time=0.029 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=9 ttl=64 time=0.032 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=10 ttl=64 time=0.033 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=11 ttl=64 time=0.029 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=12 ttl=64 time=0.029 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=13 ttl=64 time=0.026 ms

--- localhost.localdomain ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 11997ms
rtt min/avg/max/mdev = 0.025/0.029/0.034/0.007 ms

lads@2[~]$ ping MasterPriv.firewall
PING MasterPriv.firewall (192.168.2.254) 56(84) bytes of data.
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=1 ttl=255 time=8.42 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=2 ttl=255 time=1.11 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=3 ttl=255 time=9.84 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=4 ttl=255 time=28.0 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=5 ttl=255 time=14.6 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=6 ttl=255 time=1.70 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=7 ttl=255 time=0.689 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=8 ttl=255 time=3.66 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=9 ttl=255 time=0.627 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=10 ttl=255 time=3.44 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=11 ttl=255 time=17.6 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=12 ttl=255 time=7.01 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=13 ttl=255 time=19.1 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=14 ttl=255 time=3.29 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=15 ttl=255 time=7.75 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=16 ttl=255 time=15.8 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=17 ttl=255 time=31.8 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=18 ttl=255 time=2.64 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=19 ttl=255 time=15.9 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=20 ttl=255 time=9.80 ms
64 bytes from MasterPriv.firewall (192.168.2.254): icmp_seq=21 ttl=255 time=1.89 ms

--- MasterPriv.firewall ping statistics ---
21 packets transmitted, 21 received, 0% packet loss, time 20097ms
rtt min/avg/max/mdev = 0.627/9.764/31.817/8.784 ms

It looks like packages are having trouble on passing through the final Gateway. This could be a weird setting on the Gateway, but then dozens of Linux boxes connected to it would be out of service.

I have to leave now for the weekend; I can only get further feedback to you on Monday. Thanks once more.

» login or register to post comments

You have the broadcast

Submitted by carlops on Fri, 04/13/2007 - 13:09.
Posts: 2299

You have the broadcast address set wrong, I think:
inet addr:192.168.2.228 Bcast:192.168.79.255 Mask:255.255.255.0

As far as I'm aware, it should be inet addr:192.168.2.228 Bcast:192.168.2.255 Mask:255.255.255.0

Newbie or not Newbie, there's always a question

» login or register to post comments

I changed the broadcast

Submitted by lads on Mon, 04/16/2007 - 02:55.
Posts: 8

I changed the broadcast address, but the problem persists. I'll ask the sysadmin to check it, this might not be a OS problem. More feedback afterwards.

» login or register to post comments

Hi again. After a brief talk

Submitted by lads on Mon, 04/16/2007 - 08:46.
Posts: 8

Hi again.

After a brief talk with the sysadmin he told me to edit this file:

/proc/sys/net/ipv4/ip_forward

and simply write "1" on it. The file has nothing else in it and just indicates whether to use ip forwarding or not. The problem lies in the firewall of the LAN I connect through, which has a very old OS. With ip forwarding set on my MEPIS connects fine.

Thanks everyone who tried to help, and sorry to bug you for something outside MEPIS.

Please mark this thread as solved.

» login or register to post comments

Thanks for letting us know.

Submitted by carlops on Mon, 04/16/2007 - 08:59.
Posts: 2299

Thanks for letting us know. Next time we'll know what to look for. Good luck with MEPIS, hope you're gonna like it.

Newbie or not Newbie, there's always a question

» login or register to post comments

Search

SOLVED: Slow internet connection

see if this helps:

I checked the variable in

Do you have a proxy or a

Hello again, After your

Just to add that I disabled

I can understand this makes

Just something I stored

Those commands

You have the broadcast

I changed the broadcast

Hi again. After a brief talk

Thanks for letting us know.

Comment viewing options