Archive for the ‘networking’ Category

Alexa

Monday, July 17th, 2017

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).

EdgeOS HE.net IPv6 Tunnel

Monday, June 22nd, 2015

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).

IPv6

Thursday, June 11th, 2015

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 😀