I just found that xt_NOTRACK is also missing, as reported in Bug#
125512, I just thought I'd mention that here since they're basically the
same issue, and maybe I can help expedite it's inclusion in Gutsy, same
as this bug.
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You
Yip, I found Ubuntu's support for questionably bleeding edge software
supprisingly good too. Just look at compiz and usplash when they first
came to light.
I'd just put this one down to a bug.
Good to see it fixed in the current Gutsy kernel now.
Cheers guys.
--
ipt_connmark is broken
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Tim Gardner (timg-tpi) = (unassigned)
Status: In Progress = Fix Released
Target: None = ubuntu-7.10-beta
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification because you are a
Still broken in the latest ubuntu kernel, release 2.6.22-11-generic.
As the Beta freeze is now on, and this bug is marked as wishlist, I
guess this is not going to be fixed in Gutsy?
Looks like I'll have to use Debian Etch for any server deployments that
require any clever firewalling or
Yeah, the attitude of Ubuntu maintainers plain sucks for this matter.
Having connmark enabled by default can't brake anything. I don't mind
recompiling the kernel by hand, but this would break automatic kernel security
updates and add more headache. Just don't get it.
--
ipt_connmark is broken
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Tim Gardner (timg-tpi)
Status: Confirmed = In Progress
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification because you are a member of
Speaking of advanced routers, I'm setting up Quagga on Debian, and
looking to do the same on 2 Ubuntu routers. When configuring BGP
sessions to 1 upstream provider's Blackhole route server, Linux
2.6.20.1 is required for TCP_MD5 passwords.
What's interesting, is the debate about the kernel
I've download last ubuntu kernel 2.6.20-29, modify the config and add this
modules:
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
recompile the kernel and now is working.
Should be added in the next kernel release.
--
ipt_connmark is broken
Yes, that's a straightforward workaround.
Recompiling the kernel every time in order to enable a feature that should have
been enabled by default sucks bad though.
Things remain the same in the latest Gutsy kernel.
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received
So how do we go about getting this fixed then?
I can confirm that the above change mentioned by saresca is all that I need to
do before compiling kernel modules to get the module I need. I do not know
where to start in making a patch for the kernel package though.
The module is about 4.0k after
I'd consider this a regression, since i'm using it for several years on
Debian, then switching my routers to Ubuntu last month, I felt a knife
in my backnot as welcoming as I had hoped.
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I sold a load-balancing scheme to a client. When I moved my scripts
over from my testing (SuSE with 2.6.16.13 kernel) to client production
(Feisty, canned), this chomped at my posterior. Is -j CONNMARK
considered unstable? There seems to be evidenced of topns of folks
using it for quite a while
re-targeting
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: linux-source-2.6.20 = linux-source-2.6.22
Importance: Undecided = Wishlist
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification because you are a member of Ubuntu
Bugs,
So, is it going to get fixed for Gutsy?
--
ipt_connmark is broken
https://bugs.launchpad.net/bugs/112611
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is it possible to get this enabled in Gutsy Gibbon and future revisions of the
kernel?
I am using xt_CONNMARK for a site that serves to two ADSL connections and
xt_CONNMARK is the simplest way to keep route correct for the two connections.
--
ipt_connmark is broken
Thanks for taking the time to report this bug and helping to make Ubuntu
better. I have unmarked it as a security issue since this bug does not
show evidence of allowing attackers to cross privilege boundaries nor
directly cause loss of data/privacy. Please feel free to report any
other bugs you
17 matches
Mail list logo
