ping breaks

**ifti** · 12-16-2009

I have implemented advance routing fo load balancing and a script for and fail over on a Linux machine which run squid and dansguardian for proxying, i have three interfaces on this machine which are

10.201.108.254 eth1 external interface connected to service provider
10.201.109.254 eth2 external interface connected to service provider
10.200.14.11 eth0 Internal interface for users.

Routing List
192.101.5.0/26 via 10.200.14.254 dev eth0
10.1.45.0/24 via 10.200.14.254 dev eth0
192.168.100.0/24 via 10.200.14.254 dev eth0
10.201.108.0/24 dev eth1 proto kernel scope link src 10.201.108.11
10.201.14.0/24 dev eth3 proto kernel scope link src 10.201.14.11
10.201.109.0/24 dev eth2 proto kernel scope link src 10.201.109.11
192.168.65.0/24 via 10.200.14.254 dev eth0
192.168.50.0/24 via 10.200.14.254 dev eth0
192.168.151.0/24 via 10.200.14.254 dev eth0
10.1.10.0/24 via 10.200.14.254 dev eth0
10.200.17.0/24 via 10.200.14.254 dev eth0
10.200.16.0/24 via 10.200.14.254 dev eth0
131.11.3.0/24 via 10.200.14.254 dev eth0
192.168.155.0/24 via 10.200.14.254 dev eth0
10.200.14.0/24 dev eth0 proto kernel scope link src 10.200.14.11
192.168.152.0/24 via 10.200.14.254 dev eth0
10.203.0.0/24 via 10.200.14.254 dev eth0
172.25.0.0/16 via 10.200.14.254 dev eth0
10.100.0.0/16 via 10.200.14.254 dev eth0
192.172.0.0/16 via 10.200.14.254 dev eth0
169.254.0.0/16 dev eth3 scope link
10.200.0.0/16 via 10.200.14.254 dev eth0
default
nexthop via 10.201.108.254 dev eth1 weight 2
nexthop via 10.201.109.254 dev eth2 weight 1

I have added static routes for LAN users which are

#LOCAL NETWORKS

any net 192.168.151.0/24 gw 10.200.14.254 dev eth0
any net 192.168.50.0/24 gw 10.200.14.254 dev eth0
any net 192.168.152.0/24 gw 10.200.14.254 dev eth0
any net 192.168.155.0/24 gw 10.200.14.254 dev eth0
any net 192.168.65.0/24 gw 10.200.14.254 dev eth0
any net 192.172.0.0/16 gw 10.200.14.254 dev eth0

Problem is that when i ping internal interface that is 10.200.14.11 which is assigned on eth0, the ping breaks too much due to which browsing gets slow when internet traffic load is high on proxy server then ping breaks too much on internal interface, i have checked the network on layer-2 switches and layer-3 firewalls which are fine changed network cables also changed network interface on proxy server still ping is breaking, i dont understand wts the reason traffice flow is Users -> Firewall (gateway) -> Proxy Server -> Router -> service provider
any help will b highly appreciated

**Lazydog** · 12-16-2009

Post the output of ping showing what it is that you are having issues with. Remember PING is low on the priority list and if the system is doing other things and doesn't have time ping requests will get dropped.

**ifti** · 12-17-2009

here is the output of ping from my ip that is 192.168.151.220

C:\ping 10.200.14.11 -t

Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=3ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=2ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Request timed out.
Request timed out.
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Reply from 10.200.14.11: bytes=32 time=1ms TTL=61
Request timed out.
Reply from 10.200.14.11: bytes=32 time=8ms TTL=61

