* Jussi Peltola <[email protected]> [2012-10-24 21:37]: > This is something that can only be fixed by getting rid of the > assumption about non-changing host addresses.
what a brilliant design. instead of fixing a networking problem at the networking layer change all the layers above, up to and including the application layer. but NAT is bad, right. > NATs tend to break my idle SSH sessions that is just one more of the lies spread all over the place. NAT doesn't have ANYTHING to do with that really. what you are seeing are broken devices throwing away state they must not. yes, they are common. and NAT is common. but blaming one on the other is still just wrong. > Do your ssh sessions stay up if one of your upstreams starts blackholing > but still announces you a full table of routes? now that is even more ridulous. the problem is blackholing, the solution is to not blackhole, not to apply gazillions of stupid workarounds. and guess what: in practice, accidental blackholing is extremely rare. -- Henning Brauer, [email protected], [email protected] BS Web Services, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
