Ipcop connect fail

kameelperdza · 10-08-2008, 03:00 AM

I have the latest ipcop running on a pentium3 coputer. Im using it as a proxy server and a url filter. The problem is that sometimes i will get the following error. http://192.168.0.1:82/public/proxy.p...reachable&dns=[unknown]&ftpcommand=nothing&ftpreply1=nothing&version=squid/2.5.STABLE14

I dont know what is means and what to do to fix it. It only began to do this 3 monhs ago. Can anybody please tell me what to do to fix it and what it can be?

lensman3 · 10-09-2008, 09:29 PM

This is just a guess, but

It looks like the computer with an IP number of 192.168.0.1 is going to your proxy server (SQUID) out port 82. It is trying to go out using a redirected(?) ftp connection and your proxy server doesn't know how to deal with an ftp (probably a passive) connection.

Do a "dig 192.168.0.1" and see what happens. Is the 192.168.0.1 machine your firewall/proxy server? Where does this error show up? Is it in the proxy servers logs? Since it is a firewall there must be two NIC's, so does the error say which NIC this error is registered against?

kameelperdza · 10-10-2008, 12:26 AM

Elo thanks for that response.

I did some test becos i dont think that its ipcop that is givng the errors. I had the server for over a year now and it only began to give the error recently. I did the folowing to find out more about the problem. I got a extra switch and put in on the red interface. I connected my laptop to the switch that is connected to the red so that i can check if i get the same problems. To test this i tried to ping www.google.co.za. The replies from www.google.co.za was good but suddenly i got this error.

Reply from 72.14.205.99: bytes=32 time=309ms TTL=237
Reply from 72.14.205.99: bytes=32 time=410ms TTL=237
Reply from 72.14.205.99: bytes=32 time=365ms TTL=237
Reply from 72.14.205.99: bytes=32 time=450ms TTL=237
request timeout
request timeout
request timeout
request timeout
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
reply from 196.14.234.2 : destination net unreachable
request timeout
request timeout
request timeout
Reply from 72.14.205.99: bytes=32 time=501ms TTL=237
Reply from 72.14.205.99: bytes=32 time=389ms TTL=237
Reply from 72.14.205.99: bytes=32 time=410ms TTL=237
Reply from 72.14.205.99: bytes=32 time=309ms TTL=237
Reply from 72.14.205.99: bytes=32 time=370ms TTL=237

This was strange so i called the isp and told them that im getting the strange reply from a certain ip. They told me that it is one of their new servers that they have build. I dont think that server want to forward the packets.

I also noticed that when i open a web site then i will get a page that shows a picture of the clark connect logo and a few statistics. The statistics said that the server is unable to connect to the internet. it also show the url i tried to open and the status of the connection.

Ive been complaining about this error for a few months now. but lately the errors increased. The isp has a defferent exuse eveyday. They even told me that its my proxy. I reinstalled ipcop and that did not solve it. So i did my own test and prove them wrong. Another strange thing is that they say we are the only clients that have this internet problem

kameelperdza · 10-10-2008, 02:36 AM

i contacted the isp and told them that they have a week to sort out the problem. i have attached 2 jpegs to show what problem i get.

lensman3 · 10-11-2008, 03:05 PM

Try a traceroute. You may have to be superuser to do this. But run "traceroute 196.14.234.2". You should see each of the network routers the packet hits.

If you run "whois 196.14.234.2", it shows that the owner of the 196.14.234.2 IP number is in Joberg, South Africa.

Also play with the program "/bin/tracepath 196.14.234.2". This program will tell you if the "ping" path was symmetrical or asymmetrical, ie, the forward and return routes were the same.

tracepath also discovers MPU so that you can adjust your Ethernet accordingly. On my machine tracepathing to South Africa, my results are: pmtu 1500 hops 23 back 64. The 23 hops to za appears right, but 64 on the return is excessive (and probably not correct).

Take a look at this site: http://forums.whirlpool.net.au/forum...fm/887518.html
It appears that you may be affected by your ISP shaping your connection.

kameelperdza · 10-13-2008, 04:06 AM

Thanx i have tested the connections. The ping reply was low on sunday. If im run whois then i get a reply that its all from the same location. I think that the return hops is becos out internet is not up to date. I have a private wlan link directly from work to my house so that i can be online at home. When i play onlne the lowest ping that i can get is 250ms. an local is 56ms. The proxy error seems to be resolved,

