On Mon, Oct 31, 2016 at 04:52:46AM +, Carlos Alcantar wrote:
> Hey Samual,
>
>
> you might want to check out the voice ops mailing list, might be a bit more
> relevant over there.
>
>
> https://puck.nether.net/mailman/listinfo/voiceops
Aside from voiceops, here's decade (or more?) old web
Hi John,
Thanks for the info and background.
One operational suggestion I have is … why link synthesis rules to a specific
DNS zone?
Most larger operators of auth DNS use an IP management tool, like BT Diamond
IPAM, BlueCat, or Infoblox. Oftentimes, allocations of IP space will not be on
clas
On 10/31/2016 14:42, William Herrin wrote:
On Mon, Oct 31, 2016 at 3:33 PM, Randy wrote:
Any idea how a traceroute (into my network) could end up this fubar'd?
Discovered this wierd routing while investigating horrendously slow speeds
(albeit no packet loss) to a particular ISP abroad.
Hi R
Nick,
Very cool, learn something new every day :)
[root@stellarfrost(~)]> nicinfo 103.11.67.167
# NicInfo v.1.1.1
[ NOTICE ] Terms of Service
1 By using the ARIN RDAP/Whois service, you are agreeing to the
RDAP/Whois Terms of Use
About https://www.arin.net/whois_tou.html
# Query t
Selphie Keller wrote:
> APNIC -> 103.11.64.0/22 -> then to WebNX 103.11.67.0/24, which would show
> the full chain and a proper abuse contact for this subnet.
the tl;dr on the thread scrollback was:
1. whois is irredeemably broken
2. use rdap, which supports referrals
3. open source RDAP client:
Hi,
I am trying to determine the physical diversity of the Zayo and Level3 networks
vis-a-vis each other on the European racetrack -
London/Amsterdam/Frankfurt/Paris/London. It is for a client of mine.
Regards,
Roderick.
On 10/31/16 4:20 PM, Olivier Benghozi wrote:
Hi Randy,
ECMP loadbalancing is most frequently done on layer3+layer4 headers, and
unixlike traceroute use UDP with increasing destination port number for each
packet (usually starting at 33434), which allows to see the different available
paths,
Hi,
I noticed this thread and wanted to provide some information, subnet
103.11.67.0/24 is not an illicit squat this subnet is apart of
103.11.64.0/22 which was transferred from APNIC to ARIN back this last
February and is listed publicly at
https://www.arin.net/knowledge/statistics/transfers.html
Hi Randy,
ECMP loadbalancing is most frequently done on layer3+layer4 headers, and
unixlike traceroute use UDP with increasing destination port number for each
packet (usually starting at 33434), which allows to see the different available
paths, as wrote William.
Would you want/need to stick
On Mon, Oct 31, 2016 at 3:33 PM, Randy wrote:
> Any idea how a traceroute (into my network) could end up this fubar'd?
> Discovered this wierd routing while investigating horrendously slow speeds
> (albeit no packet loss) to a particular ISP abroad.
Hi Randy,
This is per-packet load balancing. I
Happy monday all!
Any idea how a traceroute (into my network) could end up this fubar'd?
Discovered this wierd routing while investigating horrendously slow
speeds (albeit no packet loss) to a particular ISP abroad.
It's like - coming into us - the packets are taking every available
path,
On 30/10/2016 12:43 AM, Eric S. Raymond wrote:
> Ronald F. Guilmette :
>> Two kids with a modest amount of knowledge
>> and a lot of time on their hands can do it from their mom's basement.
>
> I in turn have to call BS on this. If it were really that easy, we'd
> be inund
On Fri, Oct 28, 2016 at 7:36 PM, Ronald F. Guilmette
wrote:
> In my own defense, I didn't see the ARIN allocation because I have a
> normative process that I use for looking up IP addresses. It's
> hierarchical, and I always start with whatver whois.iana.org has to
> say. And it says that that
Ronald F. Guilmette wrote:
>
> You are correct. In this case, it would have been helpful if APNIC's WHOIS
> server returned something, when queried about 103.11.67.105, that would
> include an explicit referral to the ARIN WHOIS server. I mean they
> obviously know all the transfers they've made
14 matches
Mail list logo
