[Bug 189949] Review Request: mystun - STUN (Simple Traversal of UDP through NATs) server

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: mystun - STUN (Simple Traversal of UDP through NATs) server


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189949





------- Additional Comments From wolfy at nobugconsulting.ro  2007-03-15 10:43 EST -------
The very first time I tried to start the server after editing
etc/sysconfig/mystun. I've performed the manual tests because using the  init.d
script was not successfull:
[root]# cat /etc/sysconfig/mystun
### mystun NAT traversal server
###
### For correct operation, the mystun-server has to bind to two different
### ip addressed. Please configure your server accordingly and specify
### these two addresses here.
###

# First Interface
int1="192.168.1.1"
# Second Interface
int2="192.168.50.31"
# extra options
extra_opts=""

[root]# service mystun start
Starting mystun server: using intefaces:0 and 1
pid file contains old pid, replacing pid
                                                           [  OK  ]
[root]# service mystun status
mystun dead but subsys locked


[root]# /usr/sbin/mystun-server -i 192.168.50.31,192.168.1.1
using intefaces:0 and 1
strange family 0 skipping...
strange family 29797 skipping...
strange family 0 skipping...
strange family 0 skipping...
strange family 29797 skipping...
strange family 0 skipping...
Located interfaces
    [127.0.0.1] ip->127.0.0.1
Before daemonize pid is [28817] parent [28757]
Sending FROM: 127.0.0.1:3478
NOTICE:udp init succeded 3
Sending FROM: 127.0.0.1:3479
NOTICE:udp init succeded 4
init_ss: BUG: unknown address family 0
ERROR: udp_init: could not init sockaddr_union
ERROR:udp init failed
Unable to udp_init alternate_address
Initialazing failed ... code -1


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.