Old prefixes not being removed isn't really a problem. The problem lies in the fact that old prefixes not being marked as depreciated when it should have been.
Unifi TMnet Streamyx/Unifi & IPv6, Now live!
|
|
 Oct 21 2013, 08:17 PM
Show posts by this member only | IPv6 | Post
#241
|
 
Elite
4,541 posts Joined: Jan 2003 From: BSRPPG51 Access Concentrator  
|
|
Quote|
|
|
|
|
Oct 21 2013, 08:30 PM
Show posts by this member only | IPv6 | Post
#242
|
 
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(Moogle Stiltzkin @ Oct 21 2013, 07:33 PM) does all new ipv6 have to do this for first time setup ? Or is this something have to do on a regular basis after router reboot Honestly, if I did not reconnect to TM with my router so frequently during my debugging phase, this issue would have been non-existent for me. In fact, I could have left them at the default settings because I leave my router running 24/7 and my pppoe connection is rock solid. This setup is only required if you get very frequent disconnects on your pppoe connection and it auto reconnects within less than the preferred lifetime setting.  |
|
|
Oct 21 2013, 08:32 PM
|
Senior Member
4,454 posts Joined: Jan 2003
|
 This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:37 AM |
|
|
Oct 21 2013, 08:38 PM
Show posts by this member only | IPv6 | Post
#244
|
|
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(Moogle Stiltzkin @ Oct 21 2013, 08:32 PM) what is causing this ? Whos fault is it ? Unifis implementation, or the router firmware which lack support ? It's not really a "fault". But if I were to blame something, it's the dynamic prefixes that TM hands out.Same situation here. 24/7, but when i debug, i reboot my router after update or changes, so this could add up and start to be annoying for me too  If you reboot your router that connects to your client devices, the prefixes would automatically clear themselves, just like how disconnecting and reconnecting the ethernet interface on the client devices solves the problem. Rebooting your router is analogous to disconnecting and reconnecting to your client devices. So I really don't see any issues in this at all. I have a an access point connected to my router which my wireless laptop still connects to when I reboot my router, hence the old prefixes aren't cleared. Edit: haha, noticed that you edited to add that picture This post has been edited by Alpha Wolf: Oct 21 2013, 08:41 PM |
|
|
Oct 21 2013, 08:39 PM
|
 
