Asuswrt-Merlin 376.44 is out

[ColinTaylor]

What information about my settings of router should I present for clever community that can help me with my god damn port forwarding?

I suggest that you start a new thread as your problem is not specific to 376.44 and the replies are getting lost amongst all the other posts.

Is any kind of tool that can test is specific port is open or not?

https://www.grc.com/shieldsup

 

[Jobine]

I just tested it and it's working correctly for me.

Try disabling HW acceleration under LAN -> Switch Control.

All works without Nat acceleration... why ? like that my files transferts gone be more slow ?

 

[RMerlin]

All works without Nat acceleration... why ? like that my files transferts gone be more slow ?

HW acceleration is only necessary for WAN speeds above 150 Mbps.

 

[Alfsu]

Removed layer7 filtering support

@ Merlin,

How are Selective Routing & Firewall-Start Scripts affected by:

"- REMOVED: Removed layer7 filtering support in Netfilter from ARM devices due to compatibility issues (AC56,AC68)"

I had working scripts on an AC66 for selective routing, and have recently migrated to an AC56 for the additional CPU processing power.

Can I still use the same scripts?
What should I be concerned with? (if any)

Thank you

 

[RMerlin]

@ Merlin,

How are Selective Routing & Firewall-Start Scripts affected by:

"- REMOVED: Removed layer7 filtering support in Netfilter from ARM devices due to compatibility issues (AC56,AC68)"

I had working scripts on an AC66 for selective routing, and have recently migrated to an AC56 for the additional CPU processing power.

Can I still use the same scripts?
What should I be concerned with? (if any)

Thank you

I doubt those scripts used any Layer7 iptables rules, but I haven't looked at them so I can't be 100% positive.

 

[kibosh]

Unfortunately I have had to return to .43 from .44. Every couple of days I would lose my internet connection completely. I think it occurs when the lease is up with the ISP. Something similar used to happen with older versions of the firmware and it seems to have returned with this version.

Here is what was in my log:

Aug 16 09:33:46 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:33:46 miniupnpd[724]: Failed to get IP for interface eth0
Aug 16 09:33:46 miniupnpd[724]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts - 5 addresses
Aug 16 09:33:46 dnsmasq[657]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:46 dnsmasq-dhcp[657]: read /etc/ethers - 3 addresses
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.204#53
Aug 16 09:33:46 dnsmasq[657]: using nameserver 64.71.255.198#53
Aug 16 09:33:49 WAN Connection: ISP's DHCP did not function properly.
Aug 16 09:33:49 stop_nat_rules: apply the redirect_rules!
Aug 16 09:33:50 dnsmasq[657]: exiting on receipt of SIGTERM
Aug 16 09:33:50 dnsmasq[2084]: started, version 2.72test3 cachesize 1500
Aug 16 09:33:50 dnsmasq[2084]: warning: interface ppp1* does not currently exist
Aug 16 09:33:50 dnsmasq[2084]: asynchronous logging enabled, queue limit is 5 messages
Aug 16 09:33:50 dnsmasq-dhcp[2084]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts - 5 addresses
Aug 16 09:33:50 dnsmasq[2084]: read /etc/hosts.dnsmasq - 3 addresses
Aug 16 09:33:50 dnsmasq-dhcp[2084]: read /etc/ethers - 3 addresses
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.204#53
Aug 16 09:33:50 dnsmasq[2084]: using nameserver 64.71.255.198#53
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 09:36:41 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:25 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Aug 16 10:16:29 miniupnpd[724]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address

Looks like the issue isn't with the newest firmware. I rolled back to 43 and after 2 days I got the same issue. I guess something else has changed with Rogers?!?!

 

[Alfsu]

No Layer 7 rules in selective routing scripts

I doubt those scripts used any Layer7 iptables rules, but I haven't looked at them so I can't be 100% positive.

Thank you Merlin for your answer.

I did further research and there is no Layer 7 commands used in the selective routing scripts used on my 56U.

Cheers!

 

[speedlever]

Sticking this in here because I'm running 376.44, but this question is really generic. Do you guys find the Auto channel setting to work well? Or do you prefer to do a site scan and choose your own static channel?

When I put mine in auto, it defaults to channel 6, which already has some neighboring homes using... as do channels 1 and 11. Does the auto channel selection work pretty aggressively to minimize the noise?

 

[Deleted member 22229]

Sticking this in here because I'm running 376.44, but this question is really generic. Do you guys find the Auto channel setting to work well? Or do you prefer to do a site scan and choose your own static channel?

When I put mine in auto, it defaults to channel 6, which already has some neighboring homes using... as do channels 1 and 11. Does the auto channel selection work pretty aggressively to minimize the noise?

I never use auto for channel selection in any router brand it just never seems to work right, i have had routers set to auto that would pick the worse possible channel for what ever reason. I always manually select my channels.

 

[speedlever]

Thanks for the input. I wonder how the auto function is supposed to work? Always scan and move to the least congested channel? I suppose if everyone was in auto, there would be quite a bit of channel hopping going on.

 

[RMerlin]

Set DNS Filtering on with a global default of no filtering. Selected one of the clients to OpenDNS Home (for example) and then changed to Comodo and reapplied the setting. Filter remained on OpenDNS despite Comodo being chosen. Filter always appears to remain on the previously selected filter whenever Comodo is selected.

Still can't reproduce it here. The setting was properly set to Comodo after I applied the change to the OpenDNS-configured client, so it must be a browser-specific issue.