23 replies to this topic

[VK4AKP]

Why doesn't dyndns.org work with the Billion routers?

Is it because dyndns is now www.dyndns.com instead of .org?

Can this be fixed?

.-.-.

[VK4AKP]

Why doesn't dyndns.org work with the Billion routers?

Is it because dyndns is now www.dyndns.com instead of .org?

Can this be fixed?

.-.-.

Humm, no replies yet???

OK, Still trying to work this out.

Email Status also has never worked for me with this device.

Both these things have simple settings. I can not see where I am going wrong. Maybe I'm not? Is the firmware simple broken?

it is version 5.08a.dk4

I also notice in the events log that there are no events for either of these services.

Do I perhaps need to turn the Loging on to a higher setting? If so where? I can not find where.

Any help soon please????

.-.-.

[Markovich]

Not that it probably helps much, but dyndns.org is working fine here with my 7402VGO with 5.07.

My settings are:

Dynamic DNS - Enable
Server - www.dyndns.org (dynamic)
Wildcard - Disable
Domain Name - <my.dyndns.domain>
Username - <username>
Password - <password>
Period - 25 days

After every reboot of the router (which I have reduced from once daily to once weekly since 5.07) the sync with the dyndns server is reported in the event log as follows:

Jan 01 10:02:04 home.gateway:ddns:none: starting to update at [www.dyndns.org (dynamic)].
Jan 01 10:02:04 home.gateway:ddns:none: host name [<my.dyndns.domain>].
Jan 01 10:02:04 home.gateway:ddns:none: username [<username>].
Jan 01 10:02:04 home.gateway:ddns:none: my IP address [<myi.pad.dre.ss].
Jan 01 10:02:05 home.gateway:ddns:none: update successful.
Jan 01 10:02:05 home.gateway:ddns:none: update <my.dyndns.domain> successfully.

[VK4AKP]

Hi, thanks for the reply.

Yes it has me beat. The settings are so very simple.

I had DynDns working on my Linksys WRT54GP2, when engin killed it remotely I was forced to buy the Billion.

I have never been able to get both Email Status and DynDns to work with my Billion 6404VGP since the day I got it.

I have tried many combinations of settings and different email servers and still nothing.

I even tried a firmware upgrade to the now supposedly stable firmware on their web site (And I can tell you it is far from stable).

SO I went back to the originally shipped 5.08

I never see any mention of the device even trying to update the dyndns site or check for waiting emails in the logs of the box at all.

I have done that many factory resets and entered the settings in manually again that I care to even think about. Still nothing.

That log you have shown me, is that from your actual Billion device? I never get any entries like that in mine.

.-.-.

[Markovich]

That log you have shown me, is that from your actual Billion device? I never get any entries like that in mine.

Well, I actually captured it from the Billion 741/743 SNMP Viewer (via Syslog), but it is the same information as shows up in the web GUI's Event Log.

[VK4AKP]

Well, I actually captured it from the Billion 741/743 SNMP Viewer (via Syslog), but it is the same information as shows up in the web GUI's Event Log.

Humm, OK, Well I assume then that that shows than my Box is not even trying to check the Email Status or update my Dyndns address?

OK, so what do I try or do next to try and resolve this situation?

.-.-.

[tgillett]

VK4AKP
dyndns.org is working for me on 7402VGP with 5.52 (and previous) firmware.

I should be able to test on 6404VGP over the next week or so when I get access to one.

T

[VK4AKP]

VK4AKP
dyndns.org is working for me on 7402VGP with 5.52 (and previous) firmware.

I should be able to test on 6404VGP over the next week or so when I get access to one.

T

Still no joy my end getting either dyndns or Email status working on my router.

.-.-.

[tgillett]

Still no joy my end getting either dyndns or Email status working on my router.

.-.-.

VK4AKP
Apologies for the delay in getting to this, but I've just managed to retrieve a 6404 from service to do some testing.

