On Sun, 5 Jul 2015 08:55:28 +0200 Petter Adsen <[email protected]> wrote:
> Maybe machine2 has no ip6tables rules, or rules that allow the access, > and machine1 blocks it? Or maybe only machine2 has IPv6 enabled? > machine2 is a very recent install directly from jessie. machine1 is also jessie, but dist-upgrade. netstat -a shows tcp6 on both machines. > > ?? > > > > i then tried modifying the config file to listen =NO but leaving ipv6 > > commented, and it doesn't work that way. > > No, it probably doesn't listen on IPv6 by default, and now you're > telling it to not listen on IPv4 either. > listen=NO means to run it standalone instead of from inetd. I don't believe it has anything to do with ipv6/ipv4. > I'm certainly no networking expert, so these are just guesses. > well i have configured BOTH machines thusly : listen=YES #listen_ipv6=YES and then it works on BOTH machines. This most certainly points to some issue with IPV6. There is a problem here, one I should most likely fix, but i can't figure out what it is. Brian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
