These days I think the idea is to use unnumbered or dynamic neighbors so
most of the configuration complexity goes away:
https://docs.cumulusnetworks.com/display/DOCS/Border+Gateway+Protocol+-+BGP#BorderGatewayProtocol-BGP-ConfiguringBGPUnnumberedInterfaces
In this case, your container would peer
On Thu, Mar 29, 2018 at 9:07 AM, Chip Marshall wrote:
> I think the real question is "when are we going to get some memorable
> IPv6 public recursive DNS servers?"
>
> 2001:4860:4860:: or 2620:fe::fe just aren't quite as catchy as
> 8.8.8.8 or 9.9.9.9.
>From https://1.1.1.1/:
For IPv6: *20
How does one get ARIN to register resources to come up with this result?
https://whois.arin.net/rest/nets;q=103.11.67.105
The /16 is APNIC but there are 2 subnets that appear to be allocated from
ARIN. Having just typed 'whois 103.11.67.105' I completely missed the fact
that the supernet was APNI
On Tue, Jun 9, 2015 at 4:27 PM, Joel Maslak wrote:
> Agreed - apparently the solution is to implement SLAAC + DNS advertisements
> *AND* DHCPv6. Because you need SLAAC + DNS advertisements for Android, and
> you need DHCPv6 for Windows.
>
> Am I the only one that thinks this situation is stupid?
On Wed, Nov 6, 2013 at 4:45 PM, William Herrin wrote:
> Incidentally, I'd suggest that an ounce of prevention is worth a pound
> of cure. Simply block outbound tcp port 25 for new hosting customers
> on a "tell me if you want it open" basis.
>
>
Or to thwart those clever spammers, block inbound S
5 matches
Mail list logo