My test set up is a 7404VGP connected to the internet, and the 6404VGP connected via its WAN port to a LAN port on the 7404. The 6404 is running on subnet 192.168.2.x while the 7404 is running on the default subnet of 192.168.1.x. The 6404 is set to obtain its WAN address etc automatically from the 7404 host.
Both devices are running 5.08 firmware. Firewall is off on both devices. I am using dyndns.org accounts for testing.

The 7404 has ddns working correctly with Event Log entries as described in earlier post. I can access the GUI from the internet via the ddns address with a suitable Virtual Server rule set up.

The 6404 seems to be mostly working correctly, with a couple of exceptions.

I have successfully registered VSPs on both phone ports and can place and receive calls. A PC plugged into the LAN port on the 6404 can access the internet via the 7404 gateway.

1. Firstly, ddns doesn't appear to be working from the log entries.
However I think it is actually correctly registering the device as I can ping it successfully and see the WAN led flash with the pings.

I have set logging level for ddns to 'all' with the CLI command:
system log set ddns all

The only log entry that appears on restart is as follows:
May 06 12:56:37 home2.gateway:ddns:none: IP interface setting error.

I tried to forward port 80 form the 6404 address on the 7404 segment with a Virtual Server rule on the 7404 but can't get to the GUI on the 6404. This arrangement works for the 7404 and other devices on the main subnet.

2. Second, I can not get any incoming audio on PSTN calls either incoming or outgoing.
I can make calls from an Astratel account registered on a 6404 phone port to another Astratel account registered on the 7404 phone port and the audio works OK.
I haven't been able to test to see if this is also true for an Astratel account at a different site, but I'll test when I get a chance.

Not sure if these two situations are related, but it seems to me there may be a problem with passing ports from the 6404 through the 7404 to and from the internet.
Also the ddns logging in the 6404 is not working the same as in the 7404.

Any suggestions would be welcome.


Regards
T

Edited by tgillett, 06 May 2007 - 01:13 PM.

[MarkLL]

1. Firstly, ddns doesn't appear to be working from the log entries.
However I think it is actually correctly registering the device as I can ping it successfully and see the WAN led flash with the pings.

I have set logging level for ddns to 'all' with the CLI command:
system log set ddns all

The only log entry that appears on restart is as follows:
May 06 12:56:37 home2.gateway:ddns:none: IP interface setting error.

Can you see if it works when the device is attached as a router and doing the PPPoE?

If you think about... it won't work in ATA mode or where the IP address is a local IP address because that would not be valid to DynDNS anyway.

You sort of need STUN for Dydns...

[VK4AKP]

Well all I know is that when I had my LinkSys WRT54GP2-EA Box running, DynDNS worked.

Then engin killed my Linksys Box, so I bought a Billion 6404VGP.

* DynDNS and EMail status have never worked from this point on.

DynDNS.org send me emails all the time telling me that my IP is not being updated. And in the end they gave up on me and cancled my account.

The settings in the Billion box for DynDNS and Email Status are very simple. Impossible to stuff up.

