nanog mailing list archives
Re: IPv6 Ingress traffic by default
From: Owen DeLong <owen () delong com>
Date: Mon, 20 Jun 2016 16:33:46 -0700
And that is the fault of the Raspberry PI. There is zero reason for the Raspberry PI to be open to the world before it has been configured. It could have a initial configuration that is just permit <local-prefixes>/64 any port 22 deny any any port 22
It’s very hard to configure a Raspberry PI using Cisco’s filter language. I don’t know of any case where this will work. Owen
Current thread:
- Re: Netflix banning HE tunnels, (continued)
- Re: Netflix banning HE tunnels Ricky Beam (Jun 09)
- Re: Netflix banning HE tunnels Owen DeLong (Jun 12)
- Re: Netflix banning HE tunnels Ricky Beam (Jun 14)
- Re: Netflix banning HE tunnels Valdis . Kletnieks (Jun 14)
- Re: Netflix banning HE tunnels Owen DeLong (Jun 14)
- Re: Netflix banning HE tunnels Mark Milhollan (Jun 17)
- Re: Netflix banning HE tunnels Owen DeLong (Jun 20)
- IPv6 Ingress traffic by default Jared Mauch (Jun 20)
- Re: IPv6 Ingress traffic by default Mark Milhollan (Jun 20)
- Re: IPv6 Ingress traffic by default Mark Andrews (Jun 20)
- Re: IPv6 Ingress traffic by default Owen DeLong (Jun 20)
- Re: IPv6 Ingress traffic by default Mark Andrews (Jun 20)
- Re: Netflix banning HE tunnels Mark Andrews (Jun 20)
- Re: Netflix banning HE tunnels Owen DeLong (Jun 20)
- Re: Netflix banning HE tunnels Mark Andrews (Jun 20)
- Re: Netflix banning HE tunnels Jason Baugher (Jun 20)
- Re: Netflix banning HE tunnels Owen DeLong (Jun 20)
- Re: Netflix banning HE tunnels Donn Lasher via NANOG (Jun 20)
- Re: Netflix banning HE tunnels Harald Koch (Jun 20)
- Re: Netflix banning HE tunnels Ricky Beam (Jun 09)
- Re: Netflix banning HE tunnels Karl Auer (Jun 09)