Fantastic news! Thank you!*) wireless - added U-NII-2 support for US and Canada country profiles for hAP ac^3;
*) wireless - added U-NII-2 support for US and Canada country profiles for hap ac, hAP ac^3 LTE6, Audience and Audience LTE6;
poe-out, warning Failed to upgrade poe FW on /dev/poe, diag code -778/0
What is this bug?Can't believe that "Delegated-IPv6-Prefix" didn't fixed in this release also. How many months do we have to wait to fix this option in stable release?
Is it really hard to get fix from 6.49beta and implement it? Unbelievable...
The security package is disabled or not installed?CRS354-48P-4S+2Q+ ( problem ). Using Winbox , there is a 6.48.4 update shown in the latest version , however , when performing the [ Download&Install] it looks like it is downloading but when it reboots, it is still version 6.48.3
Is not better to use directly pppoe-server to distribute IPv6 with "DHCPv6 PD Pool" on pppoe-server profile?It's a radius attribute to distribute prefixes to users. DHCPv6 server create dynamic rule for it but with empty name. So first user can connect and rest get an error. Pics attached fyi.What is this bug?
Im just trying to implement ipv6 using dhcp-pd...
Thanks, understanded.We want to keep static per user because of regulations. Otherwise every user take an block from pool individually.
ip firewall filter add action=accept chain=input comment="CAPsMAN accept all local traffic" dst-address-type=local src-address-type=local
add action=drop chain=input comment="drop all not coming from LAN" in-interface-list=!LAN
/ipv6 address
add from-pool=isp interface=bridge
/ipv6 dhcp-client
add add-default-route=yes interface=ether1-isp-gateway pool-name=isp \
request=prefix
/ipv6 firewall filter
add action=accept chain=input comment="Allow all ICMP6" protocol=icmpv6
add action=accept chain=input comment="Allow DHCP for PD" dst-port=546 \
protocol=udp
add action=drop chain=input comment="Drop (invalid)" connection-state=invalid
add action=accept chain=input comment="Accept (established, related)" \
connection-state=established,related
add action=drop chain=input comment="Drop the rest" in-interface=\
ether1-launtel-gateway
add action=accept chain=forward comment="Allow all ICMP6" protocol=icmpv6
add action=drop chain=forward comment="Drop (invalid)" connection-state=\
invalid
add action=accept chain=forward comment="Accept (established, related)" \
connection-state=established,related
add action=drop chain=forward comment="Drop the rest" in-interface=\
ether1-launtel-gateway
/ipv6 nd
set [ find default=yes ] interface=bridge ra-interval=5s-10s
...errr...what's that all about?*) lte - added support for Sharp 809SH;
/interface wireless registration-table print as-value
"dst-address-type=local" and "dst-address=127.0.0.1" are not same things!Short answer: Yes; but I do not know the ''local" part in your syntax; i've used "127.0.0.1"
At least, the former includes the latter"dst-address-type=local" and "dst-address=127.0.0.1" are not same things!
What exactly did happen? Reboot (needed to perform upgrade) AFAIK always causes removal of all dynamic items - including members of address lists.THE Upgrade from RoS v6.48.3 [Stable] to RoS v6.48.4 [Stable] CAUSED ALL my dynamic Blacklist to be removed and/or deleted .... The very same has been reported by many of my MOAB Clients
And I lost nearly all my static DNS...THE Upgrade from RoS v6.48.3 [Stable] to RoS v6.48.4 [Stable] CAUSED ALL my dynamic Blacklist to be removed and/or deleted .... The very same has been reported by many of my MOAB Clients
@mkxWhat exactly did happen? Reboot (needed to perform upgrade) AFAIK always causes removal of all dynamic items - including members of address lists.
Logically it should, but in this caseAt least, the former includes the latter :)"dst-address-type=local" and "dst-address=127.0.0.1" are not same things!
ip firewall filter add action=accept chain=input comment="CAPsMAN accept all local traffic" dst-address-type=local src-address-type=local
ip firewall filter add action=accept chain=input comment="CAPsMAN accept all local traffic" dst-address=127.0.0.1 src-address=127.0.0.1
ip firewall filter add action=accept chain=input dst-address=127.0.0.1
Can this be related to other incorrect system health/voltage readings on some devices? Maybe current and power readings are also affected in addition to voltages...we have noticed a sudden increase in power current on our RB1100x4 with 6.48.4 ?
it was bobbing at 450ma for months then after the update its jumped to 750ma?
roll back to 6.48.3 and the current drops back to 450ma?
Possibly yes but I’m not sure,Can this be related to other incorrect system health/voltage readings on some devices? Maybe current and power readings are also affected in addition to voltages...we have noticed a sudden increase in power current on our RB1100x4 with 6.48.4 ?
it was bobbing at 450ma for months then after the update its jumped to 750ma?
roll back to 6.48.3 and the current drops back to 450ma?
I think the voltage readings on CCR are a different issue.Can this be related to other incorrect system health/voltage readings on some devices? Maybe current and power readings are also affected in addition to voltages...
Any news on this problem?we have noticed a sudden increase in power current on our RB1100x4 with 6.48.4 ?
it was bobbing at 450ma for months then after the update its jumped to 750ma?
roll back to 6.48.3 and the current drops back to 450ma?
[admin@MikroTik] > /int bri por pri
;;; disabled
switch: none
control-ports:
excluded-ports:
[admin@MikroTik] > /int bri port pri
Flags: I - INACTIVE; D - DYNAMIC; H - HW-OFFLOAD
[...]
Yes, that will explain it, thx, tested and that is the case/int bri por is expanded to /interface bridge port-controller for some reason.. just don't abbreviate cli commands, they are suspected to change anyway.
...
interface wireless registration-table reset
reset -- Reset a specific registration-table
It resets the counters of a specific entry. Like in firewall.Can someone tell, what the new action "reset" does in:
Same problem with 5G radio on RB-962 ROS 6.48.3, 6.48.4, 7.1RC4"DHCP without success" symptom cause by 5G radio crash (broadcasts stop being forwarded - zero TX counter) still not fixed.