Re: Status of Heimdal and Amavis
On Thu, Jan 30, 2003 at 08:29:33AM +0100, Mikael Andersson wrote:
> > Heimdal appears to work fine, as far as I could test it on sid.
> > Hence I will upload it to Debian ASAP.
> >
> > However, the version I compiled for woody is a different
> > story.
> >
> > snoopy:unstable:~# netstat --tcp -a -n -p | grep kdc
> > tcp 0 0 226.122.44.64:4352 0.0.0.0:* LISTEN 8355/kdc
> > tcp 0 0 226.122.44.64:512 0.0.0.0:* LISTEN 8355/kdc
> > tcp 0 0 226.122.44.64:4992 0.0.0.0:* LISTEN 8355/kdc
> > tcp 0 0 226.122.44.64:4993 0.0.0.0:* LISTEN 8355/kdc
> > tcp 0 0 226.122.44.64:4994 0.0.0.0:* LISTEN 8355/kdc
>
> Isn't addresses >= 224.0.0.0 Multicast addresses? Some kind of multicast
> address to the nearest kdc?
I don't think KDC is intentionally doing this though, especially when it
only does so on stable. Also, I can't imagine why a KDC would want
to multicast or receive multicast packets.
The kernel on this computer doesn't have CONFIG_IP_MULTICAST defined...
The log file, when starting says:
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 88/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 88/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 88/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 88/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 88/udp
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 88/tcp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 88/tcp
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 88/tcp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 88/tcp
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 88/tcp
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 750/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 750/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 750/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 750/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 750/udp
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 750/tcp
2003-01-31T10:25:50 bind IPv4:192.168.87.1/750: Address already in use
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 750/tcp
2003-01-31T10:25:50 bind IPv4:192.168.87.1/750: Address already in use
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 750/tcp
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 4444/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 4444/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 4444/udp
2003-01-31T10:25:50 listening on IPv4:192.168.87.1 port 4444/udp
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 4444/udp
2003-01-31T10:25:50 listening on IPv4:127.0.0.1 port 4444/tcp
2003-01-31T10:25:50 bind IPv4:192.168.87.1/4444: Address already in use
2003-01-31T10:25:50 listening on IPv4:203.12.237.110 port 4444/tcp
2003-01-31T10:25:50 bind IPv4:192.168.87.1/4444: Address already in use
2003-01-31T10:25:50 listening on IPv4:203.12.237.97 port 4444/tcp
For:
snoopy:unstable:~# netstat --tcp -a -p -n | grep kdc
tcp 0 0 226.122.44.64:4352 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:512 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:1856 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:1857 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 203.12.237.97:750 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 203.12.237.110:750 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 203.12.237.97:4444 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 203.12.237.110:4444 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:1853 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:1854 0.0.0.0:* LISTEN 1633/kdc
tcp 0 0 226.122.44.64:1855 0.0.0.0:* LISTEN 1633/kdc
I fail to see a relationship between the log file and the netstat
output... Port 88 simply vanished.
(also don't ask why it is trying to bind to 192.168.87.1 multiple times,
yet 192.168.87.1 doesn't show up once in netstat).
--
Brian May <bam@debian.org>
Reply to: