Basicly whats the name in the topic...

I want to bypass just LAN and try to connect and share my screen to smart TV which is on the other subnet, i mean network....what should i do with mikrotik rules or something else ?

That's not a valid scan. Avast is intercepting the nmap scan and reporting open ports, but almost all of them are not on the router .. they are local to the host. The "proxy" ones are self evident. Another example .. tcp/563 is the Avast service itself. Google and see what the others are....

i scan from inside LAN... add action=add-src-to-address-list address-list="port scanners" address-list-timeout=2w chain=input comment="Port scanners to list " protocol=tcp psd=21,3s,3,1 add action=accept chain=input comment="Accept Ping" protocol=icmp add action=accept ...

When i scanned my router with nmap i got this: 25/tcp open smtp 110/tcp open pop3-proxy Avast! anti-virus pop3 proxy (cannot connect to 10.0.0.1) 119/tcp open nntp-proxy Avast! anti-virus NNTP proxy (cannot connect to 10.0.0.1) 143/tcp open imap-proxy Avast! anti-virus IMAP proxy (cannot connect to ...

Sry for bump... I had the same problem today at about 7am.... Aug/09/2018 07:02:03 memory pptp,info TCP connection established from 113.96.223.207 can someone explain to me first what doest this mean since i dont have open vpn here on router...does this mean that someone get into my router/network ?...

I finally got an answer from different section of ISP, and they give me the tech prospect which saying that they are blocking source port 53 from clients in order to maximize security.... So 3 times i was in contact with "some" technical support and they told me they are blocking nothing, ...

is this the proof that dns replay made out on WAN interface

Yes, it is.

Tnx, ISP is telling me that they are not blocking anything, but 4 different client IPs cant receive DNS replay....i guess i will speak with them again.

They should also be logged with some details, so check if packets are going the right way, i.e. via WAN interface to client's IP address. If they do, then router is sending replies back to client correctly. And if they don't arrive, then something must eat them somewhere between you and client. But...

They should also be logged with some details, so check if packets are going the right way, i.e. via WAN interface to client's IP address. If they do, then router is sending replies back to client correctly. And if they don't arrive, then something must eat them somewhere between you and client. But...

It's after packet was routed somewhere. And it will show some you don't need to see, so try to add src-address-type=local as basic filter. In any case, when you send request from outside, you should see both steps logged for response. when i do nslookup google.com on remote DNS client both mangles ...

It's possible to miss things in torch, you can use logging rules instead: /ip firewall mangle add action=log chain=output log-prefix="step1" protocol=udp src-port=53 add action=log chain=postrouting log-prefix="step2" protocol=udp src-port=53 And btw: And one important point - i...

Perhaps unrelated: you have configured static route towards network 192.168.1.0/24 using gateway with address 192.168.85.253. That IP address is member of DHCP address pool you're using. Either the gateway is really using DHCP-assigned address which means it can change in time (I don't see static a...

The funny thing is that im trying to reslove dns query from 3 different ISPs from my country...and the situation is similar....i have RB433, with RouterOS 6.42.6 (i tried with 3 different version, the basic one, the 6.40.8, and this one - the newest)...called 2 times my ISP to ask them if they are b...

Another idea for using torch: when you observe incoming DNS request at your WAN port, do you see a DNS request originating RB device being targeted at either of DNS forwarders (8.8.8.8 or 8.8.4.4)? Do you see reply coming from those? Unless reply to your own DNS request is cached at router's DNS se...

export only shows the static configuration elements, to see the dynamically created ones, you need to use print, and you can only print a single configuration tree leaf at a time. So post also /ip route print , and in order that it would make sense, you'll have to obfuscate only the gateway IPs; th...

Dynamic entries don't get into export, you can only see those using print command. Is there anything weird if you issue command "/ip firewall filter print"? Nothing.... just this from the code 0 X ;;; accept DNS UDP chain=input action=accept protocol=udp port=53 log=no log-prefix="&q...

Here is the code, but there is like nothing...i do have some dynamic routes tho, dont know why that didnt dispay in the export command.... BTW, i did everything on fresh new clean RouterOS without any configuration (except that DNS settings, static DNS record, and DHCP client so i can get internet a...

No rules in firewall mean everything is permitted. This is a) a very bad idea (to put it softly) on a machine with a public address on it, and b) an indication that the issue must be within routing or the DNS process itself. Well i did system reset-config and did just a basic setup from scratch, an...

...what firewall rule should i apply ? And does the place of firewall rule matter ? Yes, the order of the rules does matter, so without knowledge of the overall configuration, no one can suggest you what rule to add or which rule to remove or modify. So again, to get a useful advice, follow the ins...

Yea i used the torch exactly like that and there is no src-adr thats my WAN ip and dst-adr thats remote DNS client.... If you see packets in both directions (on one row 53 is src-port and on another row 53 is dst-port), then the ISP is filtering the responses. If you only see 53 as dst-port but neve...

If the torch doesn't show the responses, there is no need to talk to ISP - if ISP was blocking it, you would see the responses in torch but they wouldn't get through the ISP network to the asking PC. So follow the instructions in my automatic signature, it must be something in your firewall setting...

Are you sure your ISP is not filtering DNS requests targeted at their clients? Use torch tool and check if there are any packets targeting your public IP TCP/UDP port 53 coming to your WAN interface ... OK, I see that you mentioned filter counters going up. However, that doesn't rule out IPS filter...

Sindy tnx for the answer, and i get that totally...awesome explanation of how dns works tho....but... Im losing all the hope after all of these days... So basically i set up everything, tried every solution possible (all kind of firewall rules, different routerOS, change every little thing in DNS co...

I'm reading some topics here and someone said that router should not be in DNS "client" mode but in DNS Server mode....how can i check that, when is he operating as a client and when as a server ?

Ok sorry for bumping but basically i check "allow remote requests" and added public IP address of that mikrotik router as dns server for "outside" computer and he cant resolve the DNS....im using RouterOS v6.40.8 ... I even made a firewall rule, chain - dstnat, protocol - udp, d...

Ok sorry for bumping but basically i check "allow remote requests" and added public IP address of that mikrotik router as dns server for "outside" computer and he cant resolve the DNS....im using RouterOS v6.40.8 ... I even made a firewall rule, chain - dstnat, protocol - udp, ds...

Hello everyone, im new here and i just have one question, maybe its a little tricky but im so desperate to find the solution So the thing is that im trying through CLI to find the bytes that one active PPTP VPN connection generated so i can use api to collect that integer, but i can see in older ver...