Re: [reTurn-devel] Wireshark reports malformed STUN packets from reTurn
Hi Eric,
First off - what version of reTurn are you using? I would recommend with SVN head or resiprocate version 1.5 tarball. Those versions of return have passed all of the STUN message tests from draft-ietf-behave-stun-test-vectors-04.
One thing to keep in mind is that reTurn implements the lastest stun rfc 5389. RFC 5389 is relatively new and specifies a new SOFTWARE header - this is what's causing Wireshark to show a malformed packet. However stun clients should be ignoring headers they don't understand, so this should be causing any issues. If you want to avoid placing that header in the STUN messages from reTurn you can change line 145 of RequestHandler.cxx to say if(0) instead of if(1) - I eventually want to make this a setting.
Note: I'll provide some more info in response to your other posting.
Thanks,
Scott
On Fri, Jul 24, 2009 at 7:17 PM, Eric Chamberlain
<eric@xxxxxx> wrote:
Hello,
While troubleshooting a Linksys SPA942 STUN issue, I noticed that Wireshark (1.2.1 OS X build) reports that the STUN response packets are malformed.
Is there an issue with the STUN response packets, or is wireshark giving a false indication?
--
Eric Chamberlain, Founder
RF.com - http://RF.com/
_______________________________________________
reTurn-devel mailing list
reTurn-devel@xxxxxxxxxxxxxxx
List Archive: http://resiprocate.org/archive/return-devel/