Hello Robin!
> So the message that both server and client have is "Resource temporarily
> unavailable".
> Did someone have the same problem? How can this be solved?
Which operating system are you using? Do you have a firewall active? Make sure
nothing is blocking either server or client. If its still not working, use
Wireshark or tcpdump to check what's happening "on the wire".
I'm using Ubuntu 10.04 with 2.6.32-27 kernel.
So, I've been following your advice and put wireshark to check the packages on
the lo "wire". Besides the "Destination unreachable(Host unreachable)" message
that I receive I can see the flow from Source port 40673 to Destination port
23232 both on 127.0.0.1, of course. Is this (at least) flow's correct
behaviour? Besides this messages I don't get anything else.
I tried also another way to check what happens and used s_server and c_client
of openssl package.
~# openssl req -x509 -nodes -days 365 -newkey rsa:1024 -subj
'/C=CA/ST=ON/L=Ottawa/CN=www.madboa.com' -keyout mycert.pem -out mycert.pem
~# penssl s_server -cert mycert.pem -www -dtls1 &
~# openssl s_client -connect 127.0.0.1:4433 -dtls1
CONNECTED(00000003)
write:errno=111
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 0 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : DTLSv1
Cipher : 0000
Session-ID:
Session-ID-ctx:
Master-Key:
Key-Arg : None
PSK identity: None
PSK identity hint: None
Start Time: 1295872784
Timeout : 7200 (sec)
Verify return code: 0 (ok)
---
then I tried with 23232 port:
~# openssl s_client -connect 127.0.0.1:23232 -dtls1
CONNECTED(00000003) // That's all I receive.
Is there any default port for a DTLS session that openssl opens/uses?
Thanks again!
Sebastian
