sajal83
Joined 16 years ago
Karma
1,569
Submissions
254
Member since
Aug 23
[ my public key: https://keybase.io/sajal; my proof: https://keybase.io/sajal/sigs/FRgz6WjRPcySo08oI3SNhMSFTWZlbqgxR9LZUck5MJM ]
View on Hacker NewsRecent submissions
Comment · 7 years ago
Most, if not all websites require more than one round trip.
Comment · 8 years ago
> The subscriber must be directly network-accessible and is identified by its Subscriber Callback URL
Does this mean the subscriber needs to have a forwarded port open to the internet for this to work? Without IPv6, users behind NAT (and specifically behind CGNAT) wouldn't be able to use it.
Comment · 8 years ago
I have a redundant 2 ISP setup, and use multipath TCP to use both of them at the same time.
A very outdated post about my setup : https://www.sajalkayan.com/post/fun-with-mptcp.html
I now have 2 broadband ISPs, and optionally I can hook in my phone's 4g into the mix.
Multipath TCP allows me to "mix" bandwidth of both ISPs at the same time.
Comment · 8 years ago
My policy: if email is interesting/relavent. Do nothing.
If I remember subscribing and haven't attempted to unsubscribe in the past, attempt to unsubscribe. Spending max 10 seconds.
All other situations, hit "mark as spam"
Comment · 8 years ago
I currently run my own (DNSSEC validating) Bind. But it has some drawbacks. For occasionally visited sites/tlds, my bind would need to contact root more often than if using a shared resolver.
Comment · 8 years ago
https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad...
Some traceroutes captured during the incident. The results that show "Target unreachable" were the ones seeing the hijacked paths.
Comment · 8 years ago
https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad...
Some traceroutes captured during the incident. The results that show "Target unreachable" are the ones seeing the hijacked paths
Comment · 8 years ago
The bad routes can be seen by agents: 219-YVR-Canana, 221-qeast, 16-TurboBytes, 6-VPS TH, 10-TurboBytes, 220-TurboBytes, 17-aks-seattle and 190-ATT-AS7018
From outages mailing list, following subnets were affected.
205.251.192.0 205.251.193.0 205.251.195.0 205.251.197.0 205.251.199.0
The issue has since been fixed, outage lasted for ~2 hours.
If you are still using a single DNS provider for your domain, you should consider having a dual-provider setup.