nitinics

6 ms·

31.
by nitinics 12y ago
Thanks for posting this. This is an April Fool's day RFC. Similar hilarious RFCs are posted almost every year on 1st of April. Check out the list here http://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_..
32.
by nitinics 12y ago
With the advent of DNSSEC, IPv6 and EDNS0 you're more likely to see DNS responses >512 bytes, therefore falling back to TCP (with truncate bit set). Therefore it is strongly recommended you do not drop/block tcp 53 on your midd
33.
by nitinics 12y ago
Indeed. It would be interesting to know the distance between two AZs, provided 2ms is the RTT. And considering many factors including - switching and network latency including encryption / decryption on cross AZ traffic (if they do)
34.
by nitinics 12y ago
They do have interesting infrastructure v6 prefixes too. >> snip << 5 be2.bb01.iad3.tfbnw.net (2620:0:1cff:dead:beef::6b8) 37.323 ms 37.332 ms 37.326 ms 6 be13.bb02.frc3.tfbnw.net (2620:0:1cff:dead:beef::16c0) 37.6
35.
by nitinics 12y ago
From what I am reading, it runs on Multi-Use Radio Service (MURS). i.e. 151-154 Mhz spectrum. Excerpt From https://apps.fcc.gov/edocs_public/attachmatch/FCC-02-139A1.p... Under the revised rules, MURS units are:
36.
by nitinics 12y ago
FYI http://www.nsi.edu.np/?option=com_content&func=details&id=36 . This is the story about Nick. How he went to Nepal, worked there, grew fonder and after his death - still lives with the organization that helps trai
37.
by nitinics 12y ago
You can always create multiple routing instances (namespaces) for overlapping IPv4 blocks with a VRF-based strategy. This would create separate FIBs and IMHO is a cleaner approach than mangling packets with iptables.