Sorry, forgot to make that point clear: yes, MIMO (2x2) should be used.
(Otherwise it would be a bit trivial
NO, please don't do this. If i want an analyzer i'd buy one. If i want a router i dont't want it to do other tings than routing! (or at least very similar things)Up!
I think his is VERY interesting for ALL user.
i'd guess one will see different distances only, when exporting routes from one routing protocol into another.
What I am missing is some information in ROS what metrices
my routes actually have.
but i would select PtP-interface type whenever possible, cause it saves the router from the whole DR-/BDR-selection work.There is no need to set network type on each interface running OSPF unless you need specific network type.
I see. Are there many VPN-Clients using the same Protocol e.g. IPSec? Does this work too?I run both IPSEC and PPTP through an MT with src-nat defined and it works fine using UDP encapsulation for the ESP packets.
Which Linksys (WRT?) reaches > 20 Mbit througput? Never heard of such data rates.I’m completely stupefied by the cheapo $50.00 linksys router getting 25 to 30 mbps with the crappie hardware and tiny cpu’s and then the router boards strain to get this speed
Last year we tried SBE T3/E3 cards but they didn't work with Router OS.SBE T1s are supported.. (DS3 as well)
Don't do this! One radio for each antenna is a must for professional use.I've read many topics where people "split" one AP with omni- antena to 3 or 4 sectors
add chain=dstnat in-interface=<lan> src-address=!<other-mt-ip> dst-address=!<local-net> protocol=tcp dst-port=80 action=redirect to-ports=3128
you're right but it could be done already, e.g:A facility similar to that of IOS which allows piping CLI output through a filter.
add chain=dstnat in-interface=lan protocol=tcp dst-port=53 action=redirect to-ports=53 add chain=dstnat in-interface=lan protocol=udp dst-port=53 action=redirect to-ports=53
what kind of notebook, radio and OS is meant?...
im using my laptop near the MT router 5 meters only
/ip firewall filter add chain=input protocol=tcp dst-port=22 limit=1/10s,2 action=accept comment="Accept limited SSH" disabled=no add chain=input protocol=tcp dst-port=22 action=drop comment="Drop excess SSH" disabled=no
10:03:57 ipsec,ike,info phase 1 negotiation timed out
after installation "wireless-legacy" and "wireless" both are showing up as "wireless". only the nstreme and some other features are not available in the winbox with wireless-legacy.It is wireless, not wireless-legacy.
it would be even more interesting, if someone is doing this by using two (or more) mt systems and VRRP.anybody worked with mikrotik and multihoming bgp through 2 providers for seamless failover ?
I am sure people have used it for keeping it up and running.
did you load by chance the wireless-legacy package or both wireless packages. for nstreme only wireles package has to be used.Came with 2.8.20, when I did not see it I tried 2.8.21.
i wouldn't call them junk, but doing bandwith or performance tests it's always important to know about hardware issues....
So 3COM nics are junk, Realtek nics are junk and I need to build up a couple of $400 boxes just to test if my hardware is a problem?
you are right, i tried the winbox, terminal is of course working.
how did you try it with Tab button? Maybe DND settings are incorrect in your router. Try, for example:
thanks, that sounds good to me!of course this is a cheap workaround and mikrotik will work on a solution in upcoming versions
/ip firewall src-nat add src-address=192.168.1.0/24 action=nat to-dst-address=xxx.yyy.1.1-xxx.yyy.1.15
i am not sure. does it mean i can resolve a dns name in a script? does it mean too, i could configure dns-name-based vpn-connections only by scripting? (or can i put the command into the ip-address field?)Doesn't it say you something? :)
:put [:resolve www.example.com]
i tried this of course. all i got is an error, stating a non zero ip-address is needed. tried with pptp and ip-tunnel.have you tried to enter a DNS name and, before accepting this, press Tab button?
in-interface=pppoe dst-address=:80 protocol=tcp action=redirect to-dst-address=192.168.255.10 to-dst-port=80
until now -- nothing. we are counting ip-volume;-)ok many thanks, I did it ands it seems it works ok.
Do you also have people using p2p on your network? what do you do with them?
search for "MTU" in the forum, there are many answers (adapting MTU, MRU and MSS)i have a problem with the PPPoE users they cannot surf some sites
yes, right, but i didn't say to change everything from ip-addresses to dns-names, only to have the option to use dns-names too.This is unsecure...