D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-826L => Topic started by: dthims on March 29, 2014, 12:14:58 PM
-
opened wan (::) to lan (2002:44c0:XXXX:XXXX::X), then ran port test. sometimes it passes, sometimes it doesn't. very inconsistent. definitely works internally, but not externally. fw is 1.04na.
have no trouble with ipv4. that works perfectly. any suggestions would be helpful
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your router? Look at sticker under router.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- What region are you located?
- Are you wired or wireless connected to the router?
- Has a Factory Reset (http://blog.dlink.com/what-is-a-reset-button-when-should-i-use-it) been performed?
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
- Was the router working before any firmware updates?
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
- Is ISP Modem/Service using Dynamic or Static WAN IP addressing?
- What ISP Modem service link speeds UP and Down do you have?
- Check cable between Modem and Router, swap out to be sure. Link> Cat6 is recommended. (http://en.wikipedia.org/wiki/CAT6)
- Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask. Link>Checking MTU Values (http://forums.dlink.com/index.php?topic=53008.0)
- For DSL/PPPoE connections on the router, ensure that "Always ON" option is enabled.
-
Hi,
sounds quite strange: A firewall sometimes passing and sometimes not.
I'd guess that IPv6 packets matching your firewall rule will always pass and in those cases you think that your firewall blocks them, packets got dropped somewhere else before reaching your router.
So why? Well, you use 6to4 known to have issues, see RFC6343 (http://tools.ietf.org/html/rfc6343#section-3).
Perhaps you could try another IPv6 access technique, e.g. 6rd (if supported by your ISP) or HE tunnel, and then test if the problem persists ...
PT
-
hey, thnx for the quick replies. created that tunnel as you suggested and it's doing the same thing. ipv6 does not work with this unit. on the scan test, on the 4th try it said open. then about 30 seconds later, it was back closed. this time the address was 2001:X:X:X, not 2002:X:X:X
-
... I hope it wasn't 2001:0::/32, because in this case you would have used Teredo where a client behind your router terminates an IPv6 over UDP/IPv4 tunnel and your router has absolutely nothing to do with IPv6? And Teredo is even worse than 6to4, being the last choice if nothing better is available.