I surely hope not!Great work.
I'm hoping to see 6.36.x in bugfix soon
Can't you fix that by turning off fastpath?We are still on 6.34.6 as 6.35 and 6.36 broke our routing-marks for multi-wan setups...
Is this issue fixed again?
I have a setup running with a 4-WAN config and did not experience any problems while running 6.36Can't you fix that by turning off fastpath?We are still on 6.34.6 as 6.35 and 6.36 broke our routing-marks for multi-wan setups...
Is this issue fixed again?
AFAIK you will have to wait till RouterOS v7, all newest drivers require newest linux kernel.Hi guys,
I still miss Hardware Support for Supermicro SYS-5018A-MLTN4 with C2000 SoC I354 Quad GbE controllers (MACs)....
Please let me know if there is any Change in the next Releases.
Thx
Steve
If disabling FastTrack does not resolve this issue, please send supout.rif file to support@mikrotik.comWe are still on 6.34.6 as 6.35 and 6.36 broke our routing-marks for multi-wan setups...
Is this issue fixed again?
AFAIK you will have to wait till RouterOS v7, all newest drivers require newest linux kernel.Hi guys,
I still miss Hardware Support for Supermicro SYS-5018A-MLTN4 with C2000 SoC I354 Quad GbE controllers (MACs)....
Please let me know if there is any Change in the next Releases.
Thx
Steve
fyi - tested l2tp-server on CHR v6.36.3 - works fine - maybe you should elaborate your problem.Problems with server l2tp!!!
The moment you manipulate the packets (change tcp MSS) you cannot "bypass" them any longer, so there's no other way to go... whether it will work or not, it will depend on the network being suitable for unclamped TCP packets or not.Fast path allows to forward packets without additional processing in the Linux kernel. It improves forwarding speeds significantly.
Correction. CAP client does not work on Winbox 3.5 and ROS6.36.3. Bugfix 6.34.6. does not work with wireless-rep package. I have not tested other versions.ver6.36.3 Cap client does not work. Certificates is marked in red. Returned to 6.36.2, everything works Fine.
What version did you upgrade from?i've upgraded my RB433AH to v6.36.3 [current] is released, and know i see that the ports are on different group.
ether1 PoE know is ether 2, ether2 know is ether1, just ether 3 is same. The new version did that or???
Thanks
{
:put "name - default-name"
:foreach eIf in=[/interface ethernet find] do={
:put ([/interface ethernet get $eIf name] . " - " . [/interface ethernet get $eIf default-name])
}
}
It's likely a stuck SA on either side, or an incorrect configuration. Reboot both sides of the tunnel when changing enc or auth.Hi,
i found a problem when using IPsec. When i set Proposal Auth. Algorithm sha256 option. SAs cert. are created but communication LAN to LAN is not working. When i set different Auth. Algorithm it works fine.
Details:
ROS 6.34.6 (mipsbe) and 6.36.3 (mipsbe) where tested.
HW: RB951-2n and RB951G-2HnD
I should have finished the thread before replying...after reset all good
Thanks
TNX for your interest,It's likely a stuck SA on either side, or an incorrect configuration. Reboot both sides of the tunnel when changing enc or auth.Hi,
i found a problem when using IPsec. When i set Proposal Auth. Algorithm sha256 option. SAs cert. are created but communication LAN to LAN is not working. When i set different Auth. Algorithm it works fine.
Details:
ROS 6.34.6 (mipsbe) and 6.36.3 (mipsbe) where tested.
HW: RB951-2n and RB951G-2HnD
I have 37 Mikrotiks all using aes256cbc & sha256 with no issues.
Different router manufacturer, or different router from MikroTik?When i now try it with different HW, it works ok. Strange...