Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-19 Thread Ty Featherling
you trace that to the customer/port? > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Ty Featherling > *Sent:* Friday, February 19, 2016 7:05 PM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] IPv6 traffic to ff02::1:2 > > > > Forgot to update: had the

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-19 Thread Sterling Jacobson
How did you trace that to the customer/port? From: Af [mailto:af-boun...@afmug.com] On Behalf Of Ty Featherling Sent: Friday, February 19, 2016 7:05 PM To: af@afmug.com Subject: Re: [AFMUG] IPv6 traffic to ff02::1:2 Forgot to update: had the customer reboot his router and the traffic

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-19 Thread Ty Featherling
lto:af-boun...@afmug.com <af-boun...@afmug.com>] *On > Behalf Of *Ty Featherling > *Sent:* Thursday, February 18, 2016 10:08 AM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] IPv6 traffic to ff02::1:2 > > > > Found the offending customer and looking at their radio I can see t

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread David
Featherling *Sent:* Thursday, February 18, 2016 10:08 AM *To:* af@afmug.com *Subject:* Re: [AFMUG] IPv6 traffic to ff02::1:2 Found the offending customer and looking at their radio I can see the actual traffic is about 5Mbps worth but the traffic shaping knocks it down to 1.5 before it reaches our

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread Paul Stewart
ROFL .. that’s awesome… From: Af [mailto:af-boun...@afmug.com] On Behalf Of Chris Wright Sent: Thursday, February 18, 2016 1:22 PM To: af@afmug.com Subject: Re: [AFMUG] IPv6 traffic to ff02::1:2 It just really, REALLY wants everyone to know it exists. Cute little thing. Set it on fire

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread Paul Stewart
“IPv6 compatible” etc for marketing … we tested if they can actually function properly without breaking… From: Af [mailto:af-boun...@afmug.com] On Behalf Of Ty Featherling Sent: Thursday, February 18, 2016 1:08 PM To: af@afmug.com Subject: Re: [AFMUG] IPv6 traffic to ff02::1:2 Found

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread Ty Featherling
> Velociter Wireless > > 209-838-1221 x115 > > > > *From:* Af [mailto:af-boun...@afmug.com] *On Behalf Of *Ty Featherling > *Sent:* Thursday, February 18, 2016 10:08 AM > *To:* af@afmug.com > *Subject:* Re: [AFMUG] IPv6 traffic to ff02::1:2 > > > > Fo

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread Chris Wright
Subject: Re: [AFMUG] IPv6 traffic to ff02::1:2 Found the offending customer and looking at their radio I can see the actual traffic is about 5Mbps worth but the traffic shaping knocks it down to 1.5 before it reaches our network. Makes me think this is more like a malfunctioning router than

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-18 Thread Ty Featherling
Found the offending customer and looking at their radio I can see the actual traffic is about 5Mbps worth but the traffic shaping knocks it down to 1.5 before it reaches our network. Makes me think this is more like a malfunctioning router than a feature. -Ty -Ty On Wed, Feb 17, 2016 at 2:43

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-17 Thread Ty Featherling
1 layer 2 network per tower. All APs and CPE bridged to that one broadcast domain. -Ty -Ty On Wed, Feb 17, 2016 at 2:32 PM, Cassidy B. Larson wrote: > How big is your layer2 network? Ideally, with multicast, your switch > should only be sending it to the hosts that

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-17 Thread Cassidy B. Larson
How big is your layer2 network? Ideally, with multicast, your switch should only be sending it to the hosts that subscribe to that multicast IP. > On Feb 17, 2016, at 10:54 AM, Ty Featherling wrote: > > So it's DHCPv6 discovery? Why the hell so much traffic then? If

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-17 Thread Ty Featherling
So it's DHCPv6 discovery? Why the hell so much traffic then? If I can find the source radio I will definitely turn off multicast. Good idea. -Ty -Ty On Wed, Feb 17, 2016 at 11:51 AM, Cassidy B. Larson wrote: > Look for the mac: a813.430a.5950 I think. That’s the source

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-17 Thread Cassidy B. Larson
Look for the mac: a813.430a.5950 I think. That’s the source MAC, assuming I flipped the right bit. I know the last 8 are right at least. You could just turn off multicast on his radio or the AP, but his router is looking for a DHCP server and sending to that multicast address in question. If

Re: [AFMUG] IPv6 traffic to ff02::1:2

2016-02-17 Thread Sterling Jacobson
Yes, I see it too. Was wondering exactly what is going on and how to ‘trim’ the chatter down. It’s about a meg of traffic on my system too. Dennis? Any ideas? From: Af [mailto:af-boun...@afmug.com] On Behalf Of Ty Featherling Sent: Wednesday, February 17, 2016 10:47 AM To: af@afmug.com