Ta!Hi, I'm not Dave but:Dave does this script replace your old 'blacklistUpdate' script that was scheduled? Must I just schedule this new script as per before?
Yes and Yes :)
I also prefer Winbox and the command line via ssh or a terminal session.well, I am sure I am not the only one preferring winbox above all other, with CLI in case winbox won't work.
No into the actual router, either via winbox or ssh.logs in where? hotspot? ppp?
So which one is it?I use no-ip.com and here is the script for that:
# Dynamic DNS Update / Simple Edition # Written by Sam Norris, ChangeIP.com # Copyright ChangeIP.com 2009 # For support send mail to Support@ChangeIP.com #
http://download.mikrotik.com/all_packages-x86-4.5.zipDoes anybody have any links to x86 version 4.5? I upgraded this from 3.30, so I've nothing in the x86 4.x tree.
I'm not an ISP but I use Mikrotik as LAN routers for my customers and I've experienced this problem. However not since moving away to another DNS (either Google or the ISP DNS).How many people having this problem are ISPs?
Poke oh who? :-)Works great to proxy-redirect block.opendns.com to http://www.disney.com. Those trying to surf for hardcore smut will end up getting Pochohontas... :D
http://18.104.22.168/all_packages-mipsbe-3.24.zipplease, is there anybody, who could tell me, where I can download version 3.24 and the right way how to downgrade???
From what I know, you need a username to authenticate and then there's a level of encryption (granted not 256 AES or similar).Depends on what you need out of the connection. L2TP does not provide confidentiality
Probably the opposite. L2TP is pretty easy with Mikrotik and why add another level of complication if you don't have to?Why use L2TP when I can go just IPsec? On Debian/Ubuntu-forums they all say that if you can, just go with IPsec without L2TP. Does the same advice go for Mikrotik -> Mikrotik?
You probably meant protocol UDP so note to Muldahir, change the dst-nat rule to reflect this.
And then transparently redirect all DNS requests to the router itself:
/ip firewall nat add chain=dstnat protocol=tcp dst-port=53 in-interface=local action=redirect to-ports=53
That's a bit harsh!Hey don't let that guy charge you from the above message unless you want it really really bad. :-D
Thanks very much, it certainly does indeed.The issue is the virtual Sun Java's VirtualBox Network Interface (similiar to VMWare).
Disable that network interface, and it works perfectly!
This works partially on my Win7 RC1you could try to right-click it and choose 'run as administrator
Dude, loosen those tight panties of yours and just send firstname.lastname@example.org an email.
AGAIN an other point of view... In a community open by support team, is expected the participation of them and the use of forum as an way of obtain support from support team...
Yes that is my experience. Had me fooled for some time, I've learnt to trust winbox over the years and never thought to check via ssh or terminal.in Winbox? so, all is working, you just cannot see it in Winbox?
Mark, this is done easily with simple static routing.There should be a way to say which tunnels are allowed to acces which other tunnels...
You can't say I didn't tell you before!we found a bug and fixed it
Say again? I thought the whole idea was to keep the channels clean. So first channel 1, then 6 then 11 and then back to 1?same SSID, same frequency band
Ah, so there's a secret conversion needed!You have to convert your SSH keys from linux to PuTTY format using the tool included with putty tools.
Try this;has anyone found some info from Mikrotik that indicates what User Service Tag means??
I agree. This is what is so frustrating.The WOL packet is almost to simple to get wrong.
What are you smoking?Well - two more primaries updated and operational - the clock date field is hilarious though - check it out.
Please let me know what is up with that??
I had to downgrade to 3.13 and then upgrade to 3.26 to make it all work.First attempt at an upgrade to 3.26 from 3.25 on a x86 box did not succeed.
working like a bomb here in South Africa. The stream is transferring on average 70kbps.we are testing upstream bandwid streaming now anybody can access mms://22.214.171.124:1234 :)
Could please elaborate? I know this not related to Mikrotik but it is a necessary requirement nowadays.For a more comprehensive solution, we use a separate appliance between the Mikrotik and the LAN to implement very detailed Internet usage controls.
I suspect this may have actually made it worse. One of the gripes was that a sub menu list was too long to view in a small screen. Now whilst the top level menu options are fewer, the sub-menus are now way too long.*) made WinBox work better on smaller screens;
thenI install RouterOs v2.9.27 on a machine with 2 NIC.
thenHmm.. question, why are you installing v.2.9.27?
Busted!the version is not the issue right now
You probably need a src-nat (masquerade) rule for this to happen.
If I get this to work, how will ether2 understand that it needs to go to ether1 to access the internet? Do I need to bridge ether1 and ether2?
For sure it's working but I've only been successful with the changeip service. If you're trying to use dyndns.org or something similar then perhaps it wont work properly.Is anyone using '/tool dns-update' successfully on Mikrotik 3.22?
This may sound like an obvious question but why don't you just use routing? Why the need for the bridge?Hmmm...not sure if that's possible either. Anyway thanks for info!
Are there other ways around to pass L2TP broadcast traffic on to the LAN side bridge?
As does the RB433.well, not all RB400 series have switch chip, but these boards have - RB450, RB493