[GH-ISSUE #359] ipv6 bind support #136

New issue

Closed

opened 2026-02-27 08:15:27 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 08:15:27 +03:00

Owner

Originally created by @ldpr on GitHub (Nov 1, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/359

hello!

I've been testing this and it works great for systems on our internal network, which uses ipv4.

When we try connect from outside via ipv6 though, it's refused. It's not a firewall issue, IPs are already whitelisted.
It looks to only be binding on ipv4 addresses:

netstat -tulpn | grep lldap
tcp        0      0 0.0.0.0:3890            0.0.0.0:*               LISTEN      107866/lldap        
tcp        0      0 0.0.0.0:17170           0.0.0.0:*               LISTEN      107866/lldap

I'm not seeing a config option for which interface to bind to either, so presumably it's not implemented?

Would it be possible to get ipv6 support? We can continue without for the affected machines but it'd be really sweet to get everything working with LLDAP :)

Thanks so much for your work, it's an awesome project!

Originally created by @ldpr on GitHub (Nov 1, 2022). Original GitHub issue: https://github.com/lldap/lldap/issues/359 hello! I've been testing this and it works great for systems on our internal network, which uses ipv4. When we try connect from outside via ipv6 though, it's refused. It's not a firewall issue, IPs are already whitelisted. It looks to only be binding on ipv4 addresses: ``` netstat -tulpn | grep lldap tcp 0 0 0.0.0.0:3890 0.0.0.0:* LISTEN 107866/lldap tcp 0 0 0.0.0.0:17170 0.0.0.0:* LISTEN 107866/lldap ``` I'm not seeing a config option for which interface to bind to either, so presumably it's not implemented? Would it be possible to get ipv6 support? We can continue without for the affected machines but it'd be really sweet to get everything working with LLDAP :) Thanks so much for your work, it's an awesome project!