home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!darwin.sura.net!convex!constellation!osuunx.ucc.okstate.edu!unx.ucc.okstate.edu!datacomm.ucc.okstate.edu!martin
- From: martin@datacomm.ucc.okstate.edu (Martin McCormick)
- Subject: Re: Bootleggers
- Message-ID: <1992Nov10.153000.10508@unx.ucc.okstate.edu>
- Sender: news@unx.ucc.okstate.edu (USENET News System)
- Organization: Oklahoma State University, Stillwater, OK
- References: <92309.135530HANK@BARILVM.BITNET> <1992Nov6.015854.2994@unx.ucc.okstate.edu>
- Date: Tue, 10 Nov 1992 15:30:00 GMT
- Lines: 18
-
-
- I want to really thank everybody who answered my question about what to do
- with or to those people who won't get with the program and register their
- network interfaces. Since certain actions had the potential for disrupting
- honest network users, I asked that the responses be E-mailed to me. I received
- 10 responses. Fortunately, most of the measures which can be taken to stop
- people from just picking an IP number and going full steam ahead are things
- that only network managers can do, assuming the network is configured properly.
- The best actions appear to be to tell all bridges or routers in your network
- not to handle any packets from X interface. If you can get everybody to
- go along, run versions of tcp-ip applications that do a nslookup on every
- connect request to see if they are in the name server data base. Between
- those two measures, the network should become a pretty boring place for
- bootleggers. Again, my thanks to all and also thanks for the recommendations
- for management software which I received from a couple of posters.
-
- Martin McCormick WB5AGZ Stillwater, OK
- O.S.U. Computer Center Data Communications Group
-