*) fixed upgrade problem when it failed with error “disk is too small” while
there was plenty of space left;
*) fix health and poe access reliability on OmniTIK UPA and RB750UP boards;
*) sstp - improve initial handshake to better handle many new connections;
*) wireless - do not use bridge and WDS mode on AP-AP links, causes loops;
*) dhcp ipv6 pd client - fixed ipv6 pool creation after reboot;
*) dhcp ipv6 pd client - added option add-default-route;
*) sstp - fixed connection idle time reporting;
*) fix bad block count not to increase on Samsung K9F1208U0C nand;
*) snmp - fix dhcp lease table, snmp reported an incorrect information
when a static lease had configured different address than current active address,
this should also solve problem with dude polling same leases over and over again;
*) fix RB1100 crash on interface disable/l2mtu change/reboot;
*) dns could not resolve some domain names, was ignoring replies with DNAME RRs;
*) fix firewall log action - sometimes was not logging mac addr;
I’m a bit confused here…; is this a problem in previous version that now is solved? Or is the bridge and WDS funcion on AP-AP links causing loops and in 5.18 is therefore not recommend to use?
I suppose it is a problem solved. But than again, never knew it had an issue. I use it in same situations in versions up to 5.16 and have seen no problems so far…
And what about the wireless disconnection problems in some units that evolved in 5.17?
I have made some support tickets for these with many examples but still not seeing any solution?
We had this problems on our network. Previous owner of a part of our network was using using it. After upgrading from some 5.0rcXX to 5.7 we foung huge packet rates (like 15000p/s) on some interfaces going from no IP to no IP. Everything was solved just moving from AP-AP WDS mode to AP-client mode. It was impossible for use to fing what is the problem, (switch, RB, rOS or something else) but after changing the topology it was solved, so nevermind what it was.
That changelog line means that there were a problem between WDS-WDS link that instead using just wds mode it also used the bridge mode which then created a loop. This problem if fixed now and WDS to WDS links will work fine.
RB751U-2Hn is still spinning out with 100% flash on wifi => bridge => masq => internet traffic. Rendering DNS and telnet/ssh unusable. Sigh. These models have taken so long and still not working.
Yup. Done from a netinstall. Done reset-default on the wireless configuration. Was getting the watchdog reboots before 5.17, and going back and forth on a ticket for that since December, but that, at least, has dropped in frequency to a manageable level. But heavy traffic, particularly upstream, causes the router to just spin out of control. /tool profile stops updating, on an already opened telnet session. Reproducible within about 15 seconds.
When adding DHCPv6 Binding, no matter GUI or command line, it is being marked as dynamic and disappears after router reboot.
[admin@router] /ipv6 dhcp-server binding> add duid=00010001157dbdeadbeefc0de777 iaid=24xxxxx92 address=2001:xxxx:xxxx:xxxx::10 life-time=1:00:00 server=all disabled=no
[admin@router] /ipv6 dhcp-server binding> print
Flags: X - disabled, D - dynamic
# ADDRESS DUID IAID SERVER STATUS
0 D 2001:xxxx:xxxx:xxxx::10/128 00010001157... 24xxxxx92 dhcp_ipv6 waiting
Notice the “D”. I can make it static with “make-static”, but this needs fixing I think. There are some more problems, like when I do
set [ find ] server=my_server_name
it doesn’t show in GUI.
I cannot make my Windows 7 machine to get this specific binding address… After turning on debug logging, no matter how I set ND or DHCPv6, it displays:
