incoming.conf and IPv6

Russ Allbery rra at
Mon Feb 10 01:39:55 UTC 2003

Marco d'Itri <md at Linux.IT> writes:

> Looks like there is something wrong: on my test server I had this line
> in incoming.conf:

> peer attila { hostname: }

> and has 3FFE:1001:210:16:0:0:0:1 among its AAAA records,
> but after upgrading to -CURRENT and starting to feed
> articles from it to the test server via IPv6 it was not recognized
> anymore and passed to nnrpd:

> Jan 31 00:25:27 erode nnrpd[3940]: (3ffe:8171:10:16::1) connect
> Jan 31 00:25:27 erode nnrpd[3940]: noperm ihave without permission

> To make it accept articles I had to explicitly add the IP address:

> peer attila { hostname: ", 3ffe:8171:10:16::1" }

Just to mention before I move this one out of my ticked message queue, I
still have no idea on what's causing this and can't easily test.  Are
other people who are using IPv6 with CURRENT seeing this problem?

Russ Allbery (rra at             <>

    Please send questions to the list rather than mailing me directly.
     <> explains why.

More information about the inn-workers mailing list