Yahoo Search Busca da Web

Resultado da Busca

  1. 10 de mai. de 2024 · This example uses the MikroTik default of 192.168.88.0/24 for the LAN — with the router as .1 — and the nearby 192.168.77.0/24 subnet for WireGuard. Although port 13231 seems popular for WireGuard, there's nothing about the protocol that requires it. I prefer to put it somewhere random, making it harder for bots to target.

  2. 19 de mai. de 2024 · I can reach the web-server from 192.168.0.0 but can't from internet. Tho if I try to connect to my public ip it directs me to mikrotik web-interface on port 80. If I change the port of mikrotik web-interface to 8888 or disable it, I still can't reach my web-server. Disabling all default firewall filters changing nothing.

  3. 7 de mai. de 2024 · So firewall can act on both varieties of packets similarly (as long as the matcher part of rules inspects src-* fields). You may want to study packet flow. It's dense, but after you get it, it's rewarding. Note: I'm linking documents from older (wiki-style, accessible via https://wiki.mikrotik.com//wiki/) MT

  4. Há 2 dias · MikroTik Neighbor Discovery Protocol: 5683: Yes: Constrained Application Protocol (CoAP) 5684: Yes: Constrained Application Protocol Secure (CoAPs) 5693: Unofficial: Nagios Cross Platform Agent (NCPA) 5701: Unofficial: Hazelcast default communication port: 5718: Unofficial: Microsoft DPM Data Channel (with the agent coordinator) 5719 ...

  5. 8 de mai. de 2024 · Tried blowing it all away with the most basic of settings, single no-vlan network, ensuring a firewall rule for udp on 546 from src fe80::/10 but still just stuck 'searching'. I am only configured for IPoE (all PPP config deleted) and the portal shows connection by DHCP, with both my /32 and /56 listed.

  6. Há 4 dias · Last visit was: Wed May 29, 2024 11:31 am. It is currently Wed May 29, 2024 11:31 am

  7. Há 5 dias · Since the MikroTik forum doesn't have a chat function, you are welcome to send updates to me via the local Forum here instead. Until these lacunae are filled, the above solutions may suggest solutions to new problems you encounter: Try a "reset" on the configuration item. Try to "remove" it entirely, if you aren't using that feature of RouterOS.