Internet through Untangle is slow

[mhamilton]

Done the test, and it's the same as before 3-4mbps (sometimes goes upto 4.5 but stays there) from the LAN port on the server. This is the onboard NIC.

What gives? I've even tested it by stopping the untangle-vm. Same deal. Switches are not the problem.

[sky-knight]

Well as I said, if the Untangle VM is off and the numbers are slow, you've got something amiss with your hardware. The NICs you've listed are all among the best you can possibly use. So the obvious answers aren't going to fly here.

Run ifconfig, look for errors. Not sure what else to try at this point.

[mhamilton]

Well as I said, if the Untangle VM is off and the numbers are slow, you've got something amiss with your hardware. The NICs you've listed are all among the best you can possibly use. So the obvious answers aren't going to fly here.

Run ifconfig, look for errors. Not sure what else to try at this point.

Will let you know in 24 hours.
Meanwhile, if the onboard ports are giving out 3-4mbps, and you say they are good NICs, what could it be? Maybe the bandwidth going IN to the untangle itself is not going in to it's full potential?

[sky-knight]

That's why I suggested running the ifconfig command in the terminal and looking for errors. I've never seen NICs of that class, while operating Debian perform that slow.

The last test is also in the terminal.

wget http://www.kernel.org/pub/linux/kern...ux-3.5.tar.bz2

See how quickly wget can download that 75mb file. You can disconnect Untangle's internal interface while you do this, and it'd be a pure download test direct to Untangle.

[mhamilton]

Here's ifconfig for ya. And nope, I don't see anything in terms of errors out of the ordinary :S

br.eth1 Link encap:Ethernet HWaddr 00:15:17:39:a8:a7
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33775587 errors:0 dropped:0 overruns:0 frame:0
TX packets:40485283 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8321389288 (7.7 GiB) TX bytes:24313303052 (22.6 GiB)

dummy0 Link encap:Ethernet HWaddr fe:cc:c4:57:77:6f
inet addr:192.0.2.42 Bcast:192.0.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:270 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:50201 (49.0 KiB)

eth0 Link encap:Ethernet HWaddr 00:15:17:39:a8:a6
inet addr:122.55.15.18 Bcast:122.55.15.23 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42396148 errors:0 dropped:940 overruns:0 frame:0
TX packets:45639044 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34793561752 (32.4 GiB) TX bytes:11201815189 (10.4 GiB)
Interrupt:16 Memory:fc3e0000-fc400000

eth1 Link encap:Ethernet HWaddr 00:15:17:39:a8:a7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:61629649 errors:0 dropped:0 overruns:0 frame:0
TX packets:55038992 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12609116581 (11.7 GiB) TX bytes:35537884058 (33.0 GiB)
Interrupt:17 Memory:fc3a0000-fc3c0000

eth2 Link encap:Ethernet HWaddr 00:19:b9:f2:b1:00
inet addr:112.199.86.242 Bcast:112.199.86.247 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1087397 errors:255 dropped:0 overruns:0 frame:255
TX packets:1250473 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85220002 (81.2 MiB) TX bytes:98682825 (94.1 MiB)
Interrupt:16 Memory:f8000000-f8012800

eth3 Link encap:Ethernet HWaddr 00:19:b9:f2:b1:02
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:405 errors:0 dropped:0 overruns:0 frame:0
TX packets:2880 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:89825 (87.7 KiB) TX bytes:747172 (729.6 KiB)
Interrupt:16 Memory:f4000000-f4012800

imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:42065781 errors:0 dropped:0 overruns:0 frame:0
TX packets:41896617 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:34160412166 (31.8 GiB) TX bytes:33949139502 (31.6 GiB)

imq2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16000 Metric:1
RX packets:1078776 errors:0 dropped:0 overruns:0 frame:0
TX packets:1078776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:11000
RX bytes:65228786 (62.2 MiB) TX bytes:65228786 (62.2 MiB)

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:13557262 errors:0 dropped:0 overruns:0 frame:0
TX packets:13557262 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1991960179 (1.8 GiB) TX bytes:1991960179 (1.8 GiB)

And the kernel download plateaued around 450Kb/s.
This is killing me! lol

[sky-knight]

One of your WAN links is dropping packets, and the other is reporting frame errors.

Not sure what can cause that, but there's the problem. The UT devs would know better, but aren't frame errors an MTU problem? But considering the over all packet volume, the errors appear to be a statistical blip.

[mhamilton]

One of your WAN links is dropping packets, and the other is reporting frame errors.

Not sure what can cause that, but there's the problem. The UT devs would know better, but aren't frame errors an MTU problem? But considering the over all packet volume, the errors appear to be a statistical blip.

eth0 is the WAN (onboard, port 1 for ISP#1): Currently in use
eth2 is also a WAN (PCI, port 1 for ISP#2): Used as backup with WAN failover. The errors might be old as well because there was an issue a couple days ago with the ISP.

[mhamilton]

Tony Chan from support fixed it!
Now, unfortunately, while this is fixed.. there seems to be a new issue.

Thanks a lot for all the help from everyone, especially sky-night.

[sky-knight]

Can you drop us a hint on what it was? It's got me curious!

[mhamilton]

Can you drop us a hint on what it was? It's got me curious!

Not quite sure actually. He just told me to give him an IP so he can bypass and test. And I tested, and it seems to work.