No IPV6 address no worries. The hackers can't make a connection cause
there's nothing to connect to.
There's no need for IPV6 at home unless you want to learn more about IPV6.
On Dec 23, 2010, at 3:12 PM, barsalou <barjunk@attglobal.net> wrote:
> Quoting Arthur Corliss <acorliss@nevaeh-linux.org>:
>
>> On Wed, 22 Dec 2010, Scott Carnahan wrote:
>>
> <snip>
>> FYI: IPv6 is layer-2 compatible with IPv4, so you don't need new switches=
> .
>> Older managed switches will still need an IPv4 for management purposes, bu=
> t
>> they'll carry IPv6 traffic with no problem.
>>
>> On the router side you can always use Linux as a software router. For tha=
> t
>> matter, I'd be very surprised if one of those OpenWRT images wouldn't
>> support IPv6 as well.
>>
>> This is essentially what I'm doing at home, running a dual-stack network
>> with managed infrastructure on IPv4. My old wireless AP, ethernet switche=
> s,
>> etc., carry the IPv6 traffic seemlessly, with a central Linux box doing th=
> e
>> routing for both stacks in the middle.
>>
>> FYI: for those of you jumping into this, please remember that iptables is
>> IPv4-only. If you haven't configured ip6tables you have essentially no
>> firewalling at all on IPv6.
>
> To me, this implies that "home" routers that didn't originally account =20
> for IPV6 would be vulnerable.
>
> Would those old style routers be vulnerable? Maybe if they were only =20
> using a linux kernel?
>
> Is it also a bad assumption that if you aren't routing ipv6 traffic in =20
> your network and machines do not have ipv6 interfaces, then there is =20
> no cause for concern?
>
> Mike B.
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Thu Dec 23 18:04:54 2010
This archive was generated by hypermail 2.1.8 : Thu Dec 23 2010 - 18:04:54 AKST