, Aug 5, 2018 at 4:39 PM, Satish Patel wrote:
> 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,
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.c
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
think i should get rid of all CHEKSUM option in iptables rules? Am i right?
On Sun, Aug 5, 2018 at 4:02 PM, Florian Westphal wrote:
> Satish Patel wrote:
>> > [84166:59495417] -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
>> > --checksum-fill
>> > [68739:515
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"
>
&
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
>
ACCEPT
COMMIT
# Completed on Sun Aug 5 15:52:56 2018
On Sun, Aug 5, 2018 at 3:42 PM, Florian Westphal wrote:
> Satish Patel wrote:
>> Thanks Florian,
>>
>> FYI, I don't have any CHECKSUM configure in my iptables,
>
> You have, according to WARN stacktrace you pro
wrote:
> 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
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
