It appears likely that within the next two quarters we will be moving
off of our IPv4 class C's and onto a single IPv6 /40 for our sites.
We have a fairly complex IPTables setup which handles our gateways and
internal hosts. My question is just how much effort is involved in
moving these rules fr
>
> An update to close: it's a vmware issue:
thanks for the closure... VMware diagnosis can be a real pain...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
An update to close: it's a vmware issue:
* new centos 5 creations exhibit the same behavior
* a few months ago, we migrated from an esx 4.0 cluster to a new esx 4.1
cluster
* we've just recently started using a new centos 6 template; the centos
6 system that's working was created before the migrat
On Mon, Aug 13, 2012 at 12:46:44PM -0700, Alan Batie wrote:
> it's interacting badly with centos 6 is a good question. It could be a
> bug in vmware tools/the ethernet driver. At least it's narrowed down now...
Are you using vmxnet3 drivers? That had a known bug with small udp
packets, but it s
On 8/13/12 12:35 PM, James Hogarth wrote:
> Hmm this is especially weird given the 5.8 systems are working -
> otherwise I'd have moved the troubleshooting up to vmware or the
> switch next...
Migrating one of the vms to the same physical host made them start
talking to each other, so it's defini
On 13 August 2012 20:37, Alan Batie wrote:
> I found another CentOS 6 system that not only is talking ipv6 properly,
> but the test system that can't even talk to the router can talk to it.
> That indicates it's probably something wonky with the network itself...
>
Hmm...
I don't have a C6 ipv6
I found another CentOS 6 system that not only is talking ipv6 properly,
but the test system that can't even talk to the router can talk to it.
That indicates it's probably something wonky with the network itself...
___
CentOS mailing list
CentOS@centos.o
>
> Yes, the test system has the default ip6tables, but we always permit icmp:
>
Hmm this is especially weird given the 5.8 systems are working -
otherwise I'd have moved the troubleshooting up to vmware or the
switch next...
Without access to the machines/switches to traffic dump and check in
wi
On 8/13/12 12:00 PM, James Hogarth wrote:
> Are you allowing ICMPv6? I don't just mean echo and echo-reply (the
> pings above) but most of the rest of it too?
Yes, the test system has the default ip6tables, but we always permit icmp:
# Firewall configuration written by system-config-firewall
# M
>
> Love gratuitous changes to long standard toolsets... sigh...
>
It's not a recent change and is far from gratuitous
http://lists.debian.org/debian-devel/2009/03/msg00780.html
Features such as traffic shaping, policy routing and multiple IPs on
an interface (not virtual interfaces) either
On 8/11/12 2:17 AM, James Hogarth wrote:
> With ipv6 in the picture stop using net-tools - they were deprecated a long
> time ago and there's multiple edge cases and bugs where they don't work
> properly or lack features... learn to use the iproute2 toolset - ip, ss and
> tc being the key ones.
L
On 8/11/12, Alan Batie wrote:
> We've been running ipv6 for a year or so now, but some of our newer
> instances (all on an ESX cluster) are not working. It looks like it's
> all of our Centos 6 instances. I'm hoping someone can point me in the
> right direction...
> [27] # cat ifcfg-eth0
> DEV
On Aug 11, 2012 2:00 AM, "Alan Batie" wrote:
>
> On 8/10/12 5:50 PM, Stephen Harris wrote:
> > On Fri, Aug 10, 2012 at 05:24:12PM -0700, Alan Batie wrote:
> >> IPV6_DEFROUTE=yes
> >
> > Not sure where you get that from.
>
> That's not something normally in our configs, I think it was in the
> defa
On 8/10/12 5:50 PM, Stephen Harris wrote:
> On Fri, Aug 10, 2012 at 05:24:12PM -0700, Alan Batie wrote:
>> IPV6_DEFROUTE=yes
>
> Not sure where you get that from.
That's not something normally in our configs, I think it was in the
default config the centos 6 installer created, and I only stripped
On Fri, Aug 10, 2012 at 05:24:12PM -0700, Alan Batie wrote:
> IPV6_DEFROUTE=yes
Not sure where you get that from. Instead try adding
IPV6_DEFAULTDEV=eth0
to /etc/sysconfig/network
FWIW you can see the current routing table with "ip -6 route".
--
rgds
Stephen
We've been running ipv6 for a year or so now, but some of our newer
instances (all on an ESX cluster) are not working. It looks like it's
all of our Centos 6 instances. I'm hoping someone can point me in the
right direction...
tshark indicates that it's neighbor discovery that's failing:
[26]
16 matches
Mail list logo