This was a hard crash due to a kernel failure and the watchdog caught it.
Power was probably fine, just a bug somewhere that caused the kernel to
crash. I'd take this opportunity to think about upgrading to another
version which may have that crash fixed.
Judd
On Thu, Mar 2, 2017 at 1:13 PM,
On Netonix set each port to E or empty as I am concerned. For each vlan on
a particular port click to change it to T. Then on your trunk ports check
the "trunk port / allowed vlans" and specify 1-4095 or whatever the limit
is. Then the port going to your router can see all tagged traffic. Make
I had the same problem on a 3011. Had to netboot and reinstall from
backups. Thankfully that worked and thankfully it was here on site. Don't
upgrade to 6.38 remote.
On Jan 7, 2017 12:04 AM, "Daniel Biland via Mikrotik-users" <
mikrotik-users@wispa.org> wrote:
> today i wanted to make a easy
Try L2TP? Maybe they are filtering something.
On Dec 15, 2016 12:52 PM, "Johnathan Penberthy via Mikrotik-users" <
mikrotik-users@wispa.org> wrote:
> I have a really stubborn ISP that helps connect two parts of my network
> together on Fiber, and won’t or can’t give me a private Ethernet
>
In your routes to the 3 different wan networks:
/ip route
add check-gateway=ping distance=1 dst-address=10.10.0.0/16
gateway=10.81.35.193 pref-src=10.81.35.1
Set a preferred source (pref-src) to the public IP address on your WAN
ports and have check-gateway set to ping. If the remote gateway
Change your preferred source on the gateway check and have it ping the
other side or something on the internet. No need to go crazy on netwatch.
On Sep 8, 2016 7:35 PM, "OWS Optimum Wireless via Mikrotik-users" <
mikrotik-users@wispa.org> wrote:
> Hello.
>
> I'm trying to create a fail-over