I tried going to newer firmware, but it was even worse 5.52e. (No I won't try [f] it is reported as just as bad).

It would stop registering the phone ports and reboot and had firewall sticking issues. The list goes on.

Billion really need to get a new stable working release out before they continue to add features.

I am starting to consider the software to be so bad in these devices that I am now looking to buy a Fritz Box instead.

My current basic disapointments with the Billion device under factory shipped firmware (5.08) are ...

- Conference calling does not work.
- DynDNS does not work.
- Email Status doesn't work.
- Earpeace volume should be louder. (I have mine set to max) Still too quiet.
- Newer firmware is not worth installing because it adds more faults and then is difficult to restore to 5.08.

.-.-.

[tgillett]

Can you see if it works when the device is attached as a router and doing the PPPoE?

If you think about... it won't work in ATA mode or where the IP address is a local IP address because that would not be valid to DynDNS anyway.

You sort of need STUN for Dydns...

No I don't have a stand alone modem.

I'm not so concerned about the ddns - I was just testing that for VK4AKP. I am sure the ddns is actually working as it definitely registers with dyndns.org and you can ping the router at the dyndns address. Not sure what else can be done however...
VK4AKP - have you tried to ping the router?

However I am really concerned about using it for voip behind another router, and it appears that it will not work correctly for this.

I've tested it in VoIP Router and ATA modes, but can't get it to work without using Voxalot to to the NAT traversal.

It appears that it may only work behind a simple modem.

T

Edited by tgillett, 06 May 2007 - 09:49 PM.

[VK4AKP]

OK, I've registered with DynDNS again.

I had to do this because they had cancled my account as teh Billion box had never not even once registered with Dyndns in over a month.

Yes I cna ping it because when you register it gets your IP from the browser. So unless your IP changes, even though Billion box is not updating the IP is still correct.

If I were to cycle the modem connection and obtain a different IP then I would not be able to ping it becasue the Billion box never tries to update the the address.

I also tried Email status again, and it still does not work either.

No mention of either in any of my logs.

.-.-.

[VK4AKP]

I've mentioned this before. but just in case it has something to do wiht it.

You do realise that DynDNS.org is no longer .org that their site has gone .COM this doesn't have anything to do with it does it?

In the Billion menu's it refers to it as .org but their wen site is now .com

.-.-.

[tgillett]

VK4AKP
My dyndns.org account is still working fine for me on the 7402 box so I don't think that is the problem.

I seem to recall that when I registered, I had a choice as to which domain my dyndns account was in.

Is your account in dyndns.org?

T

[VK4AKP]

VK4AKP
My dyndns.org account is still working fine for me on the 7402 box so I don't think that is the problem.

I seem to recall that when I registered, I had a choice as to which domain my dyndns account was in.

Is your account in dyndns.org?

T

Yes.

vk4akp.dyndns.org

.-.-.

[tgillett]

Pings OK from here so it is being set up OK. You should see the WAN light blink if you ping it.

Pinging vk4akp.dyndns.org [210.49.234.243] with 32 bytes of data:

Reply from 210.49.234.243: bytes=32 time=55ms TTL=119
Reply from 210.49.234.243: bytes=32 time=54ms TTL=119
Reply from 210.49.234.243: bytes=32 time=56ms TTL=119
Reply from 210.49.234.243: bytes=32 time=56ms TTL=119

Ping statistics for 210.49.234.243:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 56ms, Average = 55ms

[VK4AKP]

Pings OK from here so it is being set up OK. You should see the WAN light blink if you ping it.

Thats because when you register with DynDNS the site reads your IP from your browser.

So currently it is correct.

But if I were to cycle the cable modem and change the IP then it would not work, because the Billion 6404VGP does not even try to contact dyndns to update the IP location.

I am currently trying no-ip.com but so far same thing.

The Billion box is doing nothing.

.-.-.

[tgillett]

VK4AKP
Not quite sure what your setup is, but something at your end must be responding to the ping.
On my test setup I could see the WAN light flash for each ping.
If I take the box off line, the ping fails.
What happens in your setup if the 6404 is off?
Regards
T

[VK4AKP]

VK4AKP
Not quite sure what your setup is, but something at your end must be responding to the ping.
On my test setup I could see the WAN light flash for each ping.
If I take the box off line, the ping fails.
What happens in your setup if the 6404 is off?
Regards
T

YOur missing the point. Your pings etc are working because when a person registers at either Dnydns or No-IP the site reads your IP from the browser.

So even though my box is not registering my IP the IP is still correct currently.

If I cycle the Cable modem and obtain a different IP. Your tests will fail.

In fact I will do that now just to prove the point. ...

- There Done. my new IP is 210.49.89.162 my old one was 210.49.234.243

Now try pinging vk4akp.dyndns.org or vk4akp.no-ip.org

Fails right? Thats because the Billion Box is not regersterig the new IP.

Pinging vk4akp.dyndns.org [210.49.234.243] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 210.49.234.243:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging vk4akp.no-ip.org [210.49.234.243] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 210.49.234.243:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

.-.-.