UnrealIRCd Forums

Hi, its me again... Ive double checked the docs and the confs, and whereas the server is running fine and links with the network fine when a user tries to connect via ipv6 they still pull an ipv4 addy. Here are my listen blocks:

listen [::ffff:65.110.53.32]:6660 {
options {
ssl;
};
};

listen [::ffff:65.110.53.32]:6667;
listen [::ffff:65.110.53.32]:6668;
listen [::ffff:65.110.53.32]:6669;
listen [::ffff:65.110.53.32]:7000;

------- The server seems to listen fine on all those ports, but does not recogonize the ipv6 addresses. Any thoughts why?

Problem was [] in IP and user got supported in #Unreal-Support

Gizmo967 wrote:Problem was [] in IP and user got supported in #Unreal-Support

Well no Yea I was the one that was helped that was the link block hostname part. This is the listen block... I tried without the [] and whereas the server starts fine, I get connection refused errors:

[3:18pm] * Connect retry #11 desync.epicirc.net (6667)
[3:18pm] * Unable to connect to server (Connection refused)
[3:18pm] * Connect retry #12 desync.epicirc.net (6667)
(%) *** Looking up your hostname...

On connect retry #12 i had rehashed with the [] back in there.

Ah yes, it was link problem with IPv6
My bad

Gizmo967 wrote:Ah yes, it was link problem with IPv6
My bad

It's ok dont beat yourself up too much. :

For the rest of you I still need help!!! hehe

All of those IPs are v4, I'm not sure I understand what the problem is here...

codemastr wrote:All of those IPs are v4, I'm not sure I understand what the problem is here...

Thats the listen block, should it be the ipv6 address and not the ipv4 one? Should there be 2? 1 for the ipv4 and one for the ipv6?

does not recogonize the ipv6 addresses.

Which means...? What does it do/say? (check log etc)

Syzop wrote:

does not recogonize the ipv6 addresses.

Which means...? What does it do/say? (check log etc)

When someone connects using ipv6 i only get an ipv4 address. Dont see any errors or anything.

- What OS are you on?
- Try looking at 'netstat -an' output to see at which socket it actually binds (on Linux 'netstat -anp|grep irc' is usually helpful)

Syzop wrote:- What OS are you on?
- Try looking at 'netstat -an' output to see at which socket it actually binds (on Linux 'netstat -anp|grep irc' is usually helpful)

RH Linux Unreal3.2


tcp 0 0 ::ffff:65.110.53.3:6660 :::* LISTEN 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6667 :::* LISTEN 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6668 :::* LISTEN 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6669 :::* LISTEN 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:7000 :::* LISTEN 27533/ircd
tcp 0 0 :::39807 :::* LISTEN 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6667 ::ffff:200.93.114.:4838 ESTABLISHED 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6667 ::ffff:68.91.108.2:3217 ESTABLISHED 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6667 ::ffff:67.65.16.9:50506 ESTABLISHED 27533/ircd
tcp 0 0 ::ffff:65.110.53.3:6660 ::ffff:66.98.152.:43577 ESTABLISHED 27533/ircd
udp 0 0 0.0.0.0:33712 0.0.0.0:* 27533/ircd
unix 2 [ ] DGRAM 2264334 27533/ircd


And the established ones are linked servers. No users have connected with it. desync.epicirc.net

Thanks

Actually I'm lost too now.

You bind to ""IPv4"" address (::ffff:<ipv4ip>) and then you are surprised nobody can connect to you using ipv6? ;). To have ipv6 users able to connect you would have to bind to a real IPv6 addr of course.

Syzop wrote:Actually I'm lost too now.

You bind to ""IPv4"" address (::ffff:<ipv4ip>) and then you are surprised nobody can connect to you using ipv6? . To have ipv6 users able to connect you would have to bind to a real IPv6 addr of course.

I see... so would it be right to do like:

listen 22.22.22.22:6667;

listen 102:9393:94b:02:6667;

So make 1 listen entry for the ipv6 addy at ipv6:port and one on the ipv4:port correct? Then people can connect using either?

listen 102:9393:94b:02:6667;

Well first off, that's a 100% illegal IPv6 address. And second, that's not even the correct notation to specify an IPv6:port.

[::1]:6667; /* The IPv6 equivilent of 127.0.0.1:6667 */

[::1]:6667; /* The IPv6 equivilent of 127.0.0.1:6667 */[/quote]

Well outta convience I didnt write the real one out.

So.. would it be like:

listen [3ffe:bc0:eca::58]:6667;

?