XPost: comp.dcom.lans.ethernet   
   From: redelm@ev1.net.invalid   
      
   In comp.dcom.lans.ethernet Morten Reistad  wrote in part:   
   > They are still on some disk and in some logs where a court   
   > backed cop can get to them.   
      
   Sure.  Nothing obscure about it.  Just not easy for everyone   
   to do.  I did not claim this was undesireable.   
      
   > I would think getting promoted to default behaviour in   
   > windows would qualify as "going general" ? You have to give   
   > an ifconfig-command in a console window to turn it off.   
      
   Or as part of ubiquitous startup scripts.   
      
   > If they had a clue. Most of these schemes are deployed   
   > by people without an incling of a clue. Hint: The lead   
   > technician in a large corporation was unable to make a   
   > route/netmask out of 15 single IP addresses for a filter.   
      
   Again, you expect too much of people.  Sure, it would be   
   good if they knew.  But they don't have to, so they don't.   
   They've lasted this long without, and may have achieved   
   considerable success reinforcing their ignorance.  It would   
   be nice if people who maintained machines & systems also knew   
   enough to build them, but they don't.  They know different   
   things, often things the builders do not know.   
      
   > This means that garbage configs for cheap home deployment   
   > makes it onto large, corporate installations.   
      
   If it can be made to work for now, that is often good enough.   
   Cost pressures prohibit investing for the future.  Of course   
   corners are cut.  It looks stupid in hindsight, but might not   
   be in foresight--alot of futureproofing is thrown away when   
   _that_ future doesn't show up an a different one does instead.   
      
   >>I suppose that depends on the ISPs involved.  I've had no   
   >>trouble, and I've used lots of direct ssh over wireless.   
   >>At least halft the time, the connection stays up overnight.   
   >>But addr changes several times per hour might get annoying.   
   >   
   > VPN, or 6to4. Problem solved. My ip use went to 65% almost   
   > overnight. All repos, microsoft included, are ipv6 enabled.   
   > So are the gateway sites I use. It just makes the world so   
   > much barable. No more hanging sessions. And it is noticably   
   > faster, too.   
      
   But I do not have these problems!  I see no advantage with   
   VPN, and only use it when port fwding config require it.  I am   
   a bit surprised at your speedup.  Could it be going through   
   better router [software]?  IPv4 is somewhat the victim of its'   
   own success -- droped/mangled packets cause fairly silent   
   retransmits.  So you get alot of them at a cost in speed.   
      
   One thing I do to help IPv4 is work on MTU to minimize   
   fragmentation downstream.  My current favorite is 1454 octets.   
      
      
   -- Robert   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)