You might turn on logging and post the logs of what is being blocked.
Sometimes things are being blocked by rules you do not expect.
On Mon, Aug 19, 2013 at 4:18 PM, Gary Aitken vagab...@blackfoot.net wrote:
On 08/19/13 00:36, Jason Cox wrote:
Are you sure that your DNS requests are over
On Mon, Aug 19, 2013 at 1:06 AM, Gary Aitken vagab...@blackfoot.net wrote:
ipfw list
...
21109 allow tcp from any to 12.32.44.142 dst-port 53 in via tun0 setup
keep-state
21129 allow tcp from any to 12.32.36.65 dst-port 53 in via tun0 setup
keep-state
...
65534 deny log logamount 5 ip
Back when cvsup was in use, I mirrored the ports with cvsup-mirror. Then I
could add files and make changes. My servers used my repository so they
always had my changes and I only had to do them once.
I am trying to replicate the same setup now that subversion is used. I've
set up svnsync, and
On Mon, Dec 3, 2012 at 5:54 PM, Dan Lists lists@gmail.com wrote:
After upgrading a server from FreeBSD 7.3 to FreeBSD 8.3 I noticed
this bug. Since upgrading, getpwnam_r is acting inconsistently. If I
look up a user that does not exist and the name is 16 characters or
less, getpwnam_r
After upgrading a server from FreeBSD 7.3 to FreeBSD 8.3 I noticed
this bug. Since upgrading, getpwnam_r is acting inconsistently. If I
look up a user that does not exist and the name is 16 characters or
less, getpwnam_r returns 0 and the result is NULL. If the name is
more than 16 characters,
On Tue, Jun 12, 2012 at 12:06 PM, Polytropon free...@edvax.de wrote:
On Tue, 12 Jun 2012 08:29:02 -0500, Mark Felder wrote:
On Tue, 12 Jun 2012 00:06:21 -0500, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Comment: using a leading zero on the numeric fields is a BAD IDEA(tm) --
you
are
From http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/anoncvs.html
USA: anon...@anoncvs1.freebsd.org:/home/ncvs (For ssh, use ssh version
2 and no password is required.)
SSH2 HostKey: 2048 53:1f:15:a3:72:5c:43:f6:44:0e:6a:e9:bb:f8:01:62
/etc/ssh/ssh_host_dsa_key.pub
Example A-2. Using
