Thanks for this grate work, but is still not working.
Is it normal, that the patch is not merging 100% of it all?
> patching file net/ipv4/netfilter/nf_nat_sip.c
> Hunk #1 FAILED at 67.
> Hunk #2 FAILED at 82.
> Hunk #3 FAILED at 129.
> Hunk #4 FAILED at 197.
> Hunk #5 succeeded at 236 with fuzz 1.
> Hunk #6 FAILED at 275.
> Hunk #7 FAILED at 300.
> 6 out of 7 hunks FAILED -- saving rejects to file
net/ipv4/netfilter/nf_nat_sip.c.rej
> patching file net/netfilter/nf_conntrack_sip.c
> Hunk #1 FAILED at 376.
> Hunk #2 FAILED at 436.
> 2 out of 2 hunks FAILED -- saving rejects to file
net/netfilter/nf_conntrack_sip.c.rej
After recompile the module and load into the kernel, the same packets
goes trough the network:
ORIGINAL
IP ser02.de.sipgate.net.5060 > 91-64-xxx-116-dynip.superkabel.de.46696:
SIP, length: 1185
> v=0
> o=root 30469 30469 IN IP4 217.10.67.14
> s=session
> c=IN IP4 217.10.68.75
> t=0 0
> m=audio 44620 RTP/AVP 8 0 3 97 18 111 5 110
> a=rtpmap:8 PCMA/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:3 GSM/8000
> ...
NAT'ED
IP ser02.de.sipgate.net.5060 > 10.10.0.2.46696: SIP, length: 1184
> v=0
> o=root 30469 30469 IN IP4 217.10.79.9
> s=session
> c=IN IP4 217.10.79.9
> t=0 0
> m=audio 44620 RTP/AVP 8 0 3 97 18 111 5 110
> a=rtpmap:8 PCMA/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:3 GSM/8000
> ...
Mike.
Jerome Borsboom schrieb:
Michael,
I am not the maintainer of the NAT-SIP module. In the future, you
should post similar requests to the linux-net mailinglist where it can
be picked up by more skilled people. I have cross-posted my reply
there too.
The problem you describe is one of the reasons why, in general, you
shouldn't run SIP over NAT. However, I have attached a crude patch
that you can try that solved a similar problem for me. The patch
applies against current 2.6.21.5 source. If you want to use the patch
for anything earlier than 2.6.21.5, then you also need the patch that
I included at the very end of this reply.
Regards,
Jerome Borsboom
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
