New Things….

I am excited to announce some new things I have been working on.  Over the past several months I have been starting several new projects. As a result, I have been needing to separate some things between the commercial side and my own interests so we things can grow and expand.

This weekend I have re-launched the j2sw.com blog at https://blog.j2sw.com . This blog was created to give more attention to my passions such as xISP topics and technology in general.  The majority of blog posts and writings will transition to being on the blog.j2sw.com.  The MTIN blog (https://www.mtin.net/blog) will mirror much of the content as this blog has been running for over 10 years. As time progresses the MTIN blog will become more of a corporate blog.  Things such as new products MTIN is doing, specials, and the like will appear on that side of the house

Other projects I am a part of are listed on the main page of https://j2sw.com/  . The one growing the most is the podcast. Look for more and more content coming for the blog. As soon as I can figure out how to transition the blog URL I will move the primary posts to the blog.j2sw site. Make sure to subscribe to the RSS feed, the e-mail feed, or your favorite page watcher.

Onward and Upward!!

PodCast: Mum 2019 chat with JJ & Eric

Sat down With JJ Mcgrath and Eric Sooter at the Mikrotik User meeting in Autin for a little “routerside chat” about the WISP industry. #routinglight #routingrf #bendingpackets #podcast

MikroTik Router as a Vultr host

Recently I spun up a Mikrotik instance under Vultr for the purpose of doing some v6 testing. I was running into some problems with getting IPV6 to route properly. Vultr has IPV6 setup on their side to auto configure a gateway, etc. when it comes to IPV6. They are expecting a host, not a router. Why is his a problem?

The RFC states that nodes that act as routers are NOT to use SLAAC for IPv6 address configuration. In other words, routers that derived their interface IPv6 address from SLAAC cannot act as routers on that segment. This is a pretty hard set in stone thing when it comes to the RFC.

So how do we get around this in this instance? Go to IPV6…settings and turn off IPV6 forward.

IPv6 will start working at this point. The catch is, you won’t see neither address nor default route anywhere. It’s there, but it’s hidden. If you try to ping some external address, it will work.