Re: [Mikrotik] HE Tunnel Broker Setup

On Wed, 2015-07-15 at 14:08 -0500, Christopher Tyler wrote: Just putting this out there for anyone else that might stumble across this thread. It's an issue on at least Debian (and it's derivatives like Ubuntu) that supposedly has been addressed upstream, but has yet to make it into the

Re: [Mikrotik] HE Tunnel Broker Setup

Setting everything manually.. $ ip address show eth0 inet6 2001:470::1:4216:7eff:fead:286c/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4216:7eff:fead:286c/64 scope link valid_lft forever preferred_lft forever $ ip -6 route show

Re: [Mikrotik] HE Tunnel Broker Setup

What does traceroute show? On 7/15/2015 2:28 PM, Christopher Tyler wrote: Setting everything manually.. $ ip address show eth0 inet6 2001:470::1:4216:7eff:fead:286c/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4216:7eff:fead:286c/64 scope link

Re: [Mikrotik] HE Tunnel Broker Setup

On Wed, 2015-07-15 at 13:48 -0400, Scott Reed wrote: Default route is from the link local address, not the global address. That is normal for some OS. Specifically, Linux will do that every time (or has with my RedHat varieties). Here's my pbx: default via fe80::260:e0ff:fe44:2a06 dev eth0

Re: [Mikrotik] HE Tunnel Broker Setup

Default route is from the link local address, not the global address. Last line in route information. On 7/15/2015 1:44 PM, Christopher Tyler wrote: I'm just now dipping my toes into the IPv6 water and I've hit a wall... First off, I followed the manual at

Re: [Mikrotik] HE Tunnel Broker Setup

Okay, that's weird, traceroute appears to work just fine... $ traceroute6 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::), 30 hops max, 80 byte packets 1 2001:470::1::1 (2001:470:389e:1::1) 0.609 ms 0.582 ms 0.553 ms 2

[Mikrotik] HE Tunnel Broker Setup

I'm just now dipping my toes into the IPv6 water and I've hit a wall... First off, I followed the manual at http://wiki.mikrotik.com/wiki/Manual:My_First_IPv6_Network The tunnel is working fine and from the router at least everything works fine. I can ping 2001:4860:4860:: and other sites.

Re: [Mikrotik] HE Tunnel Broker Setup

Pinging 2607:f8b0:400d:c04::93 works fine from the router. From the PC I can ping my side of the tunnel but not the remote side. From the PC to any IP on the router, pings work fine. I only get timeout/Hop Limit on IP's past the router. -- Christopher Tyler MTCRE/MTCNA/MTCTCE/MTCWE Total

Re: [Mikrotik] HE Tunnel Broker Setup

Just putting this out there for anyone else that might stumble across this thread. It's an issue on at least Debian (and it's derivatives like Ubuntu) that supposedly has been addressed upstream, but has yet to make it into the downstream packages. The workaround is to run this command as

Re: [Mikrotik] HE Tunnel Broker Setup

part -- An HTML attachment was scrubbed... URL: http://mail.butchevans.com/pipermail/mikrotik/attachments/20150715/034b5249/attachment.html ___ Mikrotik mailing list Mikrotik@mail.butchevans.com http://mail.butchevans.com/mailman/listinfo

Re: [Mikrotik] HE Tunnel Broker Setup

Tried on my MAC and it works fine. This is an issue with my PC not the Tik or the he tunnel. Thanks for the assistance I really appreciate it. -- Christopher Tyler MTCRE/MTCNA/MTCTCE/MTCWE Total Highspeed Internet Services 417.851.1107 - Original Message - From: Christopher Tyler

Re: [Mikrotik] HE Tunnel Broker Setup

-- Jonathan Wright.. # You never know. You may see something you like. $ cat /dev/random # j...@than.io # @jon_than_ # http://jon.than.io​ -- next part -- An HTML attachment was scrubbed... URL: http://mail.butchevans.com/pipermail/mikrotik/attachments/20150715/034b5249