Hi, I've uploaded a new tarball to:
http://www.atagar.com/transfer/tmp/arm_bsdTest3.tar.bz2
http://www.atagar.com/transfer/tmp/arm_bsdTest3.tar.bz2.asc
Besides a modified version of Febian's patch to autodetect FreeBSD
jails it most notably includes...
- A replacement for the connection test
Damian Johnson atag...@gmail.com wrote:
John mentioned that for him connection resolution doesn't work in the
new arm tarball (arm_bsdTest2.tar.bz2). Hans, Fabian: can either of
you confirm, and if so what sort of issue is the log indicating?
I can't confirm this.
Also, there was interest
On Sun, 12 Dec 2010, Fabian Keil wrote:
Damian Johnson atag...@gmail.com wrote:
John mentioned that for him connection resolution doesn't work in the
new arm tarball (arm_bsdTest2.tar.bz2). Hans, Fabian: can either of
you confirm, and if so what sort of issue is the log indicating?
I can't
... Damian, how
many connections are on the node that you successfully see the conn list ?
I don't recall. It was on amunet and I'll retest this once the relay's
back up to speed (we recently switched ISPs so it'll take a few weeks
for the BW authorities to send more traffic our way again).
Fantastic - thanks Fabian! The patch looks perfect. I'll apply it
either after work today or tomorrow morning.
but I think the same should be done with connections on the SocksPort
Yup, sounds like a bug. Until recently arm had just been for relay
usage so I probably missed this when writing
On Mon, Dec 06, 2010 at 10:25:39AM -0800, Damian Johnson wrote:
Hazaa, many thanks for the patches! Committed with the exception of
sockstat2 (see below).
http://www.atagar.com/transfer/tmp/arm_bsdTest2.tar.bz2
One unrelated problem I noticed is that Arm tends to show local
connections
This IP serves as the internal adress to the jail when
called from a local subnet, and may show multiple connections to the
SocksPort,
usually IP:9050.
Sorry, I'm not sure if I'm following. You're saying that the check
should essentially be:
if (localPort == ORPort or localPort ==
On Mon, Dec 06, 2010 at 06:26:10PM -0800, Damian Johnson wrote:
if (localPort == ORPort or localPort == DirPort):
# treat as an inbound connection with the external ip
# this is part of arm's current behavior
elif (localPort == SocksPort and OS == FreeBSD):
# treat as an inbound
Damian Johnson atag...@gmail.com wrote:
Hi all. I've checked in the resolver fixes (thank Fabian and Hans!)
and a test tarball is available at:
http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2
http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2.asc
Thanks.
For BSD I'm using the
Answering to Fabian's mail, which came a minute before I was about send a
more verbose answer.
On Sun, Dec 05, 2010 at 01:02:16PM +0100, Fabian Keil wrote:
Damian Johnson atag...@gmail.com wrote:
Hi all. I've checked in the resolver fixes (thank Fabian and Hans!)
and a test tarball is
On Sat, Dec 04, 2010 at 07:49:58PM -0800, Damian Johnson wrote:
...
For BSD I'm using the following commands:
sockstat -4 | egrep 'process\s*pid' | grep -v '*:*'
procstat -f 'pgrep process' | grep 'pid' | grep -v '0.0.0.0:0'
The purpose of these greps is to only get established
Hans Schnehl torvallena...@gmail.com wrote:
On Sun, Dec 05, 2010 at 01:02:16PM +0100, Fabian Keil wrote:
Damian Johnson atag...@gmail.com wrote:
Hi all. I've checked in the resolver fixes (thank Fabian and Hans!)
and a test tarball is available at:
Hi all. I've checked in the resolver fixes (thank Fabian and Hans!)
and a test tarball is available at:
http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2
http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2.asc
I've added both of the commands you mentioned as fallback resolvers.
On Ubuntu
Damian Johnson atag...@gmail.com wrote:
The lsof command issued by arm [1] is:
lsof -nPi | grep process\s*pid.*(ESTABLISHED)
I'd be happy to work with you to provide a fix, if you'd like. Once
upon a time I tried to use VMs to troubleshoot FreeBSD and Gentoo
issues (thus far they're the
On Fri, 3 Dec 2010, Fabian Keil wrote:
- Be available to test a potential fix.
If you're up for that then I'm glad to have the help! Lets take
further discussion of this off the list. I don't think this is
generally of interest to the rest of the tor community. -Damian
It's at least
Perfect! I'll try to provide a fix for you to test later today or tomorrow.
I intent to try Arm in the future. Are you aware of anyone working on a port?
Nope. Jesse just finished an ebuild for Gentoo:
https://bugs.gentoo.org/show_bug.cgi?id=341731
and I'm working with Peter on a deb. But thus
On Fri, Dec 03, 2010 at 08:34:46PM +0100, Fabian Keil wrote:
Damian Johnson atag...@gmail.com wrote:
The lsof command issued by arm [1] is:
lsof -nPi | grep process\s*pid.*(ESTABLISHED)
What I'll need from you is the following:
- A command that, when executed as the tor user,
On Fri, 3 Dec 2010, Hans Schnehl wrote:
Sorry for jumping in , but please notice the above command might not
not work on all versions of FBSD, at least it doesn't on a 7-Stable jail.
Maybe the following just produces a similar sufficient output:
_...@ato# id
uid=256(_tor) gid=256(_tor)
On Fri, Dec 03, 2010 at 09:35:39PM +, John Case wrote:
On Fri, 3 Dec 2010, Hans Schnehl wrote:
Sorry for jumping in , but please notice the above command might not
not work on all versions of FBSD, at least it doesn't on a 7-Stable jail.
Not working refers to Fabian's use of
On Fri, 3 Dec 2010, Hans Schnehl wrote:
specifically:
ps -Al
after polling for lsof and a foreach loop, doesn't work ?
I know it's not elegant, but it appeared to me that:
lsof + ps -Al
would work ... especially if the system in question is doing little (or
nothing) other than Tor ...
I
The lsof command issued by arm [1] is:
lsof -nPi | grep process\s*pid.*(ESTABLISHED)
I'd be happy to work with you to provide a fix, if you'd like. Once
upon a time I tried to use VMs to troubleshoot FreeBSD and Gentoo
issues (thus far they're the only platforms to give arm any trouble).
However,
Arm should work just fine under BSD with the exception of the
connection listing.
The problem there is that FreeBSD's netstat lacks the flag to list the
pids associated with connections (so I can't narrow the list to tor
connections), ss is a completely different program (a spreadsheet
On Wed, 1 Dec 2010, Damian Johnson wrote:
Arm should work just fine under BSD with the exception of the
connection listing.
The problem there is that FreeBSD's netstat lacks the flag to list the
pids associated with connections (so I can't narrow the list to tor
connections), ss is a
Hi. After over a year it's about time that I announced an arm release
so here it is! What's new since August of 2009 [1], you ask? Lots. The
project has been under very active development, continuing to add
usability improvements to make relay operation nicer and less error
prone. If you're really
Hi Damian,
On Tue, 30 Nov 2010, Damian Johnson wrote:
Hi. After over a year it's about time that I announced an arm release
so here it is! What's new since August of 2009 [1], you ask? Lots. The
project has been under very active development, continuing to add
usability improvements to make
25 matches
Mail list logo
