>Ok, I've posted to the group 2 times and no-one seems to have setup a worki=
>ng
>config through a firewall ...
That's not true, based on my monitoring of this list. I can think of
other possible reasons you have not gotten a reply, such as the folks
who have dealt with this are just plain busy, for one.
I'm lucky and don't have to use a firewall, so I'm not real familiar
with the Amanda side of that, and am not at all with the firewall config.
But I may be able to shed some light on what Amanda is doing.
First, can you confirm you have configured it to restrict itself to some
port ranges. What do you get for this in the top level of the source:
grep PORT config/config.h
Next, I'm pretty sure there were some problems with the 2.4.1p1 port
range allocation, but I think it was just in the TCP area (although I
could be wrong about that). Since 2.4.2 is official now, and really
shouldn't be hard to convert to using (the exact same config/compile
options should work), how about bringing that up as a test?
This is what I recall of the way things work, along with a look at
the code.
First, amcheck creates a datagram structure, creates a UDP socket.
Then, if UDPPORTRANGE (from --with-udpportrange) is defined, the bind
first tries this range. If that fails, it tries for any privileged port.
If that fails, it tries for any port. Note that it is therefor entirely
possible for you to ask that Amanda stay within A and B but it not be
able to and so it falls back to whatever it can get.
If you run "netstat -an", are all (or at least some) of the ports you
told Amanda to use available?
If none of this helps, the next thing I'll do is provide some temporary
debugging patches for you to apply to gather more information. Will that
be OK? Make sure you tell me which version of Amanda to do them against.
>Thomas J. Hudak
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
