Re: IPv6 Ingress traffic by default

2016-06-20 Thread Mark Andrews
In message , Owen DeLong writes: > > > > 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 /64 any port 22 > > deny any any

Re: IPv6 Ingress traffic by default

2016-06-20 Thread Owen DeLong
> > 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 /64 any port 22 > deny any any port 22 It’s very hard to configure a Rasp

Re: IPv6 Ingress traffic by default

2016-06-20 Thread Mark Andrews
In message , Jared Mauch writes: > > > On Jun 20, 2016, at 1:30 PM, Owen DeLong wrote: > > > > > >> On Jun 17, 2016, at 10:10 , Mark Milhollan wrote: > >> > >> On Tue, 14 Jun 2016, Owen DeLong wrote: > >>> On Jun 14, 2016, at 11:57 , Ricky Beam wrote: > >> > I've seen many "IPv6 Capable"

Re: IPv6 Ingress traffic by default

2016-06-20 Thread Mark Milhollan
On Mon, 20 Jun 2016, Jared Mauch wrote: >On Jun 20, 2016, at 1:30 PM, Owen DeLong wrote: >>On Jun 17, 2016, at 10:10 , Mark Milhollan wrote: >>>This (open by default vs closed) has been discussed before, with plenty >>>of people on either side. >>I'm unaware of anyone advocating open inbound b