TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [TCLUG:8149] ssh and NAT



Maybe I'm not quite understanding what you're saying, but changing the box
or nic just gets him a new dynamically assigned IP address - why would he
call them up every time? 

If he's got a static ip, TTBOMK, they merely cut the static ip out of the
pool held by the dhcp server isolate it to his particular vlan. Totally
non-DHCP handled at that point.

Also, much of this is moot, as USWest is switching areas to PPP from
bridging faster and faster. I'd be suprised if there was any free bridging
left in the metro Jan 1st 2k.

-----Original Message-----
From: Daniel M. Debertin [mailto:katdan@mail.swdata.com]
Sent: Wednesday, September 08, 1999 4:12 PM
To: Unni Nambiar
Cc: 'tclug-list@mn-linux.org'
Subject: RE: [TCLUG:8149] ssh and NAT

<snip>
> I think DHCP works using a lease mechanism.  IP addresses are assigned for
a
> time period.  Even after we disconnect and reconnect (which i don't do
> anymore since i'm using DSL as a permanent connection).  I've always
> wondered how they identify that the same machine has connected.  In any
> case, i think its unlikely that my IP address could get reassigned
> on-the-fly. Right ?

Generally, if you're using DHCP, then they identify your box by MAC
address. Sucks, because you have to call them up every time you change a
box or a NIC

<snip>