Prev: Spotty internet connection
Next: DHCPNACK Message-IP Address Denied
From: RB on 29 Mar 2010 10:50
Sometimes while my wife is on facebook and she chats with others there,
I notice my BitDefender Lan log on notifications come up with ips that
are not the normal 192.168.1.x local ip's of our NAT but rather
these 64bit things like FE08:ED88:FC33:2314 which I surmise are
ip address's coming from TCP v6 ? Appreciate any input on what
these are.
(By the way we are running AES encryption security on our wireless NAT
router, with a very long key)



From: Jack [MVP-Networking] on 29 Mar 2010 14:48
Hi
If your Network computers a ere configured with IPv6 there might be some
idle probing traffic going between the computers.
You probably should ignore it, IPv6 can not go on to the current Internet.
If AES encryption is On the wireless is secured.
Jack (MS, MVP-Networking)..


"RB" <NoMail(a)NoSpam> wrote in message
news:O9YPw80zKHA.4384(a)TK2MSFTNGP06.phx.gbl...
> Sometimes while my wife is on facebook and she chats with others there,
> I notice my BitDefender Lan log on notifications come up with ips that
> are not the normal 192.168.1.x local ip's of our NAT but rather
> these 64bit things like FE08:ED88:FC33:2314 which I surmise are
> ip address's coming from TCP v6 ? Appreciate any input on what
> these are.
> (By the way we are running AES encryption security on our wireless NAT
> router, with a very long key)
>
>
>

From: RB on 30 Mar 2010 09:13
Well that is interesting to know that v6 is not needed yet. I don't recall
installing it, I am almost certain it installed by default when I first set up
my LAN workgroup.
I still get the normal 192.168.1.x of my local lan nodes also but from
time to time I notice these other 64 bit hex numbers pop up.


"Jack [MVP-Networking]" <jack(a)discussiongroup.com> wrote in message news:uxIuxB3zKHA.928(a)TK2MSFTNGP05.phx.gbl...
> Hi
> If your Network computers a ere configured with IPv6 there might be some idle probing traffic going between the computers.
> You probably should ignore it, IPv6 can not go on to the current Internet.
> If AES encryption is On the wireless is secured.
> Jack (MS, MVP-Networking)..
>
>
> "RB" <NoMail(a)NoSpam> wrote in message news:O9YPw80zKHA.4384(a)TK2MSFTNGP06.phx.gbl...
>> Sometimes while my wife is on facebook and she chats with others there,
>> I notice my BitDefender Lan log on notifications come up with ips that
>> are not the normal 192.168.1.x local ip's of our NAT but rather
>> these 64bit things like FE08:ED88:FC33:2314 which I surmise are
>> ip address's coming from TCP v6 ? Appreciate any input on what
>> these are.
>> (By the way we are running AES encryption security on our wireless NAT
>> router, with a very long key)
>>
>>
>>
>


From: Jack [MVP-Networking] on 30 Mar 2010 10:36
Hi
Yeah it is installed by default on newer OS' and it can stay there and be
ignored if not used for Local Traffic.
Or you can uncheck it in the Connection Properties.
Jack (MS, MVP-Networking)..

"RB" <NoMail(a)NoSpam> wrote in message
news:OyDzFrA0KHA.2072(a)TK2MSFTNGP02.phx.gbl...
> Well that is interesting to know that v6 is not needed yet. I don't recall
> installing it, I am almost certain it installed by default when I first
> set up
> my LAN workgroup.
> I still get the normal 192.168.1.x of my local lan nodes also but from
> time to time I notice these other 64 bit hex numbers pop up.
>
>
> "Jack [MVP-Networking]" <jack(a)discussiongroup.com> wrote in message
> news:uxIuxB3zKHA.928(a)TK2MSFTNGP05.phx.gbl...
>> Hi
>> If your Network computers a ere configured with IPv6 there might be some
>> idle probing traffic going between the computers.
>> You probably should ignore it, IPv6 can not go on to the current
>> Internet.
>> If AES encryption is On the wireless is secured.
>> Jack (MS, MVP-Networking)..
>>
>>
>> "RB" <NoMail(a)NoSpam> wrote in message
>> news:O9YPw80zKHA.4384(a)TK2MSFTNGP06.phx.gbl...
>>> Sometimes while my wife is on facebook and she chats with others there,
>>> I notice my BitDefender Lan log on notifications come up with ips that
>>> are not the normal 192.168.1.x local ip's of our NAT but rather
>>> these 64bit things like FE08:ED88:FC33:2314 which I surmise are
>>> ip address's coming from TCP v6 ? Appreciate any input on what
>>> these are.
>>> (By the way we are running AES encryption security on our wireless NAT
>>> router, with a very long key)
>>>
>>>
>>>
>>
>
>

From: JimC on 6 Apr 2010 19:41
Probably local v6 traffic as suggested by Jack. Easiest way to check is to
open a command prompt and type ipconfig /all on each PC. Look at the result
to see if your ethernet adapter has the address you have shown.
Cheers,
Jim

"RB" <NoMail(a)NoSpam> wrote in message
news:O9YPw80zKHA.4384(a)TK2MSFTNGP06.phx.gbl...
> Sometimes while my wife is on facebook and she chats with others there,
> I notice my BitDefender Lan log on notifications come up with ips that
> are not the normal 192.168.1.x local ip's of our NAT but rather
> these 64bit things like FE08:ED88:FC33:2314 which I surmise are
> ip address's coming from TCP v6 ? Appreciate any input on what
> these are.
> (By the way we are running AES encryption security on our wireless NAT
> router, with a very long key)
>
>
>

 | 
Pages: 1
Prev: Spotty internet connection
Next: DHCPNACK Message-IP Address Denied