I did something to this effect before I had a nice WAN router (pfSense) - had a script that went out and hit http://checkip.dyndns.org from my desktop and updated if necessary. There are a few publicly available tools you can use to do that precise thing, and dyndns.org has a very clear specification on how often you can hit it to check (15-30 minutes, I THINK - check!).
Still, the best way really is to let pfSense be your WAN router - that's what it was designed to do. On 5/15/06, Darkest.Cobra <[EMAIL PROTECTED]> wrote:
First of all, thanks for your answer... I still think that there's a way to make it work also on pfSense, like on Smoothwall... I've tried also IPCop and it worked really well without a problem with my DynDNS hosts... But, anyway, I'm a newbie in scripting and coding and so on... I have no idea... :P I will search for something to run in my local machine, as you have said... Thanks! - Luca Holger Bauer ha scritto: > pfSense can't use the pfSense dyndnsupdater in this scenario as it only sees the internal IP of it's WAN. > There are 3 ways how to resolve this: > 1) Let pfSense do the dialin so it is the real WAN and has a real public IP > 2) Let the router in front of the pfSense do the dyndns update as it sees the real WAN IP > 3) Use a tool running at one of your internal Machines that frequently connects to an outside server and asks this server which public IP it sees coming from your connection. It then will update the account when the external server reports another IP like for the previous request. > > Holger > >> -----Original Message----- >> From: Darkest.Cobra [mailto:[EMAIL PROTECTED] >> Sent: Monday, May 15, 2006 8:18 PM >> To: support@pfsense.com >> Subject: [pfSense Support] Problem with DynDNS daemon... >> >> >> Hi all! >> I'm newbie to pfSense... I have found it a couple of days >> ago... And it >> seems really reliable!! >> But I have a little problem with DynDNS... >> Searching the forum didn't solve the problem (maybe I've searched too >> fast :P)... So I'm hoping to find a little aid here! :D >> >> This is my problem... >> As you can see in the attachment "mynet.pdf", you can have a >> look at my >> home network... >> When I start the DynDNS daemon it works really fine, but it >> updates my >> DynDNS host with my WAN Private Address (192.168.0.100) >> instead of mine >> Router Public Address (x.x.x.x) >> After the first update, DynDNS cache is filled with my WAN Private >> Address and when it tries to do another update, it says that >> the DynDNS >> host is already correct, obviously... >> >> I had this problem also on Smoothwall, but with two light >> scripts that >> take the Public Address from a DynDNS web page and the other >> that login >> into my DynDNS account, updating it, the problem was solved... >> >> I don't know if I can attach them to my mail... But... >> Anyway... I do it >> :P Maybe they can help... >> >> You would also know that: >> >> - The router itself establishes the connection to my ISP... >> - I have a Dynamic Address >> - Into the General Setup I have specified one ISP DNS Server >> - Something else? >> >> I'm sorry for my bad bad English... >> >> Thanks for every answer! >> >> - Luca >> > > ____________ > Virus checked by G DATA AntiVirusKit > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
