Michal Kubecek wrote:
> On Mon, Aug 06, 2018 at 01:15:37AM +0200, Florian Westphal wrote:
> > Michal Kubecek wrote:
> > > Oops, exactly this issue was already discussed almost a year ago:
> > >
> > > http://lkml.kernel.org/r/20170824104824.2c318a0...@unicorn.suse.cz
> > >
> > > But something
On Mon, Aug 06, 2018 at 01:15:37AM +0200, Florian Westphal wrote:
> Michal Kubecek wrote:
> > Oops, exactly this issue was already discussed almost a year ago:
> >
> > http://lkml.kernel.org/r/20170824104824.2c318a0...@unicorn.suse.cz
> >
> > But something more urgent came and I forgot to get
Michal Kubecek wrote:
> Oops, exactly this issue was already discussed almost a year ago:
>
> http://lkml.kernel.org/r/20170824104824.2c318a0...@unicorn.suse.cz
>
> But something more urgent came and I forgot to get back to it. :-(
I did not even remeber, thanks for the pointer.
So I think be
On Sun, Aug 05, 2018 at 11:03:42PM +0200, Florian Westphal wrote:
> Satish Patel wrote:
> > Florian,
> >
> > It seems those rules coming from here
> > https://github.com/openstack/openstack-ansible-os_neutron/blob/master/files/post-up-metadata-checksum
>
> This is crazy, and, as you found, it do
Satish Patel wrote:
> Florian,
>
> It seems those rules coming from here
> https://github.com/openstack/openstack-ansible-os_neutron/blob/master/files/post-up-metadata-checksum
This is crazy, and, as you found, it doesn't even do what they seem to
think it does.
I see no reason for these rules
Satish Patel wrote:
> After reading further related DHCP checksum issue, it seems we need
> that rules when you running DHCP on same host machine where your guest
> using host DHCP service, in that case virtual nic won't do checksum.
> If your DHCP running on different host then your physical nic
After reading further related DHCP checksum issue, it seems we need
that rules when you running DHCP on same host machine where your guest
using host DHCP service, in that case virtual nic won't do checksum.
If your DHCP running on different host then your physical nic perform
checksum.
On Sun, Au
Florian,
I have removed those port 80 CHECKSUM rules and everything looks good
i didn't see kernel WARN mesg.
Thank you so much! You just nailed it :)
On Sun, Aug 5, 2018 at 4:15 PM, Satish Patel wrote:
> Florian,
>
> It seems those rules coming from here
> https://github.com/openstack/openstac
Florian,
It seems those rules coming from here
https://github.com/openstack/openstack-ansible-os_neutron/blob/master/files/post-up-metadata-checksum
On Sun, Aug 5, 2018 at 4:09 PM, Satish Patel wrote:
> Yes this is openstack-ansible deployment tool which set them up. I am
> wondering where are t
Yes this is openstack-ansible deployment tool which set them up. I am
wondering where are these rules saved? I believe openstack-ansible use
LXC container to deploy services so must be part of LXC startup
scripts.
I have checked there is no firewalld and iptables service running on system..
You t
Satish Patel wrote:
> > [84166:59495417] -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
> > --checksum-fill
> > [68739:5153476] -A POSTROUTING -p tcp -m tcp --sport 8000 -j CHECKSUM
> > --checksum-fill
These rules make no sense to me, and are also source of your backtrace.
Who set this up?
I am configured where are those rules stored why iptables -L -n -t nat
not showing them?
On Sun, Aug 5, 2018 at 3:56 PM, Satish Patel wrote:
> Oh wait!! I think you are right there i didn't notice that iptables
> has following setting.
>
> "CHECKSUM --checksum-fill"
>
> On Sun, Aug 5, 2018 at 3:5
Oh wait!! I think you are right there i didn't notice that iptables
has following setting.
"CHECKSUM --checksum-fill"
On Sun, Aug 5, 2018 at 3:54 PM, Satish Patel wrote:
> I have following kernel logging set.
>
> [root@ostack-infra-02 tools]# cat /proc/sys/kernel/printk
> 3 4 1 3
>
>
> iptables
I have following kernel logging set.
[root@ostack-infra-02 tools]# cat /proc/sys/kernel/printk
3 4 1 3
iptables output
[root@ostack-infra-02 tools]# iptables-save -c
# Generated by iptables-save v1.4.21 on Sun Aug 5 15:52:56 2018
*raw
:PREROUTING ACCEPT [42284573:38782693391]
:OUTPUT ACCEPT [2
Satish Patel wrote:
> Thanks Florian,
>
> FYI, I don't have any CHECKSUM configure in my iptables,
You have, according to WARN stacktrace you provided.
iptables-save -c
ip6tables-save -c
Thanks Florian,
FYI, I don't have any CHECKSUM configure in my iptables, i have
following rules, also do you think this kernel WARNNING is just
warning and not impacting my performance, based on that i have to
decided criticality of this issue.
[root@ostack-infra-02 ~]# iptables -L -n
Chain INPUT
Satish Patel wrote:
> I am installing openstack and as you know i have lots of bridges and
> vlan interface on my Linux CentOS 7.5
>
> I was getting following error stack on 3.10 kernel and found this is
> kernel bug which required kernel upgrade so now i have upgraded my
> kernel to 4.17.12 but
Folks,
I am installing openstack and as you know i have lots of bridges and
vlan interface on my Linux CentOS 7.5
I was getting following error stack on 3.10 kernel and found this is
kernel bug which required kernel upgrade so now i have upgraded my
kernel to 4.17.12 but i am still seeing same ke
18 matches
Mail list logo
