Apparently the last patch I published did not compile at all. Thanks to Fab this should be fixed now.
As usual you can get it here.
Apparently the last patch I published did not compile at all. Thanks to Fab this should be fixed now.
As usual you can get it here.
Discussion
The current patch should compile just fine with 3.8. I tested compilation with a 3.8rc kernel.
nat helping doesn't seem to work, same setup works ok with 3.7
I also have issues with 3.10 ..
It starts to work but fails in the help_out function and stops.
Any idea ?
It still has the same name but apparently has some fixes.
I tried also tried the 3.7 and 3.7-v2 but seem to be the same code
60dff6a41107fc8fa6f8a5f41e15ab21946d6b75 rtsp-module-3.7-v2.tar.gz
[1103542.473559] nf_conntrack_rtsp v0.7 loading
[1103542.473566] port #0: 554
[1103542.473702] nf_nat_rtsp v0.7 loading
[1103548.253281] conntrackinfo = 2
[1103548.255962] IP_CT_DIR_REPLY
[1103548.257511] IP_CT_DIR_REPLY
[1103548.257866] found a setup message
[1103548.257873] tran='Transport: RTP/AVP;unicast;client_port=8730-8731
[1103548.257873] '
[1103548.257876] lo port found : 8730
[1103548.257878] udp transport found, ports=(1,8730,8731)
[1103548.257881] setup expectation for rtcp
[1103548.257884] expect_related 212.27.38.253:0-0-MYIP:8730-8731
[1103548.257886] NAT rtsp help_out
[1103548.261106] IP_CT_DIR_REPLY
[1103548.262602] IP_CT_DIR_REPLY
[1103550.664598] teardown handled
As for the error you get. Was this working with earlier kernel versions?
My problem is that since I no longer have a linux router at home I can only compile test it.
But Panagiotis Malakoudis seems to have the same issue and it worked for him on the 3.7
It's not a server I want to reboot ...
but not the mangle and not ones
does not return a pointer to the actual protocol string..
So I try to retrieve the pointer using skb_header_pointer...
Will let you know
http://pastebin.com/JGw6QKVN
http://pastebin.com/XsyyCxzW