nanog mailing list archives
Re: identify hostname
From: Phillip Vandry <vandry () Mlink NET>
Date: Wed, 2 Dec 1998 11:40:37 -0500 (EST)
I've got to go with Pete K. on this one. In our current, cidr-ized world, it is simply not possible for an upstream provider to determine what is, or is not, a broadcast address in a downstream network. This is something that needs to be implemented from the edge in, not from the core out.
Don't forget that the original suggestion at the beginning of this thread was that UUnet should filter broadcast addresses on their Cisco routers because their Max TNT's couldn't do it, in other words take care of the networks on which the TNT's sit. It got escalated into a suggestion that they protect all their networks and all their customers networks in their core. Of course that's next to impossible! Point: Yes, people who have routers in their networks that can't be configured not to forward directed broadcasts should have this problem patched by filtering, (although it won't protect them from their own dialup users from being initiators) -Phil
Current thread:
- Re: identify hostname, (continued)
- Re: identify hostname Rusty Zickefoose (Dec 01)
- Re: identify hostname John Fraizer (Dec 01)
- Re: identify hostname Phil Howard (Dec 02)
- Re: identify hostname Pete Kruckenberg (Dec 02)
- Re: identify hostname Roeland M.J. Meyer (Dec 03)
- Re: identify hostname Jonathan Mischo (Dec 03)
- Message not available
- Re: identify hostname Roeland M.J. Meyer (Dec 03)
- Re: identify hostname Jonathan Mischo (Dec 03)
- Re: identify hostname Craig A. Huegen (Dec 02)
- Re: identify hostname Brandon Ross (Dec 02)
- Re: identify hostname Phillip Vandry (Dec 02)
- Re: identify hostname Craig A. Huegen (Dec 02)
- Re: identify hostname Steven J. Sobol (Dec 01)