We have identities in this format AAA-BBB-CC-xxxxxx We would like to capture the first three portions (AAA-BBB-CC) into a variable Is there a way to pull via regex? I think ".*-" should return what we need. But I can't find out how to set it to a variable I've gotten this far: :local ident...

Hi,
If you netinstall a mikrotik and include an admin password in the configure script which would be come the default configuration, is the configure script encrypted? Where is the configure script stored on the device?

Thanks

FYI, it was caused by what the provider called an application level filter being applied to our traffic by the provider as an oversight. I'm guessing an ids of some type. All working as it should now. Thanks for the help in determining the issue.

I was traveling yesterday, but I no longer think this is an issue with dst-nat and may be an issue with the upstream provider. Will update later.

Sorry for the long post. Here are some logs taken from the client and the CHR I am attempting to forward through. I logged for both forwarding 8122 > 22 and 22 > 22. Forwarding 22 > 22 successfully connects. Log from client system when forwarding port 8122 to port 22 08:44:09 firewall,info output: i...

Yeah, I can't see a problem either. I have tested from multiple remote locations all of which connect to ether2-Wan. I can see the SYN packet on ether2-Wan in the logs. If I change the nat rule from this: add action=dst-nat chain=dstnat comment="PWC SSH" dst-address=aaa.bb.ccc.218 \ dst-po...

Anyone have any other ideas? Is there some other info that will help?

Thanks

Bump due to forum issue yesterday

Here it is. # may/16/2019 08:51:21 by RouterOS 6.44.3 # software id = # # # /interface bridge add name=lo /interface ethernet set [ find default-name=ether1 ] disable-running-check=no name=ether1-Lan set [ find default-name=ether2 ] disable-running-check=no name=ether2-Wan set [ find default-name=et...

Hi, thanks for the replies so far. Here is some more info: Definitely a public ip and the port is open. I have rules allowing established/ related packets, etc. This seems to be a strange issue in this case. I haven't done packet capture yet, but I can see the SYN packet log in the tik on port 8122,...

I am attempting to forward ssh connections that connect to a Wan side address on one interface at port 8122 and forward to address 172.21.2.3 port 22. If I change the rule to forward xxx.xxx.xxx.xxx port 22 to 172.21.2.3 port 22, the connection is successful: add action=dst-nat chain=dstnat dst-addr...