 mthoward
join:2005-10-12 Andover, MA
| reply to michaelr7 Re: [Config] DynDNS.org on Cisco 871
said by michaelr7 : For me it never failed to work. I loaded the latest 12.4T image onto the 871and 877 as soon as they arrive. They have always worked with dyndns.org. I keep my configs in a cvs repository and so I always load them via tftp. It also works on the 1841 and 2811. Who knows. 12.4(4)T never worked for me. This was the advanced ip services IOS image.
Cisco gave me a test release at the end of January. I tested and confirmed that it works OK.
Here is a message that I received from the Cisco Rep:
The bug which I filed (CSCsc98908) was duplicated to another obscure bug (CSCeh08545) which resolves the problem you were seeing (that is the bug fix the DE put into the special image you are running). So, the bug which resolves the problem (CSCeh08545) is integrated in the image you were given to test with. That same bug will be in 12.4(5.13)T4 and later IOS releases. There is no publicly available image on CCO yet that has the bug fix which you need. My suggestion is to wait about 2 months and then if you want to, download the latest 12.4T IOS (later than 12.4(5.13)T4.
|
|
 michaelr7
join:2004-03-26 Tucson, AZ
| reply to mthoward quote: There were problems with the CLI interpreting the ? as a help command. But if you loaded the config via TFTP the problems were still there.
For me it never failed to work. I loaded the latest 12.4T image onto the 871and 877 as soon as they arrive. They have always worked with dyndns.org. I keep my configs in a cvs repository and so I always load them via tftp. It also works on the 1841 and 2811. |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to twojciac said by twojciac :CSCeg41935 has been resolved and will be integrated into 12.4(6)T2, 12.4(6)3. Looks like end of Feb is a target for the 12.4(7) mainline code integration. I do not think that this was the problem.
There were problems with the CLI interpreting the ? as a help command. But if you loaded the config via TFTP the problems were still there.
This feature fundamentally never worked on the 871.
It is clear to me that it was never tested. |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to mthoward Cisco has given me a prerelease test IOS that fixes this bug with DynDNS update on a Cisco 871.
My testing indicates that it works OK.
They have not told me when it will be 'officially' released.
Although, frankly after months of sending configs & ethereal dumps to Cisco I have lost interest. I had to come up with another solution, so the 871 is sitting unused on my rack ... updating a test DynDNS entry occassionally 
Miguel |
|
 was1
join:2005-12-25 Elkhart, IN | reply to mthoward Thanks TROLL131313, that clears it. I was doing double NAT. Any idea ip ddns works with 12.3(10) IOS ? I cant upgrade to 12.4 beacuse ive only got 24 MB of flash. |
|
 TROLL131313
join:2004-12-21 Horsham, PA
·Comcast
| reply to was1 Your DSL modem should be on Ethernet 4. Also, you should set your westell 6100 to bridge mode (IP Pass through) or you will be doing a double Nat set up.
To do this, you will have to shut off DHCP and set the VPI/VCI settings in the modem to bridged. Then you will have to set up Eth 4 (WAN Port) with a PPoE dialler instead of DHCP. |
|
 was1
join:2005-12-25 Elkhart, IN
| reply to mthoward I am also going to give a try to setup Dynamic DNS on 871. I have a question abot the equipment setup. Guys is your DSL modems connected to the WAN port on the router ? or to the any of the fast ethernet 0-3 ports ?
I have a westell 6100 and wonderng what should be the interface under i should configure Dynamic DNS. |
|
 immy
join:2002-04-06 Australia | reply to mthoward Well 12.4(6)T is out and dyndns isnt working on my 877.
Has anyone got a working config?
 |
|
 tdoran Premium join:2003-09-27 Ridge, NY
| reply to mthoward Other DDNS "Bugs": |
|
 tdoran Premium join:2003-09-27 Ridge, NY
| reply to twojciac said by twojciac :CSCeg41935 has been resolved and will be integrated into 12.4(6)T2, 12.4(6)3. Looks like end of Feb is a target for the 12.4(7) mainline code integration. More complete description:
CSCeg41935 Bug Details
Headline DDNS - Question mark is not understood by parser Product IOS Feature OTHERS Components Duplicate of Severity 3 Status More First Found-in Version 12.3(8)YA All affected versions First Fixed-in Version 12.4(6.3), 12.4(6.2)T
Release Notes
Unable to configure Dynamic DNS IOS support with HTTP method if URL string contains a question mark.
CLI understands the question mark as a request for context sensitive help.
Workaround: use %3F for '?', so you can enter it manually.
All affected versions 12.3(11)YS 12.3(11)YS1 12.3(14r)T 12.3(14r)T1 12.3(14)YT 12.3(14)YT1 12.3(4)XK4 12.3(4)XQ 12.3(4)XQ1 12.3(4)XK 12.3(4)XK1 12.3(4)XK2 12.3(4)XK3 12.3(7)XR4 12.3(7)XR5 12.3(7)XR6 12.3(7)XS 12.3(7)XS1 12.3(7)XS2 12.3(7)XR 12.3(7)XR1 12.3(7)XR2 12.3(7)XR3 12.3(8)XX2a 12.3(8)XX2b 12.3(8)XX2c 12.3(8)YA1 12.3(8)YA 12.3(8)XX 12.3(8)XX1 12.3(8)XX2 12.4(1) 12.4(1a) 12.4(1b) 12.4(1c) 12.4(1r) 12.4(2)MR1 12.4(2)XA 12.4(2)XA1 12.4(2)XB 12.4(2)T 12.4(2)T1 12.4(2)T2 12.4(2)MR 12.4(3) 12.4(3a) 12.4(3b) 12.4(4r)XD 12.4(4)T 12.4(4)T1 12.4(4)MR 12.4(5) 12.4(57)ARF 12.4(57)ARF2 12.4(57)COMP
More - Problem described in the bug report is fixed and tested in some but not all versions in which it is intended to be fixed. Placing a bug report into this state allows the fixed code to be integrated into some releases. The engineer moves the bug report into the Resolved state when the problem is fixed in all versions. |
|
  twojciac
join:2003-05-22 Sachse, TX | reply to mthoward CSCeg41935 has been resolved and will be integrated into 12.4(6)T2, 12.4(6)3. Looks like end of Feb is a target for the 12.4(7) mainline code integration. |
|
 Zolee
join:2006-01-25 10645
| reply to mthoward I noticed the same thing. I used a couple of different routers with the latest images but it sucks.
dyndns.org
1811W works the same way you router does 871 does not work at all, no DDNS updates on the website at all, under any circumstances 2801 same |
|
 Innuendo Premium join:2002-12-20 | reply to mthoward mthoward, My mistake. I thought this was your own personal router. If it is owned by the company then it is legal.
Never mind.  |
|
 mthoward
join:2005-10-12 Andover, MA | reply to Innuendo The company does have coverage on it. |
|
 Innuendo Premium join:2002-12-20
| reply to mthoward mthoward, Oh, well, that explains it...no downloads allowed without a valid SmartNet contract.
I feel compelled to point out, though, that what you did was technically illegal. You're only allowed to download IOS images for hardware you don't have coverage on. |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to Innuendo said by Innuendo :I downloaded it right away and don't have any special credentials other than a SmartNet contract. I had tried to download with my personal account ... no SmartNet contract ... still learning.
Using the company's login credentials (which have SmartNet) I was successfully able to download. |
|
 Innuendo Premium join:2002-12-20 | reply to mthoward mthoward, Very odd...maybe you answered one of the export questions wrong. I downloaded it right away and don't have any special credentials other than a SmartNet contract. |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to davelaw said by davelaw :The fixed DDNS code for the 871 (and 831) should be posted in about a month If I get a chance will post the bugid in next couple days Q: Is there any mechanism whereby I could be a beta tester for that code?
Miguel |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to Innuendo said by Innuendo :mthoward, I notice you are running an older IOS version. Have you tried the latest, 12.4.4T as well? I tried downloading 12.4.4T last nite.
After filling out all the crypto/export forms it popped a http auth dialog box and would not let me access the file ... I guess I do not have enough credentials.
I was going to ask someone at my company to download it for me this week ... although I hate to be bugging them just to download firmware for me.
Given that twojciac says that Cisco is fixing these things as we speak, then perhaps I should wait.
Miguel |
|
 mthoward
join:2005-10-12 Andover, MA
| reply to twojciac said by twojciac :The Ctrl-V workaround will only work on your running config. The bug is that it doesn't get saved properly, OK
said by twojciac :where a %3F would. It's being worked on right now... Per my previous message, note that %3F does not work with DynDNS.org ... although it might work with some other http-based ddns services.
Miguel |
|