My last question is - is there a way I could make the sfp+ a trunk port without changing my current config?
I use TPLINK eap245 and 660 for my home wifi for example.
add 10.10.0.68/24 interface=ether1BR1
/interface list member
add interface=ether1BR1 list=BASIS
I can only find basic VLAN setups in that link. I am trying to bridge multiple interfaces together. Have you seen my other post?
How many mipsbe devices come with mentioned wireless chip and 256MB RAM? Not to mention that mipsbe CPUs are mostly too weak even to maintain full-speed ac wireless.Supported v7.1rc4 Wave2 for MIPSBE?
Also 100Mbps full duplex works without any problem (which also requires the 4 pairs right?)
Do pray tell which L3 limited features could the Switch do with RoS7, that would offload the router..........
Many think electronics do not age ...Sure gadgets do get aged
I removed eht9 from the non-existant bridge and this make it.
With v7 of RoS some Tik switches will have the capability to do NEAR line speed forwarding … unfortunately the switch then OP SELECTED CANNOT DO IT.
Not impossible. But probability of it happen is 1 divided by 2 to the power of (N-1) (where N is number of active torrent peers). E.g. if number of active torrent peers is 11, then possibility of only one ISP line being used is around one in a thousand.It seems impossible ...
Circular reference: vlan1 marked as a tagged interface of bridge1, but bridge1 is the interface under vlan1.
... is hard to think something that Router generate for bad purpose...
Oh suggest something like 22 will work, pulling any number out of a hat........ ;-p :
add address=10.18.100.1/22 comment=Guest interface=ether3 network=10.18.100.0
add action=dst-nat chain=dstnat comment=SSH dst-port=22 protocol=tcp to-addresses=192.168.2.10 to-ports=22 in-interface-list=WAN
It's RouterOS heh.
No, it wouldn't. ROS doesn't downgrade unless explicitly instructed to do so.With a restart it downgrades. I used the button ‘downgrade’ in /system/packages to initiate the process. I’m not sure if a normal reboot would have done the trick as well.
it is fixed after upgrading.6.45.7 at least I hope?
I don't have any tools to read exported ".backup" file.Do a "/export" to file and search for it.
He said his WAN network was 10.1.1.2/30 ...If that is his WAN connection yes ...
Per OP's initial post, there's already a masquerade rule which should take care of source NAT of that particular connection as well. So no need to add a specific one.
You need to source NAT that connection
If Mikrotik would me let escape the messed up Beta.... you'll have to bite a bullet and get out of this beta mess.
I just thought of a possible solution.
Please, can someone explain why I have yesterday warning level  and now "Your warning level: "???