[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipcop-user
Subject:    [IPCop-user] (no subject)
From:       "Michel Van Leuven" <michel.van.leuven () pandora ! be>
Date:       2004-08-31 18:46:22
Message-ID: 000101c48f8a$d092b1b0$6d00a8c0 () celeron
[Download RAW message or body]

Hello All,

I am using Ipcop 1.4.0b9 for the moment, and find some problems with ping.
This ping is different then in 1.2.
I have 2 ipcop systems connect over the internet via cable modem and Ipsec.
Ipcop A has kabel--red--Ipcop--green--6*Winxp+2*Win2000+1*Win98.
Ipcop B has kabel--red--Ipcop--green--1*WinXp+1*Win98.
                             --Blue---Xylinkwirelesrouter--1*Winxp

Ipcop A green = 192.168.0.1
Ipcop B green = 192.168.2.1
Ipcop C blue  = 192.168.3.1

Ipcop A = 1.4.0b9
Ipcop B = 1.4.0b3

Pinging from any Winxp on A green to Winxp on B green will never work for
only one cpu with address.
ping 192.168.2.100
Changing this address to 192.168.2.102 do not help, still unreachable
Pinging from this unreachable cpu to any machine on Ipcop A has no problem.
Also pinging all the other machines from A to B and vice versa is no
problem.
Pinging directly from Ipcop A to this machine on Ipcop B is also no problem.
ping 192.168.0.1 192.168.2.100, ok no problem.
So the responce works.

Why only this machine has a problem, it must be something in the Ipcop A but
what.


Now ping in Ipcop:
root@deskpro:~ # ping  192.168.0.1 192.168.3.100
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.708 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.567 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.581 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.570 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.566 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.588 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.570 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.573 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.565 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.561 ms
--- 192.168.0.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.561/0.585/0.708/0.042 ms

adress 192.168.3.100 is not up, where is the answer comming from ????

root@deskpro:~ # ping 192.168.0.1 192.168.2.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.082 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.574 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.559 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.575 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.588 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.562 ms
--- 192.168.0.1 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.559/0.990/3.082/0.936 ms
This is  ok its from green A to green B.

root@deskpro:~ # ping -c 5 -i 5 192.168.0.1 192.168.2.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.080 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.464 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max/stddev = 0.464/0.772/1.080/0.308 ms
This is not ok, ping must be correct, use this kind of ping to test the vpn
between the 2 boxes, and restart the vpn it fails. It always fails.

root@deskpro:~ # ping -c 5  192.168.0.1 192.168.2.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=2.236 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.568 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max/stddev = 0.568/1.402/2.236/0.834 ms

Removing the -c option solves the problem.

Please help ?

Best regards from:
Michel Van Leuven
Parsivalstraat 14
2860 Sint katelijne Waver
Belgium
Tel   : +32 (0)15 315082
Fax   : +32 (0)27 004677
Mobile: +32 (0)475 465726
E-mail:michel_van_leuven@advalvas.be


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
IPCop-user mailing list
IPCop-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-user
[prev in list] [next in list] [prev in thread] [next in thread]