10-08-2008, 03:00 AM	#1 (permalink)
kameelperdza Registered User Join Date: Oct 2008 Posts: 8 OS: xp	Ipcop connect fail I have the latest ipcop running on a pentium3 coputer. Im using it as a proxy server and a url filter. The problem is that sometimes i will get the following error. http://192.168.0.1:82/public/proxy.p...reachable&dns=[unknown]&ftpcommand=nothing&ftpreply1=nothing&version=squid/2.5.STABLE14 I dont know what is means and what to do to fix it. It only began to do this 3 monhs ago. Can anybody please tell me what to do to fix it and what it can be?

10-09-2008, 09:29 PM	#2 (permalink)
lensman3 Registered User Join Date: Oct 2007 Location: Littleton, Colorado USA Posts: 470 OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix	Re: Ipcop connect fail This is just a guess, but It looks like the computer with an IP number of 192.168.0.1 is going to your proxy server (SQUID) out port 82. It is trying to go out using a redirected(?) ftp connection and your proxy server doesn't know how to deal with an ftp (probably a passive) connection. Do a "dig 192.168.0.1" and see what happens. Is the 192.168.0.1 machine your firewall/proxy server? Where does this error show up? Is it in the proxy servers logs? Since it is a firewall there must be two NIC's, so does the error say which NIC this error is registered against?

10-10-2008, 12:26 AM	#3 (permalink)
kameelperdza Registered User Join Date: Oct 2008 Posts: 8 OS: xp	Re: Ipcop connect fail Elo thanks for that response. I did some test becos i dont think that its ipcop that is givng the errors. I had the server for over a year now and it only began to give the error recently. I did the folowing to find out more about the problem. I got a extra switch and put in on the red interface. I connected my laptop to the switch that is connected to the red so that i can check if i get the same problems. To test this i tried to ping www.google.co.za. The replies from www.google.co.za was good but suddenly i got this error. Reply from 72.14.205.99: bytes=32 time=309ms TTL=237 Reply from 72.14.205.99: bytes=32 time=410ms TTL=237 Reply from 72.14.205.99: bytes=32 time=365ms TTL=237 Reply from 72.14.205.99: bytes=32 time=450ms TTL=237 request timeout request timeout request timeout request timeout reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable reply from 196.14.234.2 : destination net unreachable request timeout request timeout request timeout Reply from 72.14.205.99: bytes=32 time=501ms TTL=237 Reply from 72.14.205.99: bytes=32 time=389ms TTL=237 Reply from 72.14.205.99: bytes=32 time=410ms TTL=237 Reply from 72.14.205.99: bytes=32 time=309ms TTL=237 Reply from 72.14.205.99: bytes=32 time=370ms TTL=237 This was strange so i called the isp and told them that im getting the strange reply from a certain ip. They told me that it is one of their new servers that they have build. I dont think that server want to forward the packets. I also noticed that when i open a web site then i will get a page that shows a picture of the clark connect logo and a few statistics. The statistics said that the server is unable to connect to the internet. it also show the url i tried to open and the status of the connection. Ive been complaining about this error for a few months now. but lately the errors increased. The isp has a defferent exuse eveyday. They even told me that its my proxy. I reinstalled ipcop and that did not solve it. So i did my own test and prove them wrong. Another strange thing is that they say we are the only clients that have this internet problem

10-11-2008, 03:05 PM	#5 (permalink)
lensman3 Registered User Join Date: Oct 2007 Location: Littleton, Colorado USA Posts: 470 OS: xp 64 sp2 Fedora Core 8 (vmware xp core 8 x32) Minix	Re: Ipcop connect fail Try a traceroute. You may have to be superuser to do this. But run "traceroute 196.14.234.2". You should see each of the network routers the packet hits. If you run "whois 196.14.234.2", it shows that the owner of the 196.14.234.2 IP number is in Joberg, South Africa. Also play with the program "/bin/tracepath 196.14.234.2". This program will tell you if the "ping" path was symmetrical or asymmetrical, ie, the forward and return routes were the same. tracepath also discovers MPU so that you can adjust your Ethernet accordingly. On my machine tracepathing to South Africa, my results are: pmtu 1500 hops 23 back 64. The 23 hops to za appears right, but 64 on the return is excessive (and probably not correct). Take a look at this site: http://forums.whirlpool.net.au/forum...fm/887518.html It appears that you may be affected by your ISP shaping your connection.

10-13-2008, 04:06 AM	#6 (permalink)
kameelperdza Registered User Join Date: Oct 2008 Posts: 8 OS: xp	Re: Ipcop connect fail Thanx i have tested the connections. The ping reply was low on sunday. If im run whois then i get a reply that its all from the same location. I think that the return hops is becos out internet is not up to date. I have a private wlan link directly from work to my house so that i can be online at home. When i play onlne the lowest ping that i can get is 250ms. an local is 56ms. The proxy error seems to be resolved,