This chipset was never fully supported. we will check if we can add it properly.
Thank you for your feedback.
Can you, please, provide me also feedback related to my 2nd point?
*) ssh - improved system stability when processing none-crypto SSH connection;
Can be this fix related to run SCP via SSH tunnel terminated on ROS?
Wifiwave2 AC3 and AX3:
/interface/wifiwave2/info country-info doesn’t work anymore since 7.7
It was already reported in the 7.7 thread but still not fixed.
SUP-107615 created.
Already got a reply (fast !).
submenu info country-info is removed.
Info is to be collected via /interface/wifiwave2/radio print detail
(but currently output is not of the same level/detail as it was using country-info so I asked about that again)
EDIT: extended info will become available in /interface/wifiwave2/radio print detail
Why is that so important for you? This is all static info that you can get from the relevant authorities…
Oh but it’s not important at all to me.
I know where to find that info in other places.
The info used to be there prior to 7.7, some users are having problems determining why some settings they are using are not working.
I assumed nobody ever bothered creating a ticket for it. I did, got a response and shared that info.
Not everyone uses BGP, you know :lol:
I sent a supout file three days ago.
Info from authorities sometimes doesn’t exactly match limitation built in ROS. Sometimes is thus very useful to get this info to verify what are actual limits imposed by ROS in actual device.
I have been using 7.8rc1 for 3 days now, and there has not been any issue with interrupted streaming since then. My main streaming service is Netflix, and IPv6 is enabled in the network. I believe the AAAA resolution issue with DNS has been resolved. Those who have encountered the issue before can upgrade to 7.8rc1 for testing.
I found a bug (present in 7.4.1 through to 7.7) where OSPF ECMP routes, when they return after a failure, are not loaded into the L3HW, despite showing up in the routing table. I’ve submitted a ticket but haven’t heard back yet.
@ErfanDL
Dear Erfan, can you tell me which USB LTE and carrier you use, please? I’m interested in buying one.
[ALERT] (1) : exit-on-failure: killing every processes with SIGTERM
[ALERT] (3) : [haproxy.main()] Cannot chroot(/var/lib/haproxy).
[NOTICE] (1) : Loading success.
[NOTICE] (1) : New worker (3) forked
[NOTICE] (1) : haproxy version is 2.7.2-7e295dd
[NOTICE] (3) : haproxy version is 2.7.2-7e295dd
[WARNING] (1) : All workers exited. Exiting... (1)
[WARNING] (1) : Current worker (3) exited with code 1 (Exit)
My HAproxy container start failing on 7.8rc1, they were working fine on 7.5, was something changed?
Unfortunately there is no information about CAPsMAN in the Release Notes, are there any improvements in this area since 7.7?
ZTE MF79U on MTN
how did you get ospf3? I’m testing on two CRS317 which converge fine in ospf2, but never using IP6
At least on CRS317 you need to disable IGMP snooping on the bridge to get OSPFv3 working. And yes, support says this is normal …
I must have misunderstood then. I saw the following change and figured that it was that:
*) route - fixed IPv6 default route presence when received from RA;
If that is not what I thought, then what is that change?
Internet tethering from Android phone via USB is not working, lte1 DHCP client stays in invalid state. Had to rollback to 7.7. Tested on hap ac3 BTW.
mducharme - New flags and properties are added to routing table. Default SLAAC routes will be there in v7.9.
This turned out to be an issue with Vodafone, which they have since resolved.