similar to: [Bug 711] New: iptables -m iprange causes unknown error

Displaying 20 results from an estimated 3000 matches similar to: "[Bug 711] New: iptables -m iprange causes unknown error"

2011 Aug 29
2
[Bug 742] New: ip6tables "-m iprange" ipv6 range detection
http://bugzilla.netfilter.org/show_bug.cgi?id=742 Summary: ip6tables "-m iprange" ipv6 range detection Product: netfilter/iptables Version: linux-2.6.x Platform: x86_64 OS/Version: SuSE Linux Status: NEW Severity: critical Priority: P5 Component: ip6_tables (kernel) AssignedTo:
2010 Mar 09
2
[Bug 639] New: iptables iprange
http://bugzilla.netfilter.org/show_bug.cgi?id=639 Summary: iptables iprange Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: paulo.santos at
2003 Sep 05
8
where is "equalize" kernel patch?
I found following paragraph in the man page of iproute2. equalize allow packet by packet randomization on multipath routes. Without this modifier, the route will be frozen to one selected nexthop, so that load splitting will only occur on per-flow base. equalize only works if the kernel is patched. ^^^^^^^^^^^^^^^^^ Now, where
2005 Jan 11
0
shorewall iprange tweak
I often find myself doing, whois some.damned.ip.address and then copying and pasting the address range for the miscreant in question, and doing, shorewall iprange x.x.x.x-y.y.y.y with the aim to drop the entire range. My one minor complaint is that I often have to edit out the spaces between the hyphen when copying and pasting the address range returned by whois. I tweaked the shorewall
2007 Mar 19
9
[BUG?] ip ru flush && RTNETLINK answers: Numerical result out of range
After an: # ip ru flush I loose all my ip rules but the priority 0 one. root@sarasvati:~# ip ru 0: from all lookup 255 root@sarasvati:~# Ok with that, but now i''m not able to insert any new rule. This leads to a total loose of conectivity. root@sarasvati:~# ip ru add from all table default RTNETLINK answers: Numerical result out of range root@sarasvati:~# ip ru add from all
2009 Jun 16
2
[ANNOUNCE]: Release of iptables-1.4.4
The netfilter coreteam presents: iptables version 1.4.4 the iptables release for the 2.6.30 kernel. Changes include: - support for the new features in the 2.6.30 kernel, namely the cluster match and persistent multi-range NAT mappings - support for the ipset set match and target - various minor fixes and cleanups - documentation updates Version 1.4.4 can be obtained from:
2006 Mar 15
5
Possible bug with multiport?
Hi Folks: I am either using the multiport of the -m or --match option of iptables in correctly or there is a bug with it. Is anyone else using it with no problem? This is the way I am trying to use it: my_ports=21,25,80 iptables -t nat -A PREROUTING -i $wan_addr -p tcp -m multiport --dports $my_ports -j DNAT --to $my_internal_address I have used this in the past successfully but that was a
2005 Oct 11
0
iptables iprange match
Hello list!: Well, I was able to install xen 2.0.7 using a 2.4.30 kernel in a domU. The domU have installed gcc3.4 .. after yum -y install compat-gcc* and put CC=gcc33 in all make commands and other changes as here: http://lists.xensource.com/archives/html/xen-users/2005-08/msg00258.html I''m trying to use the iprange match, but every time when I want apply a rule I receives:
2014 May 07
1
[Bug 922] New: iprange: --ports is not suppported
https://bugzilla.netfilter.org/show_bug.cgi?id=922 Summary: iprange: --ports is not suppported Product: nftables Version: unspecified Platform: x86_64 OS/Version: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: nft AssignedTo: pablo at netfilter.org ReportedBy: anarey
2007 Apr 18
1
[Bridge] bridge at start up
hi i have gone through the achieves but still could not get my bridge to suvive a reboot . please can anyone help me am using fedora core 2 -----Original message----- From: bridge-request@lists.osdl.org Date: Fri, 28 Jan 2005 03:08:06 +0100 To: bridge@lists.osdl.org Subject: Bridge Digest, Vol 17, Issue 25 > Send Bridge mailing list submissions to > bridge@lists.osdl.org > >
2004 Aug 12
5
shorewall iprange problem
Perhaps someone can help me understand why this is happening. I''m trying to write a script using ''shorewall iprange'' to parse some ip ranges into subnets so that i can place them into the blocklist. I keep getting an error when i run the script though. Here is the script: #!/bin/csh foreach i (`cat ipranges`) shorewall iprange $i >>
2011 Apr 03
6
[Bug 713] New: CPPFLAGS are mishandled which breaks non-shared targets
http://bugzilla.netfilter.org/show_bug.cgi?id=713 Summary: CPPFLAGS are mishandled which breaks non-shared targets Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: unknown AssignedTo: netfilter-buglog at
2002 Jun 20
3
simple error in extensions/libipt_ROUTE.c extensions/libipt_IMQ.c
Hi Patrick ! I find simple error in extensions/libipt_ROUTE.c line 24 and 127 -- change NETFILTER_VERSION to IPTABLES_VERSION extensions/libipt_IMQ.c line 18 and 87 -- change NETFILTER_VERSION to IPTABLES_VERSION (iptables-20020618) ----------------------------------- mailto:alexey_talikov@texlab.com.uz BR Alexey Talikov FORTEK -----------------------------------
2003 Apr 25
4
IMQ page
The IMQ page (http://luxik.cdi.cz/~patrick/imq/) has some rather obvios problems in the examples used. I wrote Patrick McHardy without getting an answer (yet) so I tought this was a good place to ask. Does anybody know how to contact him about this? _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
2007 Aug 13
4
Problem with iprange in shorewall 4.0.2
Hi, I have the following problem while activating this rule entry using shorewall-shell: ACCEPT:notice:rul WAN:139.x.x.226 INT:139.x.x.153-139.x.x.156 udp 1024:65535 1024:65535 "-m iprange" in front of "--dst-range" is missing in the activation command. The logging entry (above) is set correct. Below is the debug output. Thanks Regards Günter + case $level in +
2004 Feb 26
12
HFSC
hmm HFSC ? where can i find more informations and examples about the *linux* HFSC ? http://trash.net/~kaber/hfsc/ does not help here -- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
2004 Oct 31
9
Maquerading through IPSECed wireless dropping packets selectively?
Hello, I''m stuck IPSECing my wireless network at home and would appreciate any comments. I appologize in advance if I''m wasting your time with trivia - I''m not a professional and staring at the problem for days from various angles hasn''t done me any good ... My home server/firewall (morannon) is hooked up through an USB to ethernet adapter (eth1) to my DSL
2006 Sep 10
3
HFSC traffic loss bug, kernel 2.6.16.24
Hello, I have finally managed to understand HFSC up to a level which allowed me to create a QoS script which maintains low VoIP latency while running stuff like eMule. Unfortunately, HFSC seems to have a severe bug. Why do I consider this as a bug defenitely? Well, my script runs without any errors, then QoS works perfectly for some hours, no error messages in kernel log. Then randomly the
2013 Jul 20
6
[Bug 835] New: protocol without option is failing
https://bugzilla.netfilter.org/show_bug.cgi?id=835 Summary: protocol without option is failing Product: nftables Version: unspecified Platform: x86_64 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: nft AssignedTo: pablo at netfilter.org ReportedBy: eric at
2008 Jul 07
3
[Bridge] [RFC PATCH 0/2] Allow full bridge configuration via sysfs
Right now, you can configure most bridge device parameters via sysfs. However, you cannot either: - add or remove bridge interfaces - add or remove physical interfaces from a bridge The attached patch set rectifies this. With this patch set, brctl (theoretically) becomes completely optional, much like ifenslave is now for bonding. (In fact, the idea for this patch, and the syntax used herein, is