This was reported as an upstream kernel bug:
http://archive.linuxvirtualserver.org/html/lvs-devel/2017-04/msg00014.html
An IPVS kernel developer has responded to the issue and a patch has been
tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
Title:
IPVS incorrectly reverse-NATs traffic to LVS host
To manage notifications about this bug go
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
I've attempted to patch this out by adding checks where snat_handler and
dnat_handler are called (ip_vs_core.c and ip_vs_xmit.c), with no success. I
have to surmise that either:
- My patches aren't being built correctly
- My checks don't work
- This isn't the code that's mangling the packets
-
I think I may have tracked this down, but I haven't had a go at patching
it yet.
In net/netfilter/ipvs/ip_vs_core.c - in handle_response():
/* mangle the packet */
if (pp->snat_handler && !pp->snat_handler(skb, pp, cp, iph))
goto drop;
This calls the
I've tested this with the latest upstream kernel (4.11.0-041100rc6), and
the problem is still present.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
It's hard to tell whether this was the result of an upgrade - I think
this behaviour has always been present in the 14.04 stock kernels, but
we noticed it less until recently.
I'll look into testing the latest upstream kernel and get back to you.
If I get a chance I'll also try to look through
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11
apport information
** Tags added: apport-collected trusty
** Description changed:
We have observed the following behaviour on our LVS systems, which is
causing issues with our monitor scripts. The systems are running Ubuntu
14.04.5 LTS and I've tested both with the stock 3.13.0 kernel
** Description changed:
We have observed the following behaviour on our LVS systems, which is
causing issues with our monitor scripts. The systems are running Ubuntu
14.04.5 LTS and I've tested both with the stock 3.13.0 kernel (-100 and
-116) and the 4.4.0-72 xenial kernel.
Our
10 matches
Mail list logo
