Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Sammy1Am]

UPnP seems to be failing somewhere between a few hours and a few days.  It will work as expected for a while after starting or restarting the router, but then trying to create any new UPnP mappings will fail, and the ones that have been already created usually stop working.  The commandline client upnpc fails to locate the router automatically, and manually navigating to http://192.168.0.1:65530/rootDesc.xml in Chrome returns a connection reset error instead of the expected XML device description.

I turned on debug messages in the logs, but there doesn't seem to be anything useful in there (though they also seem to be flooded with a bunch of IPv6 mDNS network hopping, so I'm going to try disabling that for a while and see if that helps).  I did update to 2.10 and still had the same issue with UPnP, however my wireless network kept going down (I guess a known issue) so I downgraded back to 2.07.  After the downgrade, I reset the router and manually re-entered all my settings (i.e. I didn't import them).

Restarting the router seems to fix the problem, but it's awful inconvenient to have to restart the router about once a day just to keep UPnP working.  Anyone have any ideas or experience the same issue?

[FurryNutz]

Try Opera or FF? If IE 8 or 9, set compatibility mode and test again.
Chrome has been known to create problems.

Was factory resets performed both before and after upgrading the FW and was the router set up from scratch with out a saved configuration file being loaded?

Can you downgrade to v2.03 and test?

[Sammy1Am]

Unfortunately, I wasn't expecting quite such a quick reply (thanks though!), so I restarted my router, which means UPnP is working again, so I can't yet try to browse to that URL with another browser (i.e. it works fine now).

I did not do a factory reset before up/down grading, only after, but I did do the set-up from scratch.

I've disabled IPv6 multicast streams since there seemed to be a related message flooding the logs ("Joining mDNS multicast group on interface..." about 4 times a minute), so there's a chance that will make a difference and I'll report back.

As soon as it stops working again though, I'll try that URL in IE and Firefox (though I suspect a connection-reset error will look pretty much the same on any browser).  Then I'll try downgrading to 2.03 and run that for a while to see if it makes any difference.  I'll check the logs again too to see if there's anything useful in there.

[FurryNutz]

Be sure to do a factory reset and test as well.
I would test this out with maybe just ONE or TWO other devices, turn off others maybe if you can. Could be something on the line thats the root cause.

Keep us posted.

[Sammy1Am]

In response to your questions in the other thread (sorry for not responding to that one; I must have forgot to press "notify" on that thread:


What region are you located?
U.S.

What ISP Service do you have? Cable or DSL?
DSL (U-Verse)

What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
It's a Motorola 2210-02.  It's set up on bridge mode so that the router gets a real WAN IP.

Some things to try: - Log into the routers web page at 192.168.0.1.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
All turned off.

Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Check.

Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
I've got UDP on Address Restricted, and TCP on Port and Address restricted.  Unless there's some real connection between the firewall and UPnP though, I'd rather leave these as they are since I can't reproduce the problem quickly and would have to leave them less restricted for a long time.

Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
There WERE both enabled, though I just disabled IPv6 multicast streaming to see if it would fix that log thing (it didn't, see below).

WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
It's set on Auto, and as far as I know, my modem doesn't support Gigabit.

Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Turn off all devices accept for one wired PC while testing.
Where applicable these are turned off; usually when the UPnP failure occurs, there is only one wired PC connected to the router turned on.  I don't usually notice til I try using the other devices though.

Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended.
The cable is still there  



On an additional note, it seems like about every 4-5 seconds, I get the following messages in the router's log (addresses redacted):

Code: [Select]

Jan 14 11:16:14 info  version 1.7 started
Jan 14 11:16:14 info  Joining mDNS multicast group on interface br0.IPv6 with address <IP6address>.
Jan 14 11:16:14 info  Leaving mDNS multicast group on interface br0.IPv6 with address fe80::218:e7ff:feef:f5b8.
Jan 14 11:16:12 info  Joining mDNS multicast group on interface br0.IPv6 with address fe80::218:e7ff:feef:f5b8.
Jan 14 11:16:12 info  Leaving mDNS multicast group on interface br0.IPv6 with address <IP6address>.
Jan 14 11:16:12 info  version 1.7 startedThe log's just completely full of these messages since they pop up so often.  It's making looking for any other log messages hard, but also has me concerned there's something else up with all the constant leaving and joining.

Edit: I'm going to turn IPv6 to local-only for the time being since that seems to get rid of all these extra log messages, and might help make debugging the UPnP thing easier.

[FurryNutz]

In response to your questions in the other thread (sorry for not responding to that one; I must have forgot to press "notify" on that thread:


What region are you located?
U.S.

What ISP Service do you have? Cable or DSL?
DSL (U-Verse)

What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
It's a Motorola 2210-02.  It's set up on bridge mode so that the router gets a real WAN IP.
Any chance you can test this with out the modem being connected for uPnP testing? Just to see if the problem appears with or with out the modem being connected.

Some things to try: - Log into the routers web page at 192.168.0.1.
Turn off ALL QoS or Disable Traffic Shaping (DIR only) GameFuel (DGL only and if ON.) options. Advanced/QoS or Gamefuel.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
All turned off.

Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting.
Ensure devices are set to auto obtain an IP address.
Check.

Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall.
I've got UDP on Address Restricted, and TCP on Port and Address restricted.  Unless there's some real connection between the firewall and UPnP though, I'd rather leave these as they are since I can't reproduce the problem quickly and would have to leave them less restricted for a long time.
I recommend testing EndPoint Independent as well as a test. It won't both anything or lower the security by change this. This is for NAT Translation only, does not effect Firewall.

Enable uPnP and Multi-cast Streaming under Advanced/Networking. Disable uPnP for testing Port Forwarding rules.
There WERE both enabled, though I just disabled IPv6 multicast streaming to see if it would fix that log thing (it didn't, see below).

WAN Port Speed set to Auto or specific speed? Some newer ISP modems support 1000Mb so manually setting to Gb speeds can be supported by the router. Advanced/Advanced Networking/WAN Port Speed
It's set on Auto, and as far as I know, my modem doesn't support Gigabit.

Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
Turn off all devices accept for one wired PC while testing.
Where applicable these are turned off; usually when the UPnP failure occurs, there is only one wired PC connected to the router turned on.  I don't usually notice til I try using the other devices though.

Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended.
The cable is still there  



On an additional note, it seems like about every 4-5 seconds, I get the following messages in the router's log (addresses redacted):

Code: [Select]

Jan 14 11:16:14 info  version 1.7 started
Jan 14 11:16:14 info  Joining mDNS multicast group on interface br0.IPv6 with address <IP6address>.
Jan 14 11:16:14 info  Leaving mDNS multicast group on interface br0.IPv6 with address fe80::218:e7ff:feef:f5b8.
Jan 14 11:16:12 info  Joining mDNS multicast group on interface br0.IPv6 with address fe80::218:e7ff:feef:f5b8.
Jan 14 11:16:12 info  Leaving mDNS multicast group on interface br0.IPv6 with address <IP6address>.
Jan 14 11:16:12 info  version 1.7 startedThe log's just completely full of these messages since they pop up so often.  It's making looking for any other log messages hard, but also has me concerned there's something else up with all the constant leaving and joining.

Edit: I'm going to turn IPv6 to local-only for the time being since that seems to get rid of all these extra log messages, and might help make debugging the UPnP thing easier.
[/quote]

[Sammy1Am]

Alright, I went ahead and switched both to "EndPoint Independent".

Unfortunately, testing without the modem connected would mean that I would also be disconnected from the Internet.   I do have some spare routers lying around that I could use temporarily if it comes to that, but for now I'd like to see if any of these other steps makes a difference rather than having to set up a second non-Internet network at my house to test devices on.

Will update with more info as soon as UPnP breaks again, or in a few days if it does not.  (Optimistic for the latter)

[FurryNutz]

Trying to help you narrow down where or why the uPnP could be failing, either due to some other device being connected or possibly in the configuration and at very least something in FW. IF you can try this with out the modem being connected, that would be great if you can.

At last resort I would downgrade to v2.03 and test.

Keep us posted.

[Sammy1Am]

A quick update: UPnP seems to be stable once again, so the culprit would appear to be one of the things I've changed.  Given the abundance of issues caused by the IPv6 support on this device, I'm suspecting that it's probably the IPv6.  As I have time this week I will try re-enabling IPv6 to see if UPnP starts to fail again.

Any tips for safely configuring 6rd IPv6?

[FurryNutz]

Ensure your ISP, ISP Service and ISP Modem support IPv6. IF not, just disable or select Local Connection Only for IPv6 settings on the router.

[Sammy1Am]

Check, check, and check.  I had IPv6 running successfully actually for like a year or so.  It worked fine in 2.07 and 2.10 (though the wireless networks failed a lot in 2.10).  IPv6 itself doesn't have problems, but I suspect that it might be breaking the UPnP functionality on the router (as illogical as that seems, heh).

[FurryNutz]

You might go back and test v2.07 to see if it exhibits the same thing if you haven't already. I've contacted an IPv6 guru on here to see if he can help provide some input for you.

Possible bug with v2.10. 

[Sammy1Am]

I was on 2.07 when I experienced the issue (see title of thread).  I actually updated to 2.10 hoping it would fix the UPnP issues, which it did not.  Additionally, it caused those wireless issues others have seen, so I went back to 2.07 so I at least have wireless.

[FurryNutz]

I would phone contact DLink support and ask about this. They need some visibility on this as it could be an issue with the FW between IPv6 and uPNP. If you can talk to them about it and give them the details, hopefully they can reproduce in there labs and get a fix going. Not sure how much longer the 655 will be in a LIVE status before going EOL. It has been there work horse and I wold presume they are trying to keep it going. For how much longer I don't know since new routers seen at CES are on the near horizon.

Keep us posted.

[PacketTracer]

Any tips for safely configuring 6rd IPv6?

Before you set IPv6 to 'Local Connection only' you already had some other IPv6 configuration and a global IPv6 address active (the one you redacted in the router's log). What kind of configuration was this?

And does your ISP offer some kind of IPv6 Internet connection (either native or 6rd)? If not your former activation of IPv6 other than 'Local Connection only' did not make much sense and could have had negative side effects.

There is one exception: If your WAN side global IPv4 address is static, you can always activate 6to4 which works in any case even without IPv6 support of your ISP. So if you think IPv6 is the culprit of your UPnP problem and if your ISP doesn't provide 6rd or native IPv6 access test it by activating 6to4.

Edit: Sorry didn't see the last 4 messages wich were not yet present when I started writing my contribution