Re: kern/40139: bridge(4) does not transmit DHCP replies to tap(4)

[Quentin Garnier <cube%cubidou.net@localhost>]

The following reply was made to PR kern/40139; it has been noted by GNATS.

From: Quentin Garnier <cube%cubidou.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/40139: bridge(4) does not transmit DHCP replies to tap(4)
Date: Sat, 21 Mar 2009 20:09:51 +0100

 --wayzTnRSUXKNfBqd
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Dec 09, 2008 at 09:00:01AM +0000, Taylor R Campbell wrote:
 > >Number:         40139
 > >Category:       kern
 > >Synopsis:       bridge(4) does not transmit DHCP replies to tap(4)
 
 It's not an issue with tap(4) (the same happens if you replace it with
 any other Ethernet interface).  If you run ktrace on dhclient, you'll
 see that it receives the packet on its udp socket for port 68.  I don't
 know why it rejects it though.
 
 --=20
 Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost
 "See the look on my face from staying too long in one place
 [...] every time the morning breaks I know I'm closer to falling"
 KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
 
 --wayzTnRSUXKNfBqd
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.9 (NetBSD)
 
 iQEcBAEBAgAGBQJJxTt/AAoJENgoQloHrPno94wH/RCpQBsD5XWolFC001FDUwJv
 DttTSmddwgegTKf9iMsl+/TLg49kNCjwUrEfKt4MTyGi0rL/DH+6fFR9fhU4klDu
 IZnxCd087gsIe4Lln4e5SjyoZlr6MYTXn72lIOehKT9kuzGhFgulATxUR+Ehya+P
 Vtmtp20uL/1plkUA7chhRbcoeuP/FkZ1u4caNf5eAVUOjK1IPfcJckTx64urfnXd
 pR1jUlQ35fgOCVGw/D8VYjlKpphFSDl9J1ywCyU8wUJy0njGzM4NicmhQ5Bbv9pN
 LHeNZOEVgweV0X8hembwVV1giV8OoEKQZ+U3QNgRnZ9iaU2G7GPafiQIVCJu3HQ=
 =H5u6
 -----END PGP SIGNATURE-----
 
 --wayzTnRSUXKNfBqd--