similar to: [Bug 1450] New: Using certain simple set combinations with TCP flags causes error in mergesort.c from nft list ruleset

Hi all, I recently ran into some problems with rsync. My plan is to renew some of our old administration concepts from early 90's, I already replaced rdist with rsync a few years ago. Because of the rdist legacy, the current method requires synchronizing files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep}, which in turn are prioritized by a tool that just symlinks

Ned, Thank you very much for the response. Great example following through on the premise. It sounds like I need to have a better understanding of the traffic patterns on my network to know the optimal order for iptables filtering rules. My brief example - Premise: I want to limit outsiders from interfering with LAN client machines. So, I have the following rules regarding forwarding traffic:

On 30/06/16 23:19, Mike wrote: > Ned, > > Thank you very much for the response. > Great example following through on the premise. > It sounds like I need to have a better understanding of the traffic > patterns on my network to know the optimal order for iptables > filtering rules. > Try running: iptables -nv -L which will show you in the left hand column a counter for

Hi, system info: ubuntu 7.04 (Host OS) samba 3.0.24 (installed with apt-get) vmware-server 6.0.1 windows XP (Guest OS) I was using the iptables script provided by iptablesrocks.org. It's been quite useful, but I ran into a problem when I tried to connect samba. Without any iptables rules, I have no problem when connecting host os(ubuntu samba server) from guest os Windows XP. I referenced

https://bugzilla.netfilter.org/show_bug.cgi?id=1086 Bug ID: 1086 Summary: Nftables matching packet header fields and unexpected '(': wrong wiki info or bug? Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: minor

On 19/04/2016 3:39 PM, Gaston wrote: > Hello everyone, > > I am learning R since recently, and as a small exercise I wanted to > write a recursive mergesort. I was extremely surprised to discover that > my sorting, although operational, is deeply inefficient in time. Here is > my code : > >> merge <- function(x,y){ >> if (is.na(x[1])) return(y) >>

I indeed used is.na() to check length, as I was not sure weather lenght() was a simple query or would go through the whole vector to count the elements. So to sum up, function calls are expensive, therefore recursion should be avoided, and growing the size of a vector (which is probably reassigning and copying?) is also expensive. Thank you for your help! On 04/19/2016 11:51 PM, Duncan

Hello, some time ago I reported a bug, where we saw indeterministic behaviour of rsync (all versions since 2.5), when having the same file appearing in multiple sources. Sometimes the file in the first source was copied, other times the file was copied from one of the other sources. The attached mstest.tgz contains a test to reproduce the behaviour under darwin and solaris. The bug did

Hello everyone, I am learning R since recently, and as a small exercise I wanted to write a recursive mergesort. I was extremely surprised to discover that my sorting, although operational, is deeply inefficient in time. Here is my code : > merge <- function(x,y){ > if (is.na(x[1])) return(y) > else if (is.na(y[1])) return(x) > else if (x[1]<y[1])

https://bugzilla.netfilter.org/show_bug.cgi?id=1195 Bug ID: 1195 Summary: 'list ruleset' of 'nft -f' outputs garbage while 'nft list ruleset' seems to work. Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement

https://bugzilla.netfilter.org/show_bug.cgi?id=1118 Bug ID: 1118 Summary: nft: nft -f and nft list ruleset use different sets of service -> port mappings Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5

https://bugzilla.netfilter.org/show_bug.cgi?id=1349 Bug ID: 1349 Summary: "nft list ruleset" shows rules twice Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: minor Priority: P5 Component: nft Assignee: pablo at

https://bugzilla.netfilter.org/show_bug.cgi?id=1706 Bug ID: 1706 Summary: Nft is slow when loading ruleset with lots of add element calls of different interval maps Product: nftables Version: 1.0.x Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority:

https://bugzilla.netfilter.org/show_bug.cgi?id=1424 Bug ID: 1424 Summary: v0.9.0: segfault when using nft -f <file> and issuing "ruleset flush" twice Product: nftables Version: unspecified Hardware: All OS: Debian GNU/Linux Status: NEW Severity: normal

I am currently using samba 2.3a-12.3 as a PDC, here is my smb.conf [global] netbios name = kidpaddle workgroup = JUDO domain master = yes local master = yes preferred master = yes os level = 255 wins support = yes time server = yes security = user encrypt passwords = yes domain logons = yes domain admin group = root davidj logon drive = H: logon

Dear all, I have a bit of a complicated tinc setup yielding weird results that I cannot explain. I would be glad if maybe someone here could help me out. I have 3 machines (with IP addresses in my tinc network) machine A (10.0.0.2) runs gentoo, tinc-1.1_pre17, behind router Y machine B (10.0.0.3) runs gentoo, tinc-1.1pre15, behind router X machine C (10.0.0.1) runs raspbian, tinc-1.1pre15, behind

https://bugzilla.netfilter.org/show_bug.cgi?id=1222 Bug ID: 1222 Summary: nft list ruleset – infinite memory use Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org

https://bugzilla.netfilter.org/show_bug.cgi?id=1130 Bug ID: 1130 Summary: Better handling DNS names in nft ruleset Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at netfilter.org

Right, time to (as someone said) put this thread to a proper rest. Some of you have probably read my VPN/Routing/Lost packages hassles in the last week, well, here is the rundown. Look at http://statler.mupp.net/shorewall/Layout.jpg Basically. The shorewall knows the route to the .224.0/24 net is through .221.221. The systems in .221.0/24 has the FW as their default gw. The FW could reach

https://bugzilla.netfilter.org/show_bug.cgi?id=1463 Bug ID: 1463 Summary: nft --json table list ruleset crashes Product: nftables Version: unspecified Hardware: All OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org