John Andersen wrote:
Why not just nuke the line in hosts.allow and see if it comes back?
---- The line that was matching was: ALL: LOCAL, 192.168.3.0/255.255.255.0, [fe80:xxxxxxxx::192.168.3.0]/120]: ALLOW I'm thinking since it saw the IP6 addr on the same line, it converted the IP4 addr to an IP6 one. The fe80 isn't in use right now anyway, so put it on a separate line: ALL: LOCAL, 192.168.3.0/255.255.255.0 : ALLOW ALL: [fe80:xxxxxxxx::192.168.3.0]/120 : ALLOW Which, if I understand the access rules correctly means it should (crossing fingers)(?) match the 1st line 1st, if it is IPV4, and then the second line if it is an IPV6 addr (which I'm not really using right now, but have tried it out, and would like to leave it for experimenting...)... But never saw this message before this last month....and that line has been in there for probably a year or more...been a while since I tried config'ing my net for IPV6....decided it wasn't worth the overhead internally, and my ISP doesn't support it anyway (except in limited trials, not in my area!)... Will have to see if that changes anything. ------------------- To Per Andersen: I'm fairly certain -- I've never seen any reference to a need to put reverse dummy entries in for a dual-stack server ... (My DNS server isn't even returning IPv6 entries right now because IPv6 is unconfigured)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org