Re: not secure port
Steve, I had this exact problem. The problem is that the way NAT is done is to choose an arbitrary port number and associate it with an IP inside the NAT. Search the archive of this list for Amanda through translated addresses where Pedro Caria shared with me a patch to remove the port check from amanda. This could work, but I never tried it. I just gave up and created two separate backup systems. Search also for Amanda and firewall This was another thread that I started in which folks gave useful suggestions. Hope this helps. Let me know if I can help in any other way. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 Steve Bertrand [EMAIL PROTECTED] 12/12/02 09:01AM Hi there. I have a problem for which I have done research on using google, mailing lists and other resourses, but have gotten no definitive answer to date. If someone could help me I would be ever greatful. I have amanda set up on FreeBSD, which was working great behind a Linksys NAT gateway, pulling backups from several locations on the Internet. I have since relocated my amanda box to a different physical location, and it is now behind a Netopia nat gateway. The internal IP address of the box has changed, as well as the external IP of the nat gateway. I have updated .amandahosts on all machines accordingly, but now I get the following on all of my remote machines I am backing up: ERROR: svr3: [host netopia-external-ip.domain.com : port 64559 not secure] I rebuilt amanda with the following: --with-tcpports=1500,2000 --with-udpports=800,900 with no luck. Could someone please advise. Tks, Steve Bertrand
Re: not secure port
On Fri, Dec 20, 2002 at 03:52:03PM -0500, KEVIN ZEMBOWER wrote: Steve, I had this exact problem. The problem is that the way NAT is done is to choose an arbitrary port number and associate it with an IP inside the NAT. Search the archive of this list for Amanda through translated addresses where Pedro Caria shared with me a patch to remove the port check from amanda. This could work, but I never tried it. I just gave up and created two separate backup systems. Search also for Amanda and firewall This was another thread that I started in which folks gave useful suggestions. Steve Bertrand [EMAIL PROTECTED] 12/12/02 09:01AM ERROR: svr3: [host netopia-external-ip.domain.com : port 64559 not secure] I seem to recall, though never experienced it, that if root tries to access the port rather than the expected amanda user, the same message is generated. I'm sure someone will correct me if my memory is failing. :) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: not secure port
Steve Bertrand wrote: Hi there. I have a problem for which I have done research on using google, mailing lists and other resourses, but have gotten no definitive answer to date. If someone could help me I would be ever greatful. I have amanda set up on FreeBSD, which was working great behind a Linksys NAT gateway, pulling backups from several locations on the Internet. I have since relocated my amanda box to a different physical location, and it is now behind a Netopia nat gateway. The internal IP address of the box has changed, as well as the external IP of the nat gateway. I have updated .amandahosts on all machines accordingly, but now I get the following on all of my remote machines I am backing up: ERROR: svr3: [host netopia-external-ip.domain.com : port 64559 not secure] The ideal solution would be to configure the NAT gateway to map secure ports ( 1024) to secure ports. You might consult Linksys to determine whether this is possible. John Dalbec I rebuilt amanda with the following: --with-tcpports=1500,2000 --with-udpports=800,900 with no luck. Could someone please advise. Tks, Steve Bertrand
