Shaun's Blog

Well, I am starting to get frustrated with Meraki and their MX appliances.  They have been promising to add IPv6 support to them for a while but they have yet to add it.  This is an issue since most cell providers only offer IPv6 address to their phones & hotspots.  This means that I am not able to connect to work via VPN when I am and about.  Also means that I’m unable to connect to home via VPN and also check my personal site’s IPv6 address (I have a MX64 at home that I got for free).  I most definitely will be switching back to Ubiquiti at home once my license has expired for my Meraki gear.

Well,

My web server sending people to the wrong domain seems to only occur at home.  I have no clue what is causing it but it is rather frustrating

Well,

I couldn’t get VestaCP to work properly with Nextcloud so I am back to Virtualmin.  Problem is, some domains don’t end up going to the correct site although they not do this in all browsers.

Well, I was reading a news article today about how Charter/Spectrum is telling the FTC that Title II is making it so they don’t invest in their network but they are telling investors that it isn’t causing any issues.  Also had a link in the article saying that every user on their 60Mbps tier will be upgraded to 100Mbps, the problem I have with this is they are not increasing the upload speed.  Still a crappy 5Mbps, its taking me forever to complete my first backup with CrashPlan Small Business due to this.

Been playing around with a RouterOS VM a bit at work (wanted to try out “The Dude” at work to see if I can use it).  I think converting from EdgeOS to RouterOS is going to be a bit of work, but I’ll pull a config file from my EdgeRouter-X and just get started.  I mean, its all I can really do 😉

Well, my Ubiquiti EdgeRouter-X and UniFi AP Lite AC combo stopped working.  Picked up a TP-Link Archer C7 to get us through until I could troubleshoot the Ubiquiti gear, decided to replace them with a MikroTik hAP ac after reading that Ubiquiti gear likes to die after around 18 months.  Definitely not what I need at home.  Configuring the MikroTik will be more work for me then I’m used to, but performance should be as good as or better than the Ubiquiti combo.  I should also be able to keep the EdgeRouter-X around as a 5 port gigabit switch if I want to, powered by the hAP ac (it comes with a 24V wall wart and supports PoE out on port 5).  I’m hoping I can easily get IPv6 working on the hAP ac, since it was a PITA on my EdgeRouter-X.

Well,

My phone got its full Alexa integration today.  So far its pretty neat to use.  Adjusted the temp on my home thermostat a couple of times to try it out and verify that worked.  Also got in the beta test of the skill for the Monero mining pool I’m in, that is awesome too.  Also got my code for my free echo dots last week, they arrived today.  I’ll get them setup tonight and hopefully not confuse myself with saying the key word (thankfully you can update it on the echo devices, can’t on my phone).  I’m planning on putting one upstairs and one in my bedroom, and eventually getting a smart outlet for my wife’s nightstand lamp (and possible other lamps too).

So, I decided to finally get my EdgeOS HE.net IPv6 tunnel howto done, although it should work in VyOS or Vyatta as well.  This is how I have it setup and it is working for me, there are probably other ways to set it up that will work.  They may also be more efficient too, but I don’t want to break a working setup.

Easiest way to do this is to SSH into your EdgeOS device.  Then type the following commands to setup your firewall.  Change WAN_LOCAL to your IPv4 local firewall rule, and change rule 15 to place the new HE.net IPv4 firewall rule as the second in your list.

Now we create the tunnel to HE.net.  Replace 2001:470:xxxx:482::2/64 with your Client IPv6 address, 184.105.253.14 with your Server IPv4 address.

Next, we need to assign an IPv6 to our internal interface.  On my EdgeRouter X, this is switch0.  Other devices could be eth1, eth2, etc…  Don’t forget to change 2001:470:xxxx:482::1/64 to an IP in your Routed /64 IPv6 Prefix, and 2001:470:xxxx:482::/64 to your Router /64 IPv6 Prefix.

Next we set the IPv6 next hop.  Again, don’t forget to change 2001:470:xxxx:482:: for your Routed /64 Prefix.

Now, we setup the DHCPv6 server.  Again, don’t forget to change 2001:470:xxxx:482:: for your Routed /64 Prefix.

Finally, we set the EdgeOS device to update DNS-O-Matic.  I use this to allow me to update my OpenDNS & HE.net tunnel info at the same time.

Now commit and save your configuration, and issue a ping6 google.com.  You should see valid results, no reboot your client and ping Google’s IPv6 address (this will vary based on your OS, Windows is ping -6 google.com).

Well, I again have a dual stack network at home.  IPv4 from Charter and IPv6 through a Hurricane Electric tunnel.  I do have to say it was not as easy to setup on my EdgeRouter X as it was in pfSense but I figured it out.  I will be writing a tutorial on how I did it in a little while since I figure other people might like to know 😀