Please remember to reply to the mailing list, not the original sender: http://gnudip2.sourceforge.net/#mailinglist
+++++++++ Sorry for the delay. My server's disk crashed. Even with backups, putting it back together has been painful and time comsuming. I just discovered I was losing E-mail from this list. === The port numbers used in the -g option have nothing to do with the GnuDIP server. These ports are only used locally to check for an IP address change. For example given your command "gdipc -g 3645:749", gdipc will send a UDP packet to port 3645 at the external address of your NAT box at the time of the last update, and listen with a time out on port 749, hoping to immediately receive the packet it just sent. So if the external address of your NAT box has changed, the packet will not arrive. You must forward UDP packets arriving at port 749 on the external interface of your NAT box to 3645 of the machine running gdipc, otherwise the packets will never arrive, and you will send unnecessary updates to your GnuDIP service. Agsin, it is important to understand that the GnuDIP service is not involved in this. > The actual output is as follows (names changed to protect the innocent): > > F:\Software\gdipc>gdipc -g 3645:749 > ==== gdipc.bat running: Wed Mar 20 23:41:27 2002 ==== > Configuration file name: F:/Software/gdipc/gdipc.conf.txt > Cache file name: F:/Software/gdipc/gdipc.cache.username.xyz.com.txt > Address validation failed for 24.136.122.212 - UDP packet timed out > Attempting update at xyz.com ... > Update to address 24.136.122.212 from 24.136.122.212 successful for > username.xyz.com > > So, it appears the ip address is being updated unnecessarily at the server > because the "Address validation" failed. How can I configure or run the > client to properly validate the existing ip address from behind a NAT? > > -brian > > > > =================================================================== > Original Email text follows: > =================================================================== > I am running the GnuDIP Client (WinNT) behind a firewall/NAT and I have > successfully updated a remote GnuDIP Server. > > This means that I have: > - defined a new udp port (xyz) on my client machine (in > %SystemRoot%\system32\drivers\services ) > > - configured my NAT to forward all port traffic for xyz to the machine > where the GnuDIP client is running > > PROBLEM: > ======== > When I run: > gdipc -g 3495:xyz > > The response is something to the effect: "UDP message timed out" (I > apologize for not providing the exact message...I am no longer at my machine > to get the exact text). > > Even though it displays the time out message, the process continues and > successfully updates the server (even though the dynamic address hadn't > changed). > > I have sent an email to the dynip domain server to see if they have > configured the server to receive requests on a different port, but I am > assuming they have not (waiting for a response from them). > > So, my questions are: > 1) Am I using the correct 'sendport' for the default server > installation? I looked through the GnuDIP server install to find a > reference to that port. If there is another 'default' port, what is it? > > 2) The successful message indicates the registered ip address has > changed from a.b.c.d to a.b.c.d (in other words, it did not > actually change). Does this mean the server did unnecessary update 'work' > or was the server able to figure out that an update did not need to take > place? > > I would like to set up the client to run as a daemon, but until I feel > satisfied I am not causing the server to work harder than it needs to, I'm > holding off. > > > Thanks for your help. > > -brian -- Creighton MacDonnell http://macdonnell.ca/ -- GnuDIP Mailing List http://gnudip2.sourceforge.net/#mailinglist
