NetBSD Problem Report #18031

Received: (qmail 1361 invoked by uid 605); 22 Aug 2002 02:05:21 -0000
Message-Id: <20020822011229.D12CB174D2@arioch.imrryr.org>
Date: Wed, 21 Aug 2002 21:12:29 -0400 (EDT)
From: elric@imrryr.org
Sender: gnats-bugs-owner@netbsd.org
Reply-To: elric@imrryr.org
To: gnats-bugs@gnats.netbsd.org
Subject: kdc does not recognise when new addresses are added.
X-Send-Pr-Version: 3.95

>Number:         18031
>Category:       bin
>Synopsis:       kdc does not recognise when new addresses are added.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 22 02:06:01 +0000 2002
>Closed-Date:    
>Last-Modified:  Thu Aug 22 09:31:00 +0000 2002
>Originator:     Roland Dowdeswell
>Release:        NetBSD 1.6_RC1
>Organization:
not much, all in all.
>Environment:
NetBSD mabelode.imrryr.org 1.6_RC1 NetBSD 1.6_RC1 (MABELODE) #0: Fri Aug 16 12:46:51 EDT 2002     elric@mabelode.imrryr.org:/usr/src/sys/arch/cobalt/compile/MABELODE cobalt
Architecture: mipsel
Machine: cobalt
>Description:
	kdc(8) decides what addresses to which it binds at start-up and
	even if you do not limit the listen addresses, it will not pick
	up interface changes.
>How-To-Repeat:
	run pppoe on your kdc.
>Fix:
	not provided, yet.

>Release-Note:
>Audit-Trail:

From: joda@pdc.kth.se (Johan Danielsson)
To: elric@imrryr.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/18031: kdc does not recognise when new addresses are added.
Date: 22 Aug 2002 11:30:38 +0200

 elric@imrryr.org writes:

 > 	kdc(8) decides what addresses to which it binds at start-up and
 > 	even if you do not limit the listen addresses, it will not pick
 > 	up interface changes.

 > >Fix:
 > 	not provided, yet.

 This is because the reply should come from the address it was sent
 to. Using kdc --addresses=0.0.0.0 should work for the KDC end, but the
 client uses connect and send/recv, so it should ignore data coming
 from the wrong address. I think that in this case, TCP is your friend.

 A possible longer term solution would be to listen to a routing
 socket, and add new addresses.

 /Johan
>Unformatted:

Home	PR Database Search