Razzzhead, on Aug 7 2008, 10:20 AM, said:
Lich, are you saying that your script only gets in a mess when your assigned TSTT IP address ends in a zero? You say it's happened twice in one day, but did that result in problems both times compared to no problems when the assigned IP address ended non-zero? I could be the zero issue is a red herring since the chance of being assigned an address ending in zero in the range 190.59.0.z to 190.59.255.z is (256-2*) to 1. So that means if during your wall climbing to get your script working, you re-boot your router say 500 or so times, you would get an address of 190.59.n.0 maybe twice. If your assigned address is in a completely different range to 190.59.0.0/16 then the odds of course are different.
By the way, on which router are you using dd-wrt and for what reason?
[ * -2 because the addresses 190.59.0.0 and 190.59.255.255 should never be assigned]
After I follow the trail it was not the IP that caused it not to work, it still worked, the problem was blasted dnsomatic and opendns even when I assign an alias it tries to update all my networks which results in an error cause you can't update 2 different networks with the same IP. Eventually I made a mistake and got stuck in an infinite loop and then dyndns and opendns ban me for abuse since I was probably sending 100 updates per min, lol. Anyway I got unbanned and this guy showed me a form where I could make the code run then exit each time the wan interface goes up so that is what I will be working on instead of a plain startup script that resides in memory all the time.
To answer your question all my routers use dd-wrt I don't buy ones that can't use it. The problem was just as I identified, in opendns you can have multiple networks with different names. Now opendns is retards and they are the only service that only accepts ssl updates so I cannot use the built in Dynamic DNS client in dd-wrt or any other router to update opendns because none of them support ssl updates only regular http. Thus I went to dnsomatic which forwards the updates to all my accounts like opendns and dyndns etc. Problem is dnsomatic is stupid too and does not use the hostname correctly to update specific networks so I needed to make a script to run INADYN client which works and can update specific networks by using aliases. Problem is I need inadyn to run each time the wan ip changes which I should now be able to do. It was working before but it had to be always running in memory which is not bad but in the words of GW Bush the code needs to be redood so it will only run when the wan ip goes up then exit after it finishes update the server.
Many other people have this same problem and hopefully this script will solve that problem for them as well once I get it working. Right now I set mine on my Buffalo WHR-G125 to flash an LED while it is waiting for the wan IP to go up. This serves to look cool but it also for debugging because now I can count how many times the code runs through the while loop.
matt, on Aug 7 2008, 11:00 AM, said:
Isn't ip addresses assign by ppp are given a 255.255.255.255 subnet mask? And by your logic you should ((256 - 255) - 2), which equals -1 hosts address(which means no ip address).
Few applications and routers break, because they weren't designed with that situation in mind.
Nah he had it right the broadcast and subnet address should never be assigned.
Sign In
Register
Help
Add Reply
MultiQuote
