Displaying 20 results from an estimated 12000 matches similar to: "Long Shorewall Startup Times Revisited"
2004 Feb 02
1
ldaps connections
It is my understanding that a secure ldap connection should only send
encrypted data yet my configuration is sending plaintext
The following strace output from a smbpasswd results in the following:
connect(4, {sin_family=AF_INET, sin_port=htons(636),
sin_addr=inet_addr("<ldap server>")}}, 16) = -1 EINPROGRESS (Operation
now in progress)
...snip...
write(4,
2004 Jan 30
1
Samba 3.0.1 and OpenLDAP 2.2.4 with TLS
Hi all,
I've been searching the lists and web for an answer but i'm stumped hope
some one here has an answer for me. As I'm new to this sysadmin role.
I have set up OpenLDAP to authenticate our linux users and exim MTAs.
This all works fine with OpenLDAP only providing a ldaps:/// connection
on 636.
However I cannot for the life of me get samba to speak tls to it. I've
seen
2004 Feb 10
2
Self Signed SSL Certificate from ldap server
How do i get samba to accept a self signed certificate from my ldap server?
I have a self signed CA that created a certifcate for my ldap server.
I've added the CA to the openssl frame work. <ssl-base>certs/ca.pem and
<ssl-base>certs/<ca hash>.0.pem
Yet I still get errors from samba 3.0.2
Is it not possible? If I add in SSLeay libraries will that sort it? I
beleived that
2005 Jun 30
1
Virtual Server
shorewall-users,
I''d like to expose a local NAT''d machine externally but only
reachable on that IP. The example documents show exposing a web
server on an external ip but that server is also reachable on any
other ip that is proxyarp''d by the gateway server.
Sorry if it isn''t a very clear description.
Any help is appreciated.
Cheers
--
Martin
2002 Aug 09
2
Proxy Arp
Hopefully this is an easy question....
I''m using a leaf router (bearing) running shorewall. Three interfaces net,
loc, and dmz. Only one computer in the dmz and its being proxy arp''d.
External and internal (net and loc) can reach the dmz but the dmz cannot
reach the isp''s gateway and beyond, but can reach a system adjacent to the
firewall.
2007 Oct 06
7
ipp2p segmentation fault
Hi all.
On Sep 26th I decided to try and get ipp2p working on my machine that acts as a gateway for my Internet connection.
This machine is running Debian.
I performed the install by doing the following steps:
- I installed the Debian package called linux-source-2.6.22 for my Linux kernel source and unpacked the resulting tar.bz2 file.
- From the netfilter.org site I downloaded the following
2006 Feb 14
1
[Bug 449] New: [patch] mount-point+inode ipt_owner patch (created 18 months ago)
https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=449
Summary: [patch] mount-point+inode ipt_owner patch (created 18
months ago)
Product: netfilter/iptables
Version: linux-2.6.x
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: ip_tables (kernel)
2005 May 29
17
Plans for 2.4.0
Hi folks,
Has anyone tested the changes to multiple ISPs/load balancing or
routestopped in 2.4.0-RC1 yet? We need to talk about what criteria we
will use for determining whether 2.4.0 is ready for release.
I''ve started configuring a firewall at work with the multiple ISPs
support, but its kernel doesn''t have connection marking support, so it''s
going to be a couple of
2008 Nov 01
8
OpenVZ & shorewall. Did'nt work acl based on ip range.
Hello all,
It''s my first letter on this list, and, my English is not very well.
Please take me indulgence
for grammar/syntax and over erorrs :))
I have trouble for acl''s of ip range. But, acl for one host (with ip
adress) work fine.
Please help me for make work acl/find erorr in acl.
Becouse I''m new shorewall user, I maked test configuration on Virtual
Mashine
2004 Oct 22
3
iptables: No chain/target/match by that name
I''m trying to setup Shorewall 2.0.8 with the one-interface settings on
my LFS (kernel 2.6.5) system. I''ve read the troubleshooting guide,
recompiled my kernel with just about every netfilter/iptables module I
could find, but I''m still getting this error:
# tail /tmp/trace
+ prefix=Shorewall:smurfs:DROP:
+ ''['' 22 -gt 29 '']''
+
2005 May 18
102
I quit.
It is with regret that I announce that Shorewall development and support is
officially ended.
Sean''s post has finally driven it home to me that in the long term, trying
to support a project like Shorewall is impossible for a person of my
personality and age.
Sean -- please believe that this isn''t about you or your post -- your post
was just the proverbial straw on this old
2018 Feb 17
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Hi Frederick,
I would expect that any duplicate names in the resulting data.frame would
have the suffixes appended to them, regardless of whether or not they are
used as the join key. So in my example I would expect "names.x" and
"names.y" to indicate their source data.frame.
While careful reading of the documentation reveals this is not the case, I
would argue the intent of
2018 Feb 17
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Hi Scott,
Thanks for the patch. I'm not really involved in R development; it
will be up to someone in the R core team to apply it. I would hazard
to say that even if correct (I haven't checked), it will not be
applied because the change might break existing code. For example it
seems like reasonable code might easily assume that a column with the
same name as "by.x" exists in
2018 Feb 20
3
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Hi Frederick,
It looks like I didn't overwrite the patch.diff file after the last edits.
Here's the correct patch (attached and copied below):
Index: src/library/base/R/merge.R
===================================================================
--- src/library/base/R/merge.R (revision 74280)
+++ src/library/base/R/merge.R (working copy)
@@ -157,6 +157,14 @@
}
2005 Jun 24
6
Is it that difficult?
Hello,
You will find in attachment the layout of my
current physical configuration.
For now, the Cable ISP is not used. Since it
is a dynamic ISP, my mailserver is rejected and
my domain name registers on blacklists like ORDB
and al.
I want it to be used as a default gateway except
for my mail server that would be seen as coming
from my "honest" ADSL ISP.
Here is
2018 Feb 18
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Thanks Duncan and Frederick,
I suspected as much - there doesn't appear to be any reason why conflicts
between by.x and names(y) shouldn't and cannot be checked, but I can see
how this might be more trouble than its worth given it potentially may
break downstream packages (i.e. any cases where this occurs but they expect
the name of the key column(s) to remain the same).
Best,
Scott
On
2007 Jun 29
12
testing instance variables that are set inside views
Hi all,
In my view specs (for Rails), how can I get at instance variables that
are set within my view? For example, if my view looks like this:
<% @header = "My Header" -%>
<div>some content</div>
How can I get to @header from within my view spec? I''ve tried @header
and assigns[:header] to no avail.
TIA,
Jeremy
--
Jeremy Stephens Computer Systems
2007 Jan 22
7
memcache
Just curious, is there anyway to use memcache with a ferret index?
Thanks,
Ray
--
Posted via http://www.ruby-forum.com/.
2018 Feb 18
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
Thanks Gabriel,
I think your suggested approach is 100% backwards compatible
Currently in the case of duplicate column names only the first can be
indexed by its name. This will always be the column appearing in by.x,
meaning the column in y with the same name cannot be accessed. Appending
".y" (suffixes[2L]) to this column means it can now be accessed, while
keeping the current
2018 Feb 22
2
Duplicate column names created by base::merge() when by.x has the same name as a column in y
>>>>> Gabriel Becker <gmbecker at ucdavis.edu>
>>>>> on Wed, 21 Feb 2018 07:11:44 -0800 writes:
> Hi all,
> For the record this approach isnt 100% backwards compatible, because
> names(mergeddf) will e incompatibly different. Thatx why i claimed
> bakcwards compatable-ish
exactly.
> That said its still worth considering