Ping statistics for 10.200.14.11:
Packets: Sent = 314, Received = 259, Lost = 55 (17% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 13ms, Average = 1ms

the memory of proxy machine is 8 GB and 8 GB for swap, processor is 1795.554 MHz, cache size 1024 KB, i thought this ping problem might exist due to load on proxy machine but it occurs even when load is not high, and i m facing this problem for the last few days, this ping break affects browsing speed badly.

**Lazydog** · 12-17-2009

What is between 10.200.14.11 and the host you did this ping from?
Can you give the output of 'tracert -d'?

**ifti** · 12-18-2009

between 10.200.14.11 and the host i pinged from are two firewalls and an LBR device, the output of tracert -d is

C:\tracert -d 10.200.14.11

Tracing route to 10.200.14.11 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.151.1
2 1 ms 1 ms 1 ms 131.11.3.35
3 1 ms 1 ms 1 ms 10.203.0.1
4 1 ms 1 ms 1 ms 10.200.14.11

Trace complete.

if i ping the ips shown in tracert -d command the ping is smooth except 10.200.14..11 which is proxy's ip

**Lazydog** · 12-18-2009

Sounds like the proxy is over worked and in this case will cause you your issues. What is the load on the proxy server? What does top say?

**ifti** · 12-21-2009

below is the out put

top - 12:51:16 up 2 days, 18:17, 1 user, load average: 0.60, 0.52, 0.59
Tasks: 233 total, 1 running, 232 sleeping, 0 stopped, 0 zombie
Cpu(s): 2.3%us, 2.1%sy, 0.0%ni, 87.6%id, 6.9%wa, 0.2%hi, 0.8%si, 0.0%st
Mem: 8052168k total, 4300232k used, 3751936k free, 307756k buffers
Swap: 8707220k total, 0k used, 8707220k free, 2478036k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4025 squid 15 0 553m 513m 2184 S 4 6.5 9:01.37 squid
3333 root 15 0 381m 123m 1384 S 1 1.6 24:31.18 clamd
874 nobody 15 0 200m 117m 1184 S 1 1.5 0:00.08 dansguardian
901 nobody 15 0 200m 117m 1116 S 1 1.5 0:00.05 dansguardian
919 nobody 15 0 200m 117m 1196 S 1 1.5 0:00.11 dansguardian
920 nobody 15 0 200m 118m 1188 S 1 1.5 0:00.07 dansguardian
824 nobody 15 0 200m 116m 424 S 0 1.5 0:02.06 dansguardian
828 nobody 15 0 202m 119m 1196 S 0 1.5 0:00.14 dansguardian
831 nobody 15 0 200m 117m 704 S 0 1.5 0:01.28 dansguardian
836 nobody 15 0 206m 123m 1196 S 0 1.6 0:00.17 dansguardian
863 nobody 15 0 200m 117m 688 S 0 1.5 0:00.80 dansguardian
865 nobody 15 0 200m 117m 1184 S 0 1.5 0:00.59 dansguardian
888 nobody 15 0 200m 117m 1204 S 0 1.5 0:00.18 dansguardian
889 nobody 15 0 200m 117m 1092 S 0 1.5 0:00.34 dansguardian
921 nobody 15 0 200m 117m 1184 S 0 1.5 0:00.06 dansguardian
922 nobody 15 0 202m 119m 1196 S 0 1.5 0:00.11 dansguardian
1118 root 15 0 12708 1164 796 R 0 0.0 0:00.79 top
1 root 15 0 10308 664 552 S 0 0.0 0:00.85 init
2 root RT 0 0 0 0 S 0 0.0 0:00.47 migration/0
3 root 34 19 0 0 0 S 0 0.0 0:04.90 ksoftirqd/0
4 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/0
5 root RT 0 0 0 0 S 0 0.0 0:00.68 migration/1
6 root 34 19 0 0 0 S 0 0.0 0:04.93 ksoftirqd/1
7 root RT 0 0 0 0 S 0 0.0 0:00.00 watchdog/1
8 root 10 -5 0 0 0 S 0 0.0 0:00.01 events/0
9 root 10 -5 0 0 0 S 0 0.0 0:00.00 events/1
10 root 17 -5 0 0 0 S 0 0.0 0:00.00 khelper

dear lazy thanks for ur interest that u extended to me, i also thought that the proxy machine is over burdened, i ill appreciate further assistance from u

**Lazydog** · 12-22-2009

The interfaces connecting 10.203.0.1 and 10.200.14.11. What are they set at?

Speed?
Duplex?

Are these device connected directly together or is there some other device between them?

Thread Tools

Display

ping breaks

Posting Permissions