rohc team mailing list archive

[AITelecom <question248894@xxxxxxxxxxxxxxxxxxxxx>]

Question #248894 on rohc changed:
https://answers.launchpad.net/rohc/+question/248894

    Status: Needs information => Open

AITelecom gave more information on the question:
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

-- 
You received this question notification because you are a member of ROHC
Team, which is an answer contact for rohc.