[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: binding problem.
- To: heimdal-discuss@sics.se
- Subject: Re: binding problem.
- From: Enrico Pelletta <enrico@it.kth.se>
- Date: Fri, 15 Nov 2002 15:33:46 +0100
- In-Reply-To: <3DBFBAEA.50603@it.kth.se>
- Organization: IT-Universitetet/KTH
- References: <3DBFBAEA.50603@it.kth.se>
- Sender: owner-heimdal-discuss@sics.se
- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021017
Hi!
I have played around the problem with Heimdal 0.5.1 kdc and Debian
Woody, and finally I found a sort of solution... I installed
heimdal-0.4e with the kadmin patch! So kth-krb 1.2.1 and heimdal 0.4e
works fine on Debian Woody. No idea about why 0.5.1 failed! However, I
tried to install 0.5.1 and kth-krb 1.2.1 on a RedHat 8.0 machine, and
they work fine.
In order to successfully build heimdal 0.4e I had to do an horrible
patch. At line 878 and 915 I changed the variable krb_error_base with
ERROR_TABLE_BASE_krb. the first one does not exist, the second I took it
from the heimdal 0.5.1 source... How could it happen? Did I use the
right variable to solve the problem?
Enrico.
Enrico Pelletta wrote:
> Hi!
>
> I got a problem using Heimdal 0.5.1 on Debian Woody. When running kdc
> the daemon does not bind the right IP addresses/ports. I attached to
> this mail what the command "netstat -lpn" shows when running kdc and the
> kdc.log. Note that the IP address 226.10.23.64 it's not configured in
> the machine! The only IP in use is 130.xxx.xxx.xxx.
> The network system seems to works fine, and when I stop the kdc daemon
> all the anomalies disappear.
>
> I installed heimdal 0.5.1 together with KTH-krb 1.2.1 and I'm using a
> customized kernel 2.4.18 built from the Debian 2.4.18 kernel source.
> Becuase the machine I use is part of a testbed, and it's not going to be
> a production server, I included many advanced options in the networking
> support of the kernel. I wonder if some of them could have generated the
> problem I tried to describe. Any suggestion?
> Thanks,
>
> Enrico.
>
>
> ------------------------------------------------------------------------
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address
> State PID/Program name
> tcp 0 0 0.0.0.0:32768 0.0.0.0:*
> LISTEN 169/rpc.statd
> tcp 0 0 0.0.0.0:515 0.0.0.0:*
> LISTEN 180/lpd
> tcp 0 0 0.0.0.0:37 0.0.0.0:*
> LISTEN 808/inetd
> tcp 0 0 226.10.23.64:4360 0.0.0.0:*
> LISTEN 2579/kdc
> tcp 0 0 226.10.23.64:520 0.0.0.0:*
> LISTEN 2579/kdc
> tcp 0 0 226.10.23.64:8 0.0.0.0:*
> LISTEN 2579/kdc
> tcp 0 0 0.0.0.0:9 0.0.0.0:*
> LISTEN 808/inetd
> tcp 0 0 0.0.0.0:13 0.0.0.0:*
> LISTEN 808/inetd
> tcp 0 0 0.0.0.0:111 0.0.0.0:*
> LISTEN 104/portmap
> tcp 0 0 0.0.0.0:113 0.0.0.0:*
> LISTEN 808/inetd
> tcp 0 0 0.0.0.0:754 0.0.0.0:*
> LISTEN 808/inetd
> tcp 0 0 0.0.0.0:22 0.0.0.0:*
> LISTEN 187/sshd
> tcp 0 0 0.0.0.0:25 0.0.0.0:*
> LISTEN 808/inetd
> udp 0 0 0.0.0.0:32768 0.0.0.0:*
> 169/rpc.statd
> udp 0 0 0.0.0.0:769 0.0.0.0:*
> 169/rpc.statd
> udp 0 0 226.10.23.64:4360 0.0.0.0:*
> 2579/kdc
> udp 0 0 226.10.23.64:520 0.0.0.0:*
> 2579/kdc
> udp 0 0 226.10.23.64:8 0.0.0.0:*
> 2579/kdc
> udp 0 0 0.0.0.0:9 0.0.0.0:*
> 808/inetd
> udp 0 0 127.0.0.1:88 0.0.0.0:*
> 2579/kdc
> udp 0 0 127.0.0.1:4444 0.0.0.0:*
> 2579/kdc
> udp 0 0 127.0.0.1:750 0.0.0.0:*
> 2579/kdc
> udp 0 0 0.0.0.0:111 0.0.0.0:*
> 104/portmap
> Active UNIX domain sockets (only servers)
> Proto RefCnt Flags Type State I-Node PID/Program
> name Path
> unix 2 [ ACC ] STREAM LISTENING 309 192/xfs
> /tmp/.font-unix/fs7100
> unix 2 [ ACC ] STREAM LISTENING 297 180/lpd
> /dev/printer
> unix 2 [ ACC ] STREAM LISTENING 570 277/gpm
> /dev/gpmctl
>
>
> ------------------------------------------------------------------------
>
>
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 88/udp
> 2002-10-30T11:45:24 listening on IPv4:130.xxx.xxx.xxx port 88/udp
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 88/tcp
> 2002-10-30T11:45:24 bind IPv4:130.xxx.xxx.xxx/88: Address already in use
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 750/udp
> 2002-10-30T11:45:24 listening on IPv4:130.xxx.xxx.xxx port 750/udp
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 750/tcp
> 2002-10-30T11:45:24 bind IPv4:xxx.xxx.xxx.xxx/750: Address already in use
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 4444/udp
> 2002-10-30T11:45:24 listening on IPv4:130.xxx.xxx.xxx port 4444/udp
> 2002-10-30T11:45:24 listening on IPv4:127.0.0.1 port 4444/tcp
> 2002-10-30T11:45:24 bind IPv4:130.xxx.xxx.xxx/4444: Address already in use