Iprohc client doesn't work

Asked by gordon

Hi, I'm sorry to ask a dummy question.
I have set my server part and it works well

client server
192.168.136.142 <-----> 192.168.136.138

But, when I follow the client part

"There is no init script on client-side, so you have to start it manually on command line. Run this command as root:

# iprohc_client --remote X.X.X.X --port 3126 --dev iprohc --p12 /path/to/client1.p12"

I use
# iprohc_client --romote 192.168.136.138 --port 3126 --basedev eth0 --dev iprohc --p12 /home/gordon/demoCA/client.p12

When I enter this command, it seems to invoke something.
However, I grep nothing after typing "# grep iprohc_client /var/log/messages | tail -n 20"

I don't know what's wrong.

Does anyone has the same problem?

Gordon

Question information

Language:
English Edit question
Status:
Expired
For:
rohc Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
gordon (gordon0730) said :
#1

hi guys, I give up using the rohc_clien/rohc_tunnel.
I refer this page https://rohc-lib.org/wiki/doku.php?id=rohc-tunnel
and use rohctunnel.
Every setting in this page seems ok.
When i ping to the target, it shows:
decompression of packet #1 failed
-------------------------------
ROHC packet (81 bytes):
01 0a 00 00 02 0a 00 00 01 00 40 00 00 a0 00 2b
bc 08 00 74 58 18 08 00 01 cc ae 6a 54 3f 98 0a
00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16
17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26
27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36
37
-------------------------------
[rohc_decomp.c:1351 rohc_decompress3()] given feedback_send is not empty
....
....
....
rohctunnel: rohc_buf.c:100: rohc_buf_push: Assertion `buf->offset >= offset' failed.

It says the bug is rohc_buf.c:100 because of assertion failed. But I think this bug comes from the decompression error, right?
Does any one have the same problem?

Revision history for this message
Didier Barvaux (didier-barvaux) said :
#2

Hello,

> I use
> # iprohc_client --romote 192.168.136.138 --port 3126 --basedev eth0 --dev iprohc --p12 /home/gordon/demoCA/client.p12
>
> When I enter this command, it seems to invoke something.
> However, I grep nothing after typing "# grep iprohc_client /var/log/messages | tail -n 20"
>
> I don't know what's wrong.
>
> Does anyone has the same problem?

Be careful, you misspelled the --remote option.

What version of the IP/ROHC client do you use? To get the answer:
$ iprohc_client --version

You may got more details by adding the --debug option:
# iprohc_client --debug --remote 192.168.136.138 --port 3126 --basedev eth0 --dev iprohc --p12 /home/gordon/demoCA/client.p12

Regards,
Didier

Revision history for this message
Didier Barvaux (didier-barvaux) said :
#3

Hello,

> hi guys, I give up using the rohc_clien/rohc_tunnel.
> I refer this page https://rohc-lib.org/wiki/doku.php?id=rohc-tunnel
> and use rohctunnel.
> Every setting in this page seems ok.
> When i ping to the target, it shows:
> decompression of packet #1 failed
> -------------------------------
> ROHC packet (81 bytes):
> 01 0a 00 00 02 0a 00 00 01 00 40 00 00 a0 00 2b
> bc 08 00 74 58 18 08 00 01 cc ae 6a 54 3f 98 0a
> 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16
> 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26
> 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36
> 37
> -------------------------------
> [rohc_decomp.c:1351 rohc_decompress3()] given feedback_send is not empty
> ....
> ....
> ....
> rohctunnel: rohc_buf.c:100: rohc_buf_push: Assertion `buf->offset >= offset' failed.
>
> It says the bug is rohc_buf.c:100 because of assertion failed. But I think this bug comes from the decompression error, right?
> Does any one have the same problem?

I tested the rohctunnel app of the 1.7.0 release. It indeed fails. I didn't test it enough before the release because it is deprecated. Please test the patch I just made: http://bazaar.launchpad.net/~didier-barvaux/rohc/rohc-1.7.x/revision/1189

Regards,
Didier

Revision history for this message
Launchpad Janitor (janitor) said :
#4

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Revision history for this message
gordon (gordon0730) said :
#5

Hi, sorry about being late here. After upgrading 1.7.x, it works well! Thanks for your help!