Re: [swinog] Swinog #34 Ride on 30th - Geneva and Lausanne

Same train from Lausanne for me. -- Make the coupling between modules visible. - The Elements of Programming Style (Kernighan & Plauger) ――― Original Message ――― From: "lucas.dousse" Sent: 29 octobre 2018 20:08 +0100 Subject: Re: [swinog] Swinog #34 Ride on 30th - Geneva

[swinog] BGP LLGR, followup

Hey! A quick followup for my lightning talk from last year about BGP LLGR: - Support has been added in BIRD 1.6, BIRD 2 and GoBGP. AFAIK, Cisco still only supports it on VPN and FlowSpec families. - Draft 4 has been published and IANA has assigned capability code and well-known

Re: [swinog] IRR and trust

❦ 11 mars 2018 09:54 +0100, Vincent Bernat <ber...@luffy.cx> : >> Did you try contacting radb.net or the ARIN first? Their answers would >> be interesting about it. > > As I am not familiar with how things work, I did not. But I have mailed > CloudFlare NOC. They to

Re: [swinog] IRR and trust

❦ 11 mars 2018 09:49 +0100, Vincent Jardin  : > Did you try contacting radb.net or the ARIN first? Their answers would > be interesting about it. As I am not familiar with how things work, I did not. But I have mailed CloudFlare NOC. -- Localise input and output in

Re: [swinog] IRR and trust

❦ 10 mars 2018 23:02 +0100, Vincent Bernat <ber...@luffy.cx> : > I am peering with Atlantic Metro at DE-CIX. Their IRR record is > "AS-AMC". I have noticed recently some invalid prefixes: > > $ bgpq3 -4 -R 24 -m 24 -A -J -E AS-AMC > [...] > route-filt

[swinog] IRR and trust

Hey! I am peering with Atlantic Metro at DE-CIX. Their IRR record is "AS-AMC". I have noticed recently some invalid prefixes: $ bgpq3 -4 -R 24 -m 24 -A -J -E AS-AMC [...] route-filter 1.0.0.0/24 exact; route-filter 1.1.1.0/24 exact; I didn't check which members of the macro pulled

[swinog] RIPE database and more specific routes

Hey! I am updating the route/inetnum objects in the RIPE database and I am wondering if I have to create more specific route objects. For example, I have the following routes announced: - 89.145.160.0/21 - 89.145.160.0/22 (FR7) - 89.145.164.0/23 (DK2) - 89.145.166.0/23 (GV2) Each more

Re: [swinog] TCP timestamps

❦ 10 mars 2016 17:12 +0100, Andre Keller  : > in the last few months we had several security audits and all of them > proposed to disable tcp timestamps. (i.e. on Linux > net.ipv4.tcp_timestamps=0). AFAIK roundtrip time calculation in tcp > relies on this and there might be

[swinog] Swisscom 6RD and MTU

Hi! At home, I have replaced Swisscom internet box by my own (Linux) router. For IPv6, I noticed that the MTU is 1472 instead of 1480 (1500 - 20). For IPv4, MTU is 1500. Does anyone know why the MTU on those 6RD links has to be 1472 and not 1480? Have other people with the same setup noticed

Re: [swinog] chrome ipv6-only vpn targets not accessible.

❦ 16 juillet 2014 15:40 +0200, Andre Keller a...@list.ak.cx : we have customers that run basically an IPv6-only infrastructure with some ipv4 reverse proxies in front of the services that need to be publicly available. Some of these internal services can be accessed using a VPN. The VPN