You're absolutely right. Plain -b makes it listen on ALL via IPv6, while -b0.0.0.0 makes it listen via IPv4. Both methods allow me to connect via the public domain name. However, when I use either method (even IPv4) and I try to approach cherokee-admin via localhost (via an SSH tunnel, ssh -L 9090:localhost:9090 or -L 9090:127.0.0.1:9090) I get this error from cherokee-admin: > channel 3: open failed: connect failed: Connection timed out
If I didn't have the bind() issue when trying to listen on localhost only, I'd think this was just an SSH problem. I'm not sure whether it does work with localhost via IPv6, since I don't know how to open an SSH tunnel via IPv6. Any ideas? P.S. Sorry about that private reply (again!) On 16 May 2010 01:13, andor.pierdelacabeza.com <[email protected]> wrote: > Hi Peter... > > Kind of funny becase if I open cherokee-admin with -b : > > tcp6 0 0 :::9090 :::* LISTEN > 13508/cherokee-admi > > and with -b0.0.0.0: > tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN > 13515/cherokee-admi > > So it appears that, if you don't specify an ipv4 address on the -b option, > it does default to ipv6, and maybe that's the question... Should it answer > correctly when bind on ipv6? > > > Even answering on tcp6, I think > > On Sat, 15 May 2010 23:46:11 +0200, Peter-Paul van Gemerden <[email protected]> > wrote: >> Thanks for answering! >> >> I've been testing, and if you use just '-b' as a flag, it doesn't bind > to >>> all, you should use '-b0.0.0.0' if you wanna bind it to anything. Maybe >>> that >>> can be filed as a bug... >>> >>> You can check with 'netstat -ntap|grep cherokee' if does it bind to >>> 0.0.0.0:9090(anything) or your ip address. >>> >> >> If I use only -b, I get this from netstat: >> tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN >> 3387/sshd >> tcp 0 48 x.x.x.x:22 x.x.x.x:56916 ESTABLISHED >> 3886/sshd: ppvg [pr >> tcp6 0 0 :::9090 :::* > LISTEN >> 3958/cherokee-admin >> tcp6 0 0 :::80 :::* > LISTEN >> 3871/cherokee-worke >> tcp6 0 0 :::22 :::* > LISTEN >> 3387/sshd >> >> So it seems it's still mucking about with IPv6... >> >> Excuse me for the obvious question: are you using 'localhost' or >>> '127.0.0.1'? >>> >>> If you're using 127.0.0.1 we can discard the resolv interference. >>> >> >> Obvious questions are often the best! But I tried sudo cherokee-admin >> -b127.0.0.1 but it doesn't work: >> [15/05/2010 23:41:12.532] (critical) bind.c:284 - Could not bind() >> port=9090 >> (UID=0, GID=0) >> >> I'm not sure how to proceed. It seems IPv6 is still interfering, though > I >> don't see how; `cat /proc/sys/net/ipv6/conf/all/disable_ipv6` returns 1. >> >> >> With kind regards, >> Peter-Paul >> >> >> (P.S. Alvaro: my apologies for the private reply) > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
