rohc team mailing list archive
-
rohc team
-
Mailing list archive
-
Message #02011
Re: IPROHC certificate cannot be verified
Kimo,
Sorry for the late answer. I was busy with my everyday life and job...
In your 2nd test, you are using the overlapping IP ranges for:
* the network that interconnects the 2 test machines
(192.168.0.0/24)
* the IP/ROHC network (192.68.0.0/16).
Please update your iprohc_server.conf file with a different network.
For example:
ipaddr: 192.168.1.1/24
Regards,
Didier
On Sun, 8 Nov 2015 13:49:15 -0600,
Kimo Kandi <kandisyskimo@xxxxxxxxx> wrote:
> Hi Didier,
>
> *Testing between two public cloud servers*
>
> I am testing between two public IP cloud servers. I am not sure about
> NAT settings but IP tables are not running. Below are configured
> interfaces on server and client boxes.
>
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet X.X.X.X netmask 255.255.255.0 broadcast X.X.X.X
> inet6 fe80::601:7cff:feb9:3701 prefixlen 64 scopeid
> 0x20<link> ether 04:01:7c:b9:37:01 txqueuelen 1000 (Ethernet)
> RX packets 141 bytes 16722 (16.3 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 201 bytes 24020 (23.4 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> inet6 fe80::601:7cff:feb9:3702 prefixlen 64 scopeid
> 0x20<link> ether 04:01:7c:b9:37:02 txqueuelen 1000 (Ethernet)
> RX packets 8 bytes 648 (648.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 14 bytes 1860 (1.8 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
> inet 127.0.0.1 netmask 255.0.0.0
> inet6 ::1 prefixlen 128 scopeid 0x10<host>
> loop txqueuelen 0 (Local Loopback)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
>
> *Testing over LAN*
>
> I also tested between on two Ubuntu boxes on LAN setup. Now, it seems
> client is connecting to server properly. I Tested PING requests
> between client and servers. When I verified packet transmission
> statistics, *all packet size are being shown zero in server
> statistics. *Please suggest me further.
>
> https://rohc-lib.org/wiki/doku.php?id=iprohc-run
>
> IPROHC version is 0.8.0 for both server and client.
>
> Started server and client using below commands
> sudo iprohc_server -b eth0 &
> sudo iprohc_client -r 192.168.0.119 -beth0 -i tun_ipip -P
> demoCA/certs/IpRohcClient1/client1.p12
>
> Attached the server and client logs of server machines and server
> configuration file.
>
> Below are the network interfaces on local server.
>
> eth0 Link encap:Ethernet HWaddr 00:19:66:66:0c:81
> inet addr:192.168.0.119 Bcast:192.168.0.255
> Mask:255.255.255.0 inet6 addr: fe80::219:66ff:fe66:c81/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:99050 errors:0 dropped:47 overruns:0 frame:0
> TX packets:82909 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:15556076 (15.5 MB) TX bytes:13712924 (13.7 MB)
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:11994 errors:0 dropped:0 overruns:0 frame:0
> TX packets:11994 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1015980 (1.0 MB) TX bytes:1015980 (1.0 MB)
> tun_ipip Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.0.0 P-t-P:192.168.0.0 Mask:255.255.255.0
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1458 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:500
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> *Code changes while compiling iprohc on Ubuntu servers*
>
> Also, I made code changes in iprohc as I was unable to install apt-get
> iproute-dev in Ubuntu and was getting errors like
> "tun_helpers.c:31:24: fatal error: libnetlink.h: No such file or
> directory" Commented code like below and other changes made as per
> URL(I am unable to fine URL now. I am trying to get it)
>
> libiprohc_common_la_LIBADD = \
> -lgnutls \
> -lrohc
> # -lnetlink
>
>
> On Thu, Nov 5, 2015 at 2:30 PM, Didier Barvaux <didier@xxxxxxxxxxx>
> wrote:
>
> > Hi,
> >
> > > Thank you, Didier,
> > > Attached the logs with smaller size. Please verify and suggest me
> > > further.
> >
> > You're welcome. I looked at the log files. I would say that the
> > control channel established correctly but that the data channel
> > doesn't. It could be related to NAT or filtering.
> >
> > Is there a NAT gateway or a network firewall between your client and
> > your server?
> >
> > Regards,
> > Didier
> >
> > PS: See the wiki for the terms control and data channels:
> > https://rohc-lib.org/wiki/doku.php?id=iprohc-overview#software_architecture
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~rohc
> > Post to : rohc@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~rohc
> > More help : https://help.launchpad.net/ListHelp
> >
> >
Attachment:
signature.asc
Description: PGP signature
References
-
IPROHC certificate cannot be verified
From: syskan syskan, 2015-10-15
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-10-18
-
Re: IPROHC certificate cannot be verified
From: syskan syskan, 2015-10-20
-
Re: IPROHC certificate cannot be verified
From: syskan syskan, 2015-10-26
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-10-27
-
Re: IPROHC certificate cannot be verified
From: syskan syskan, 2015-10-28
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-10-29
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-10-29
-
Re: IPROHC certificate cannot be verified
From: syskan syskan, 2015-11-03
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-11-03
-
Re: IPROHC certificate cannot be verified
From: syskan syskan, 2015-11-04
-
Re: IPROHC certificate cannot be verified
From: Didier Barvaux, 2015-11-05
-
Re: IPROHC certificate cannot be verified
From: Kimo Kandi, 2015-11-08