IPROHC for dummies routing

Hello,

> I dont understand if in order to make it 2 way communication i have
> to set to bidirectional on the server side.

No, it is one unrelated thing. The uni- and bi-directional modes are about ROHC modes, not uni- or bi-directional traffic in the tunnel.

> on the client i have modified the routing by changing the default
> gateway to the tunnel and keeping a ip host route to the iprohc
> server for the keepalive to work otherwise the tunnel will colapse.

Seems fine.

> if i set the return path tru the server packets dont arrive to the client.

What do you mean? Do you set the return path on the "desired host", on the server, or on both of them?

Could you please try to ping the server from the client? Then ping the client from the server? If it doesn't work, you have problem with one IP/ROHC problem. Otherwise, this is one IP routing problem.

> Does any one have a sample routing scripts for the client and server?

No sample scripts. Basic routing (server -> client and client -> server) needs no configuration at all. Larger setup are specific and cannot be handled with one single sample script.

Regards,
Didier

Here is the scenario.

  Client ======> IPROHC GW (Client) =========> ROUTING EQUIPMENT ============> IPROHC Server ======== Host To Access
10.255.254.2 ETH0 10.255.254.1 ETH5 192.168.3.14
                             iprohc 172.31.4.3 =======================================> iprohc_ipip 172.31.4.1
                               ETH3 10.23.207.2 ==========> 10.23.207.1

Script used on client:
#!/bin/bash
route add -host 192.168.3.14 gw 10.23.207.1 # Keep Alive
route del default gw 10.23.207.1
route add default gw 172.31.4.1

Tests:

Ping from client to IPROHC Server OK
Ping from IPROHC Client to IPROHC Server OK
Ping from IPROHC Server to IPROHC Client OK
Ping from IPROHC Server to Client not working

I can see the traffic passing from the Client and reaching the Host to Access, i have modified the routing of the network to send packets going to 10.255.254.0 to be sent to the IPROHC Server 192.168.3.14 but traffic is not returning.

Packets from the IPROHC Server to reach the IPROHC Client are routed via 192.168.3.254 to mantain the keep alive working

I have no firewall on the systems just ip forwarding on

So i am not shure how to route the packets back to the tunnel, do i have to modify routing tables in the server side?
Is the IPROHC Server aware of which networks arrive tru which IPROHC Client ?

That is why i asked for basic scripts to see what i am doing wrong.

Regards

> So i am not shure how to route the packets back to the tunnel,
> do i have to modify routing tables in the server side?

Yes. On server, add a route for 10.255.254.0/24 through gateway 172.31.4.3. Note that 172.31.4.3 may change at every client disconnection/connection. Another way to do it is to configure some IP masquerading on the tunnel interface at client.

> Is the IPROHC Server aware of which networks arrive tru which
> IPROHC Client ?

No.

Regards,
Didier