On 27/05/2015 20:35, Brian Rak wrote:
You don't need full promisc mode, just the (poorly documented)
allmulticast option (ip link set dev $macvtap allmulticast on)
...And poorly supported on some real hardware (notably Wi-Fi adapters),
where the hash filter on each NIC's MAC is not guarantee
On Tue, 2015-05-26 at 23:59 -0700, Tony Hain wrote:
> (...) For fun, project this
> http://www.google.com/intl/en/ipv6/statistics.html
> (...)
Hi,
If someone from google is listening it would be really nice to
spend a few minutes t oavoid flash for displaying this graph, it doesn't
work on my G
On May 27, 2015, at 1:59 AM, Tony Hain wrote:
> David,
>
> While I agree with you that there is no excuse for the general IPv6
> brokenness across all vendors, they are just doing what participants on lists
> like this one tell them. Name&Shame may help a little, but until a large
> number o
On 5/27/2015 3:20 PM, Jared Mauch wrote:
On Tue, May 26, 2015 at 04:19:25PM -0700, David Sotnick wrote:
Hi NANOG,
The company I work for has no business case for being on the IPv6-Internet.
However, I am an inquisitive person and I am always looking to learn new
things, so about 3 years ago I
On Tue, May 26, 2015 at 04:19:25PM -0700, David Sotnick wrote:
> Hi NANOG,
>
> The company I work for has no business case for being on the IPv6-Internet.
> However, I am an inquisitive person and I am always looking to learn new
> things, so about 3 years ago I started down the IPv6 path. This wa
On Tue, 26 May 2015, David Sotnick wrote:
> Arista EOS code — and it only appears to affect Virtual Machines which are
> behind our RedHat Enterprise Virtualization cluster. None of the hundreds
> of VMware-connected hosts are affected. The symptom is basically the same
> as the Palo Alto bug. Nei
On 27/May/15 01:27, Ca By wrote:
> Had ipv4 ever hurt you ?
>
> Me too.
IPv4 still hurts me (in some ways, worse than IPv6), and it's 2015.
Figures...
You just need to open cases with your vendors and help them fix these
issues. Sadly, no way around this. Software is not perfect. The humans
tha
David,
While I agree with you that there is no excuse for the general IPv6 brokenness
across all vendors, they are just doing what participants on lists like this
one tell them. Name&Shame may help a little, but until a large number of people
get serious and stop prioritizing IPv4 in their purc
On Tuesday, May 26, 2015, David Sotnick wrote:
> Hi NANOG,
>
> The company I work for has no business case for being on the IPv6-Internet.
> However, I am an inquisitive person and I am always looking to learn new
> things, so about 3 years ago I started down the IPv6 path. This was early
> 2012.
9 matches
Mail list logo