VIP
6,008 posts Joined: Jan 2003
|
QUOTE(asellus @ Oct 21 2013, 08:17 PM) Old prefixes not being removed isn't really a problem. The problem lies in the fact that old prefixes not being marked as depreciated when it should have been. Ahh yeah Windows has that problem. I did some reading and found one way to address it: the routers sends a 0-second ValidLifetime RA to "clear" the prefix. This probably isn't supported by Mikrotik though. |
|
|
Oct 21 2013, 08:44 PM
Show posts by this member only | IPv6 | Post
#246
|
|
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(wKkaY @ Oct 21 2013, 08:39 PM) Ahh yeah Windows has that problem. I did some reading and found one way to address it: the routers sends a 0-second ValidLifetime RA to "clear" the prefix. This probably isn't supported by Mikrotik though. Interesting approach but I wonder if it works. This could be scripted in DD-WRT - launch radvd with a separate config file with 0 ValidLifeTime then kill radvd and launch it again with the primary config file. |
|
|
|
|
|
Oct 21 2013, 08:47 PM
|
|
Senior Member
4,454 posts Joined: Jan 2003
|
This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:40 AM |
|
|
Oct 21 2013, 08:47 PM
|
Elite
195 posts Joined: Sep 2006 
|
QUOTE(wKkaY @ Oct 21 2013, 08:39 PM) Ahh yeah Windows has that problem. I did some reading and found one way to address it: the routers sends a 0-second ValidLifetime RA to "clear" the prefix. This probably isn't supported by Mikrotik though.  RA is sent immediately after configuration is applied, should be able to script this right? CODE /ipv6 nd prefix add autonomous=yes disabled=no interface=ether2-master-local on-link=yes preferred-lifetime=0s prefix=2001:e68:dead:beef::/64 valid-lifetime=0s This post has been edited by rizvanrp: Oct 21 2013, 08:47 PM |
|
|
Oct 21 2013, 08:57 PM
|
|
VIP
6,008 posts Joined: Jan 2003
|
QUOTE(rizvanrp @ Oct 21 2013, 08:47 PM) RA is sent immediately after configuration is applied, should be able to script this right? Hmm you might be on to something!CODE /ipv6 nd prefix add autonomous=yes disabled=no interface=ether2-master-local on-link=yes preferred-lifetime=0s prefix=2001:e68:dead:beef::/64 valid-lifetime=0s Mikrotik wiki has a code snippet that can be used together with that: http://wiki.mikrotik.com/wiki/Manual:Scrip...ce_have_changed |
|
|
Oct 21 2013, 09:06 PM
Show posts by this member only | IPv6 | Post
#250
|
|
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(Moogle Stiltzkin @ Oct 21 2013, 07:11 PM) Okay i can't test ipv6 i found out. The web interface for configuring ipv6 on Tomato looks very promising as they have options for native ipv6. I am sure it's possible. So just wondering, does anyone with a tomato router who managed to get ipv6 to work yet ? Interested to know  @alpha - thx for confirming unifi ipv6 works on dd-wrt. i'm sure others will appreciate a pictorial guide to set that up  I'm considering where to place such a guide because it is going to be long and it pre-requires enabling jffs for installing additional applications or using optware and most importantly, running startup scripts to automate the process every time it boots up. Depending on the version of dd-wrt, additional ipv6 modules need to be downloaded and loaded onto dd-wrt separately.As for my setup, the only thing I'm wondering about right now is: Why do I get two different v6 prefixes for my WAN and LAN? Shouldn't they be the same? Also, I can reach my router from the external internet by using both my WAN or LAN v6 IP. This post has been edited by Alpha Wolf: Oct 21 2013, 09:16 PM |
|
|
Oct 21 2013, 09:16 PM
|
|
Senior Member
4,454 posts Joined: Jan 2003
|
This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:40 AM |
|
|
Oct 21 2013, 09:21 PM
Show posts by this member only | IPv6 | Post
#252
|
|
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(Moogle Stiltzkin @ Oct 21 2013, 09:16 PM) that sounds.... complicated Yes   , but this could all be easily scripted. You only need to get the right modules and application for your version of dd-wrt, particularly if you're using a different Linux kernel version. I am using the latest K3.X.On a side note, I had to modify and compile a switch driver to enable support for vlanids above 15, namely 500 and 600 that Unifi uses, for my Broadcom based router running linux kernel 3.10. This enables me to directly connect my dd-wrt router to the fiber modem. One less device to run 24/7 and no more requiring the use of that TM router as a bridge for internet, plus my IPTV still works when I need it. I could now use that L7 TM router for testing. Doubt it will work but maybe I could try flashing it with dd-wrt. This post has been edited by Alpha Wolf: Oct 21 2013, 09:32 PM |
|
|
Oct 21 2013, 09:35 PM
|
|
Elite
195 posts Joined: Sep 2006
|
QUOTE(wKkaY @ Oct 21 2013, 08:57 PM) Hmm you might be on to something! Something like this maybe? Mikrotik wiki has a code snippet that can be used together with that: http://wiki.mikrotik.com/wiki/Manual:Scrip...ce_have_changed  CODE :log info "IPv6 Check Start"; :local poolname "pppoev6"; :local intname "ether1-gigabit-master"; :global oldV6; :local newV6; :set newV6 [/ipv6 pool get $poolname prefix]; :if ([ :typeof $oldV6 ] = "nothing") do={ :set oldV6 $newV6 } :if ($newV6 != $oldV6) do={ :log info "Mismatch -- killing old prefix"; :log info "Current -- $newV6"; :log info "Previous -- $oldV6"; :ipv6 nd prefix add autonomous=yes disabled=no interface=$intname on-link=yes preferred-lifetime=0s prefix=$oldV6 valid-lifetime=0s; :ipv6 nd prefix remove [/ipv6 nd prefix find prefix=$oldV6]; :set oldV6 $newV6; } :log info "IPv6 Check Stop"; I was trying to grab the prefix directly from the interface but no luck, kept getting garbage so I ended up pulling from the DHCPv6 client pool instead  ** Updated the if check for the previous IPv6 prefix This post has been edited by rizvanrp: Oct 21 2013, 10:17 PM |
|
|
|
|
|
Oct 21 2013, 10:22 PM
|
|
Senior Member
4,454 posts Joined: Jan 2003
|
This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:40 AM |
|
|
Oct 21 2013, 10:25 PM
Show posts by this member only | IPv6 | Post
#255
|
|
Elite
4,541 posts Joined: Jan 2003 From: BSRPPG51 Access Concentrator
|
QUOTE(Moogle Stiltzkin @ Oct 21 2013, 08:32 PM) what is causing this ? Whos fault is it ? Unifis implementation, or the router firmware which lack support ? No, it is the routerOS problem. QUOTE(Alpha Wolf @ Oct 21 2013, 09:06 PM) As for my setup, the only thing I'm wondering about right now is: Why do I get two different v6 prefixes for my WAN and LAN? Shouldn't they be the same? Also, I can reach my router from the external internet by using both my WAN or LAN v6 IP. |
|
|
Oct 21 2013, 10:30 PM
|
Junior Member
197 posts Joined: Jul 2011
|
QUOTE(Alpha Wolf @ Oct 21 2013, 06:43 PM) Just when I was about to wonder if anyone else was using DD-WRT with IPv6... I guess technically none yet? Hmm, is it possible in the DIR-615 ? the space in DIR-615 is quite limitedIncidentally, I've spent the last few days relentlessly sorting out and getting IPv6 connection working with DD-WRT. It was an IPv6 learning experience for me too as I was completely new to IPv6. I finally have my Asus RT-N66U running on DD-WRT fully working with Unifi's native IPv6 along side 500 and 600 vlan tagging.  Currently DD-WRT has less support for IPv6 compared to other custom firmwares like Tomato and OpenWRT, at least this is according to the web interface of DD-WRT, most of which needs to be manually configure using the command line interface and script files. But being well accustomed to DD-WRT and its extensive features, I wanted this to work. Only the big builds have IPv6 modules included, but with optware and ipkg and lots of patience, it's fully possible. In short, here are the applications I am using: 1) rdisc6 to get ICMPv6 from ISP for the WAN interface. 2) DHCPv6 client to get v6 prefix from ISP. 3) and finally radvd to advertise that obtained prefix out to clients. I also added and configured ip6tables for the v6 firewall. Here are more details on my setup. Note this is a custom web interface page I included using the MyPage feature of DD-WRT for debugging and status purposes. So far it's been running really stable. No point in masking my IP addresses since they are dynamic plus I run a server. » Click to show Spoiler - click again to hide... « |
|
|
Oct 21 2013, 10:49 PM
Show posts by this member only | IPv6 | Post
#257
|
|
Junior Member
263 posts Joined: Mar 2008 From: SS2, Petaling Jaya
|
QUOTE(asellus @ Oct 21 2013, 10:25 PM) Because that's how it works. If your PPPoE dialer supports IPv6, it can get itself its own /64, then another /64 for clients behind the router. Not that different really than a HE.net tunnel. Oh good! So I'm not over pulling a prefix too many or anything like that. I still find it interesting how I can use both my WAN and LAN v6 IP as my public IP. It's like I'm having two public addresses. I guess IPv6 has too many addresses to offer. The way IPv6 works is almost entirely different from IPv4, apparently it's not just as simple as "adding more addresses". I've never tried tunnels as I started straight with native IPv6. QUOTE(zhuoyang @ Oct 21 2013, 10:30 PM) Hmm, is it possible in the DIR-615 ? the space in DIR-615 is quite limited You are only required to enable JFFS support on your router to use ipkg. Then, attach a usb drive to your router and bind mount it to /jffs and poof! Your jffs has the space of your USB drive! You have to change your usb mount path accordingly.CODE mount --bind /mnt/sda1/jffs /jffs |
|
|
Oct 22 2013, 01:04 AM
|
All Stars
31,607 posts Joined: Aug 2010
|
QUOTE(Alpha Wolf @ Oct 21 2013, 06:43 PM) You need to get a copy of the 1.01 firmware first, where DellMalaysia has requested through an email awaiting reply from TM. This is also the reason why I am in search for that firmware. thanks for telling1st day use the unifi after yesterday midnight reset the router, no dc issue let see how it goes ... |
|
|
Oct 22 2013, 10:10 AM
|
Senior Member
578 posts Joined: Jun 2012
|
Just one curious question
If TM never assign a public IPv4 address, will IPv6 will help them to resolve the issue for CCTV or IPCam port forwarding? |
|
|
Oct 22 2013, 10:22 AM
Show posts by this member only | IPv6 | Post
#260
|
Senior Member
3,669 posts Joined: Apr 2006
|
QUOTE(hinamoriamu @ Oct 22 2013, 10:10 AM) Just one curious question Technically, IPv6 could solve the issue, assuming if the router at TM side is capable of IPv6 support.If TM never assign a public IPv4 address, will IPv6 will help them to resolve the issue for CCTV or IPCam port forwarding? This way, you will have the private IPv4 and public IPv6 address. Problem, how do you know if your other end of connection support IPv6 as well? Example, location A supports both IPv4 (Private or Public) and IPv6 (Public) while location B (the one you want to access) can only support IPv4 (Private, NAT-ed). You gonna have issue setting up teredo tunneling etc just to get pseudo IPv6 working.  |
| Change to: |  0.0182sec
 0.62
 6 queries
 GZIP Disabled
Time is now: 1st December 2025 - 01:40 PM |
All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)
Powered by Invision Power Board © 2025 IPS, Inc.