unfortunately, no. not nowWill there be an x86_64 version?
for bigger available RAM?I am satisfied with the 32 bit version. Why would you need a different one ? Thanks.
also, won't 64 instructions help to manage ipv6 addresses a bit faster? %)
unfortunately, no. not nowWill there be an x86_64 version?
for bigger available RAM?I am satisfied with the 32 bit version. Why would you need a different one ? Thanks.
well, it's there. next to rc2 not in 'Downloads' but in 'try development version' of your AccountWHere can I download ros v 6 rc3?(I have enabled account on mikrotik.com to download prerelease version, but cant see it in download section.)
Thanks...I found...well, it's there. next to rc2 not in 'Downloads' but in 'try development version' of your AccountWHere can I download ros v 6 rc3?(I have enabled account on mikrotik.com to download prerelease version, but cant see it in download section.)
unfortunately, no. not nowWill there be an x86_64 version?
for bigger available RAM?I am satisfied with the 32 bit version. Why would you need a different one ? Thanks.
also, won't 64 instructions help to manage ipv6 addresses a bit faster? %)
Probably most of work and testing would be related to 32->64 migration of routeros kernel modules, and it would be done anyway for CCR. Linux drivers have already been tested in 64 bit mode.reason is amount of work and amount of testing, driver related work who knows what else that goes on underneath there
I've heard that x86_64 code is a bit faster. More processor registers are available, for example.I am satisfied with the 32 bit version. Why would you need a different one ? Thanks.
I think removed in 2.8icons were in 2.8 and were removed in 2.9, AFAIR
make it both version. i386 and amd64. Will there be any performance benefits? support for new cpu instructions? Do you think it will be good?it is whole new architecture for nothing, because we cannot drop x86 32bit, since a lot of users are using different intergated solutions based on x86 that have not heard anything about 64bit.
I have a 2.8.21 router sitting around.. somewhere.. here we go!I think removed in 2.8icons were in 2.8 and were removed in 2.9, AFAIR
Email support to ask for access to pre-release versionsHow does one get access to RC3 if it isn't showing up in ones account?
I knew it, I knew it! )))I have a 2.8.21 router sitting around.. somewhere.. here we go!I think removed in 2.8icons were in 2.8 and were removed in 2.9, AFAIR
0 03:02.0 Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev: 16) 5
1 02:00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev: 6) 10
That was so cool and retroI think removed in 2.8icons were in 2.8 and were removed in 2.9, AFAIR
here:
+1 ;DThat was so cool and retroI think removed in 2.8icons were in 2.8 and were removed in 2.9, AFAIR
here:
No, this is RetroThat was so cool and retro
It works fine on 5.x. It started with this problem on 6.0rc1/rc2....oh-no who is using masq with more than 1 IP ? cange to src-nat and paste the IP in there
add ipid
linux:
iptables -t mangle -A POSTROUTING -j IPID --ipid-pace 1
routeros how to set?
lol ?config NETFILTER_XT_TARGET_IPID
385 tristate '"IPID" hoplimit target support'
386 depends on IP_NF_MANGLE || IP6_NF_MANGLE
387 depends on NETFILTER_ADVANCED
388 ---help---
389 This option adds the "IPID" (for IPv6) and "IPID" (for IPv4)
390 targets, which enable the user to change the
391 hoplimit/time-to-live value of the IP header.
392
393 While it is safe to decrement the hoplimit/TTL value, the
394 modules also allow to increment and set the hoplimit value of
395 the header to arbitrary values. This is EXTREMELY DANGEROUS
396 since you can easily create immortal packets that loop
397 forever on the network.
1 ;;; server
name="LN" target=10.13.58.0/24 dst=10.10.10.10/32 parent=none
packet-marks="" priority=8/8 queue=default-small/default-small
limit-at=0/0 max-limit=20M/20M burst-limit=0/0 burst-threshold=0/0
burst-time=0s/0s
2 name="Internet" target=10.13.58.0/24,10.13.59.0/28 parent=none
packet-marks="" priority=8/8 queue=default-small/default-small
limit-at=0/0 max-limit=6M/16M burst-limit=0/0 burst-threshold=0/0
burst-time=0s/0s
3 name="MJ-3" target=10.13.58.3/32 parent=Internet packet-marks=""
priority=8/8 queue=default-small/default-small limit-at=0/0
max-limit=768k/2M burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s
look at Log - there's info about reboot and up/down-gradeWhen I load all needed packages of ROS 5.21 to files and do:
sys packages downgrade
the only thing that happenes is a reboot.
ipt_IPIDadd ipid
linux:
iptables -t mangle -A POSTROUTING -j IPID --ipid-pace 1
routeros how to set?lol ?config NETFILTER_XT_TARGET_IPID
385 tristate '"IPID" hoplimit target support'
386 depends on IP_NF_MANGLE || IP6_NF_MANGLE
387 depends on NETFILTER_ADVANCED
388 ---help---
389 This option adds the "IPID" (for IPv6) and "IPID" (for IPv4)
390 targets, which enable the user to change the
391 hoplimit/time-to-live value of the IP header.
392
393 While it is safe to decrement the hoplimit/TTL value, the
394 modules also allow to increment and set the hoplimit value of
395 the header to arbitrary values. This is EXTREMELY DANGEROUS
396 since you can easily create immortal packets that loop
397 forever on the network.
I did on rc2. I haven't yet on rc3.Does anyone else have issues with disappearing interfaces on 6.0rc3 ?
with RouterOS v6.0rc3? Make support output file when this happens send send it to support@mikrotik.comIm seeing it on a couple of mipsbe routers. Also pptp tunnels are unroutable when this happens