Microtik port forwarding

Spent too much time configuringĀ port forwarding (RDP) on my (Microtik) RouterBoard 751G-2HnD. The solution, as usual, was buried in a May 2014 forum post. There needs to be TWO (2) NAT rules enabled; i.e. to forward traffic to/fro the router/server.

In this case, 192.0.78.13 and 10.0.0.254 refers to the router’s WAN and LAN IPs respectively, and 10.0.0.243 is the intended recipient of my RDP traffic.

[admin@751g2hnd] > /ip firewall nat print
1 chain=dstnat action=dst-nat to-addresses=10.0.0.243 to-ports=3389 protocol=tcp dst-address=192.0.78.13 dst-port=3389 log=no log-prefix=””

2 chain=srcnat action=src-nat to-addresses=10.0.0.254 to-ports=3389 protocol=tcp dst-address=10.0.0.243 dst-port=3389 log=no log-prefix=””

Many thanks to The Digital Doctor (http://forums.ncix.com/forums/topic.php?id=2662521)!!

Advertisements

InnoDB transactions

Yesterday I updated the date column of an entire table meant for its subset only. The solution to this mistake was to recover from daily mysqldump, and filling in the gaps that were, thankfully, able to be filled in.

Writing in 2010, the author of the answer said:-

When something goes wrong, the only restoration option available is to reconstruct the data from a backup (providing one exists).

Here are two answers that I found useful; i.e., Stack Overflow, the gift(s) that keeps on giving:

http://stackoverflow.com/questions/2950676/difference-between-set-autocommit-1-and-start-transaction-in-mysql-have-i-misse
http://stackoverflow.com/questions/5727827/update-one-mysql-table-with-values-from-another