Recent content by kolodzij

No scripts...have a VPN server but no client A thought....you are applying valid ipv6 QOS rules after a set of invalid ipv6 QOS rules were applied during the last reboot.

OK, Went from QOS OFF to QOS ON followed by SAVE automatic full router reboot Went back to QOS page and did a SAVE Dec 15 12:21:21 HTTP login: login 'admin' successful from 192.168.1.100 Dec 15 12:21:27 rc_service: httpd 561:notify_rc restart_qos Dec 15 12:21:27 qos: using ipv4_lan_ipaddr...

Looks like it schedules a full reboot when I do the save...followed by the missing iPv6 address retries Dec 15 08:10:41 dnsmasq-dhcp[576]: DHCPACK(br0) 192.168.1.100 00:23:54:13:33:c9 HP-PC Dec 15 08:14:56 HTTP login: login 'admin' successful from 192.168.1.100 Dec 15 08:15:11 rc_service...

RT-AC68P so 68U works

Dec 31 17:00:21 kernel: Ebtables v2.0 registered Dec 31 17:00:21 qos: using ipv4_lan_ipaddr 192.168.1.0/24 Dec 31 17:00:21 qos: ipv6_lan_ipaddr doesn't exist, retrying Dec 31 17:00:22 qos: ipv6_lan_ipaddr doesn't exist, retrying Dec 31 17:00:22 rdnssd[690]: Get IPv6 address & DNS from DHCPv6 Dec...

I have a VOIP adapter...and there is a lot of code devoted to QOS. My workaround is to not use QOS but for those who want/need it would be great if it could be fixed. I suspect this is linux 2.6 bug since people have posted about it over a year ago.

John, Running version 16B5 of the fork and have verified that lan wired ports still do not get QOS set properly with native iPv6. Found another recent post stating the same problem with Merlins most recent release 378.56. When are you getting native iPv6...

I only had one custom QOS rule for an OOMA voip adapter. The rule is mac address, any proto and highest priority. I tried deleting the rule and it worked until a reboot and problem reoccurred. I suspect the setting is QOS related but its not something visible on a screen. I deleted the rule but...

Well, I reflashed turns out it is a bad setting thats causing the problem. While manually re-entering the QOS settings I was able to corrupt the QOS setting(s) again. Only way to clear it is to do a factory reset and start all over again. Up until Cox enabled native IPv6 3 days ago never had a...

Last action was a save on QOS page only 14E1 - save settings - Merlin 378.55 - factory reset - 14E1 - factory reset - restore settings I will try a reflash and manual settings

Here is some of the file content that may be helpful while the router is in this state.

I did a save again and no longer have IPv6...log uploaded

Nope, still no go on Lan ports, IPv6 QOS works fine on wireless, that's the part that puzzles me. I have uploaded the system log after I modified the QOS speeds followed by a reboot. BTW I have verified this on 2 separate machines. PS When I modified and saved the QOS parameters I lost IPv6...

OK I have done a little more research on this and believe there is still a problem with QOS and native IPv6. I have verified this with multiple sites and it only occurs on lan connections, wireless connections QOS work fine. A post from 4/28/2014 on the ASUS RT68U support forum outlines the...

Don't ask me how it corrected itself...but here is the most recent speedtest with QOS on. QOS is set for 45/5 Mb/s. I did not power off or reboot the router! Maybe it took a QOS off/QOS on cycle since QOS was previously on with a 6to4 relay setting before the native IPv6 today.