Bad choice of words...what I should have said was that you have to have
access to their network to be able to use their broadband hardware. This
will tie you in at some point to their router.

> -----Original Message-----
> From: Andrew Blevins [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, October 31, 2001 10:00 AM
> To: '[EMAIL PROTECTED]'; 'Kutulu'; Andrew Blevins; 
> 'scott [gts]'; 'security-basics'
> Subject: RE: help - can someone explain this to me?
> 
> 
> They don't set you up to be "on" any router. The routers 
> simply direct traffic back and forth on their private 
> network. An @home user would have no need to connect directly 
> to any of their routers, and that is their point. However, 
> sometimes, like with our VPN, it can cause trouble. Legally, 
> they are right, but it's irritating! :-)
> 
> Andrew Blevins
> 
> 
> 
> -----Original Message-----
> From: Robert Clark [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 31, 2001 6:25 AM
> To: 'Kutulu'; 'Andrew Blevins'; 'scott [gts]'; 'security-basics'
> Subject: RE: help - can someone explain this to me?
> 
> 
> 
> 
> > Tracing route to www.securityfocus.com [66.38.151.10]
> > over a maximum of 30 hops:
> > 
> >   1    10 ms    10 ms    10 ms  10.58.34.1
> >   2   <10 ms    10 ms    20 ms  24.182.156.17
> >   3    51 ms    50 ms    50 ms  24.18.95.65
> >   4    40 ms    50 ms    40 ms  10.0.236.70
> >   5    40 ms    50 ms    40 ms  24.7.76.189
> > 
> > This is, in many people's opinion, a violation of RFC1918.
> > The engineers of the networks who use them answer with the 
> > equally valid point that their internal routers can have 
> > whatever internal IPs they want, I shouldn't be trying to 
> > connect directly to them anyway.  One of those religious wars 
> > you never really want to get into.
> 
>  That's a silly argument from them...if they set you up to be 
> on the router, then how are you NOT supposed to connect to them???
> 
> Robert Clark
> MCSE, MCP+I, MCP, A+
> MIS - Texas Cellular 
> 

Reply via email to