What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

My phone' CSC original code is NEE (Nordic Countries) and now i have BTU(UK). My router had default code EU. I don't know if it's a limitation of the phone or a router problem, must do more tests...thanks

Sent from my SM-N9005 using Tapatalk
 
dual wan does work,
make sure before you start that both ip address are different subnets...
if you change between "load balance" to "fail over"
you have to go back to single wan before setting up "fail over" otherwise you will loose both links ,
things get kind of hammered.

same holds true with "fail over" to "load balance"

when on "fail over" the secondary (374_43_2 original merlin)showed standby when it was not in fail over now it shows connected when both links are active

on "load balance" both are connected on "network map" page
you can go from one network to the other
i.e. wan 192.168.7.0 , lan port 4 192.168.1.0 ping etc...

on "fail over" primary shows connected, secondary shows connected
shouldn't the secondary show standby ?? the original 374-32-2 did..

v3 and original 374-43-2
and "fail over"you can not ping from primary wan to secondary wan..

I can't think of anything that was changed that would affect dual wan behavior (and I have no way to test that for myself). I hate to give out the standard answer....but have you tried a factory reset?
 
Chrome, IE11,Firefox, and some unix browers...

all the same

it looks like it may have something to do with this function
*** function change_wan_state(primary_status, secondary_status) (index.asp) maybe (~/asuswrt-merlin/release/src/router/www)


secondary wan standby (should be)

index.asp hasn't been touched since 4 April

root@ubuntu:~/asuswrt-merlin/release/src/router/www# git log index.asp
commit e6d29252bb9f32eb6f4423d8757d53cedd3a7fbe
Author: Eric Sauvageau <rmerl@lostrealm.ca>
Date: Fri Apr 4 01:13:21 2014 -0400

Merge with 374_4887 GPL (2/2)
 
I traced things back a bit, and the status is read from a series of nvram variables that end in 'state_t'

If you want to keep looking, it would be of interest to see the results from

nvram show | grep state_t

on code that shows the status you expect vs one that doesn't.
 
No, that's just an 'enhancement' that some people may like. Without it, everything runs just the way it has in the past.

how to apply the dnsmasq.leases fix?

how to check what the current status?

after apply if want to revert to default, how to do it?
 
Without details, I'll take a crack at what he might be seeing. Local name resolution does in some cases make use of the dnsmasq.leases file. When you reboot or load code it gets wiped out since it's kept in ram.



Now, the wireless clients see the drop and request new leases. The wired clients, however, do not....and wait for their local lease time to expire before requesting a new lease. And if they are not configured with a fixed ip address, the router doesn't know about them by name. Until they request a new lease, local name resolution for wired clients without a fixed ip won't work. In order for them to get a new lease, you would need to unplug/plug the ethernet cables for each one.



The solution....move the leases file to non-volatile store so it survives reboots. I keep mine in a /jffs/tmp directory. Two things need to be done.



First....add the appropriate lines to dnsmasq.postconf script.



Code:
#!/bin/sh

CONFIG=$1

source /usr/sbin/helper.sh



pc_insert "resolv-file=/tmp/resolv.conf" "dhcp-leasefile=/jffs/tmp/dnsmasq.leases" $CONFIG



Second, the webui is hardwired to look in the default location, so make a symlink to the new leases file in the init-start script.



Code:
#!/bin/sh



# Symlink to non-volatile dhcp lease file

ln -s /jffs/tmp/dnsmasq.leases /tmp/var/lib/misc/dnsmasq.leases



Now you can either let the new lease file populate itself, or 'seed' it with your existing file by copying /tmp/var/lib/misc/dnsmasq.leases to your new location. Reboot and you are done.



After this there won't be any delay in local name resolution. Note that this is really only for routers up 24/7 to be accurate. It you power down the router for long periods, it won't hurt anything, but the leases data of course won't be correct.


I can give your suggestions a shot, but this is a problem I've seen come and go with the ASUS bases firmware. I'm using an AC68, and out of the blue resolving the local name of my NAS (it's running avahi) will stop working. Rebooting the NAS doesn't fix it. Rebooting the router does.
 
Logging into router (ac56 model) spins up hdd, is it normal?

I see my USB drive spin up when I log in about 1/2 the time.....if it's not being accessed, it will then spin down on the timer if you have a spindown timer set. I haven't been able to deduce any pattern that would explain why it feels the need to spin up. Not something I would be concerned about.
 
After some uptime -03 is running great here.
Local hostname resolution, DHCP, all OK.
OpenVPN, I use almost every day, no problems.
No open ports, tested with Shields Up.

Thumbs up. :)
 
My phone' CSC original code is NEE (Nordic Countries) and now i have BTU(UK). My router had default code EU. I don't know if it's a limitation of the phone or a router problem, must do more tests...thanks

Sent from my SM-N9005 using Tapatalk

Speedtest for WAN to LAN, pppoe
 
just updated to update 3 and found that i can access the router remotely even with Allow SSH access from WAN set to no.

reverting back to 2
 
just updated to update 3 and found that i can access the router remotely even with Allow SSH access from WAN set to no.

reverting back to 2

Can someone else try this? Can't immediately think of any change that would affect the SSH behavior.
 
just updated to update 3 and found that i can access the router remotely even with Allow SSH access from WAN set to no.

reverting back to 2

Make sure you test from outside your network, and that you didn't disable the firewall on the router.
 
Could you include the new build date and/or your version in the thread title? It would make it easier to see if there's an update. I would suggest using date eg 140906 or 20140906 as this is easiest to search and date.
 
I don't believe I have the ability to change the thread title. Also, I remember from one of Merlin's posts that if you change the thread title it would break people who had subscribed to the thread.
 
Could you include the new build date and/or your version in the thread title? It would make it easier to see if there's an update. I would suggest using date eg 140906 or 20140906 as this is easiest to search and date.

How hard is it to just check the thread for new updates. :rolleyes:
 
IS what I consider a bug guys, I expect it also exists in asus and non forked merlin firmwares.

If disabling ping's in the firewall, they still are allowed on ipv6 traffic (with ipv6 firewall enabled of course)..
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top