[#] Wed Aug 03 2016 09:23:57 EDT from IGnatius T Foobar @ Uncensored
Well I was actually just issuing some dry humor there, but now I'm going to have to try using .0 and see if it works.
Of course, if you want to confuse the heck out of people, use .0 or .255 in a network that's bigger than /24. For example, 172.16.1.0/23 or 172.16.0.255/23.
That'll quickly call out the people who don't know how to think in CIDR and only understand octets. (ProTip: these are the same dweebs who still refer to a /24 network as "a Class C," particularly when they are requesting /24 of public IPv4 space for their rack of three servers. Not gonna happen in 2016.)
I've seen it used successfully in a class before. It gave me a double-take, as it isn't very conventional.
[#] Fri Sep 02 2016 09:41:15 EDT from IGnatius T Foobar @ Uncensored
Someone just asked me what route metrics to use to get hosts on a 192.168.60.0/24 network talking over a VPN to hosts on a remote 192.168.60.0/24 network.
The labor day weekend drinking is going to have to start early, I think.
[#] Fri Sep 02 2016 10:50:06 EDT from LoanShark @ Uncensored
Use the auto-recombobulator with transparent bidirectional DS-NAT. And then punch the dumb fuck in the face.
[#] Mon Sep 12 2016 14:15:07 EDT from LoanShark @ Uncensored
The punching or the DS-NAT?
DS-NAT. Punching is straightforward, unless you plan to use a right hook.
Go to page: