Asuswrt-Merlin 3.0.0.4.270.24 is out

[RocketJSquirrel]

Is there any way to get 'Respond Ping Request from WAN' to work? It didn't work with the default FW and it doesn't seem to work with this one either. I tried it with the router firewall disabled as well as enabled without success.
Specifically, I'm using Smokeping on dslreports.com and I was pingable with my old router (Buffalo WHR-HR-G300N) using DD-WRT.

Am I missing something? Any other settings that I could attempt?

Thanks!

It works for me using Smokeping. First image shows with respond disabled, second image shows it enabled.

 

[RMerlin]

Is there any way to get 'Respond Ping Request from WAN' to work? It didn't work with the default FW and it doesn't seem to work with this one either. I tried it with the router firewall disabled as well as enabled without success.
Specifically, I'm using Smokeping on dslreports.com and I was pingable with my old router (Buffalo WHR-HR-G300N) using DD-WRT.

Am I missing something? Any other settings that I could attempt?

Thanks!

It works fine for me, I just tried it. It's probably your modem blocking ICMP packets. This will be the case if your modem isn't bridged.

 

[RMerlin]

Has there been any syslog improvements/fixes in the recent ASUS or merlin builds?

Syslog is a pretty basic feature: it takes messages and writes them to a file. What kind of fixes are you looking for?

 

[Civ]

It works fine for me, I just tried it. It's probably your modem blocking ICMP packets. This will be the case if your modem isn't bridged.

I'm using the same modem as with the old router, no changes made on that end. Hmm. I've even cloned the same MAC address to keep the previously assigned IP.

 

[nubyOz]

Is there any way to get 'Respond Ping Request from WAN' to work? It didn't work with the default FW and it doesn't seem to work with this one either. I tried it with the router firewall disabled as well as enabled without success.
Specifically, I'm using Smokeping on dslreports.com and I was pingable with my old router (Buffalo WHR-HR-G300N) using DD-WRT.

Am I missing something? Any other settings that I could attempt?

Thanks!

Don't have it in front of me, butthere is a tick box somewhere to specifically enable this. default is disabled.

Cheers

 

[Civ]

Don't have it in front of me, butthere is a tick box somewhere to specifically enable this. default is disabled.

Cheers

It's enabled, that's the first thing I did.

 

[Civ]

It appears to be dropping the ICMP packets on the router's end, according to the System Log anyway. Even with 'Respond Ping Request from WAN' enabled.

Feb 20 21:57:33 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=1 
Feb 20 21:57:34 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=2

Edit: Ahhh... I had to set my machine as the DMZ for it to finally work.

 

[netmik3]

Check mine out
https://secure.dslreports.com/r3/smokeping.cgi?target=network.bbc87e85d888ac9ddd69224ecb60444c&r=308

 

[baxterch]

WOOHOO!!!

Thank you, You pointed me in the right direction. I searched the nvram command in the forum and found another thread that explains and fixes my problem exactly. I have not tried it yet as my ADSL appears to be offline so cant get to my router right now, but this is it.

http://forums.smallnetbuilder.com/showthread.php?p=58957&highlight=nvram+rstats_path%3D%26quot%3B%26quot%3B#post58957

Thanks anyway guys, much appreciated. Now to find a little 1Gb flash drive.

Hello,

This problem has been resolved. It was exactly as in the listed thread. Thanks all for the assistance.

 

[RogerSC]

It appears to be dropping the ICMP packets on the router's end, according to the System Log anyway. Even with 'Respond Ping Request from WAN' enabled.

Feb 20 21:57:33 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=1 
Feb 20 21:57:34 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=2

Edit: Ahhh... I had to set my machine as the DMZ for it to finally work.

Not sure why you had to put your computer in the DMZ to make this work. Not something I'd want to be doing, personally. Works for me without doing that.

 

[chamberc]

Working fine here

Ping is working fine for me...

http://64.81.79.40/r3/cricket/graph...ping-time,pktloss-time&range=151200&rand=9291

 

[LegacyCode]

br0 wrong MAC

Just flashed to this firmware, everything seems to be ok.
But I noticed again that all my Windows computers detected a new network location, this is something what was happening before with firmware 3.0.0.4.264.22.

If I check the registry keys for network location awereness I see each time a different MAC-addresses for gateway, so the router somehow gets a different MAC-address. And this is causing the clients to redetect the network location (Home, Work, Public).
If I check the arp-table I see a different MAC-address then the LAN-address.
Arp says 192.168.131.254 points to 00:FF:18:1F:E0:B8
Router webpage says 50:46:5D:5E:E7:68 for LAN-address.

If I check with ifconfig and brctl the bridge has a different, guess randomized MAC-address. When I check on a different router (WRT54GL with tomatovpn) the bridge has the same MAC-address as LAN-address.
I have the feeling something is wrong with setting up the bridge.

Some commandline output:

user@RT-AC66U:/tmp/home/root# ifconfig
br0 Link encap:Ethernet HWaddr 00:FF:18:1F:E0:B8
inet addr:192.168.131.254 Bcast:192.168.135.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:173030 errors:0 dropped:0 overruns:0 frame:0
TX packets:125233 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19921535 (18.9 MiB) TX bytes:58024108 (55.3 MiB)

eth0 Link encap:Ethernet HWaddr 00:16:B6A:171
inet addr:84.197.195.146 Bcast:84.197.207.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10900311 errors:0 dropped:0 overruns:0 frame:0
TX packets:7842665 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3889840338 (3.6 GiB) TX bytes:2927005709 (2.7 GiB)
Interrupt:4 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 50:46:5D:5E:E7:68
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:461710 errors:0 dropped:0 overruns:0 frame:89603
TX packets:3612756 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31751584 (30.2 MiB) TX bytes:1058772836 (1009.7 MiB)
Interrupt:3 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 50:46:5D:5E:E7:6C
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9374 errors:0 dropped:0 overruns:0 frame:66
TX packets:75130 errors:3 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1251856 (1.1 MiB) TX bytes:15710937 (14.9 MiB)
Interrupt:5 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1
RX packets:414 errors:0 dropped:0 overruns:0 frame:0
TX packets:414 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:40641 (39.6 KiB) TX bytes:40641 (39.6 KiB)

tap21 Link encap:Ethernet HWaddr 00:FFB:7E:78:08
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:37887 errors:0 dropped:0 overruns:0 frame:0
TX packets:49709 errors:0 dropped:10 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9598964 (9.1 MiB) TX bytes:8211394 (7.8 MiB)

tap22 Link encap:Ethernet HWaddr 00:FF:18:1F:E0:B8
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:68912 errors:0 dropped:14 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:11211976 (10.6 MiB)

vlan1 Link encap:Ethernet HWaddr 50:46:5D:5E:E7:68
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2457504 errors:0 dropped:0 overruns:0 frame:0
TX packets:4910259 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:177636402 (169.4 MiB) TX bytes:2707332019 (2.5 GiB)

vlan2 Link encap:Ethernet HWaddr 50:46:5D:5E:E7:68
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

user@RT-AC66U:/tmp/home/root# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00ff181fe0b8 yes vlan1
eth1
eth2
tap21
tap22

 

[dopefish]

Very happy with 3.0.0.4.270.24, no problems so far.
~13 devices, OpenVPN enabled.

Thank you Merlin.

 

[fr33z0n3r]

Syslog is a pretty basic feature: it takes messages and writes them to a file. What kind of fixes are you looking for?

I'm thinking more about things that syslog captures than syslog itself. It seems it would be nice to capture the access log for the built-in web services (including uri) as well as general outbound fw access. The later may just be a simple rule tweak, but I'm hoping to avoid custom scripts.

How did I forget - IPv6 isn't logging as well I believe.

 

[RMerlin]

I'm thinking more about things that syslog captures than syslog itself. It seems it would be nice to capture the access log for the built-in web services (including uri) as well as general outbound fw access. The later may just be a simple rule tweak, but I'm hoping to avoid custom scripts.

The internal web server isn't a full web server in the sense you might be thinking (it's not Apache or lighttpd). It's a custom daemon that happens to process HTTP requests, with a custom backend.

I'm not sure if logging webui logins can easily be done (due to the way Asus handles authentication), I can have a look.

For firewall logging there is an option on the Firewall page to enable packet logging. Logging everything isn't really practical however, since everything is logged in clear text in the RAM disk, so you run the risk of quickly filling it up.

 

[fr33z0n3r]

It appears to be dropping the ICMP packets on the router's end, according to the System Log anyway. Even with 'Respond Ping Request from WAN' enabled.

Feb 20 21:57:33 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=1 
Feb 20 21:57:34 kernel: DROP <4>DROPIN=eth0 OUT=eth0 <1>SRC=209.123.192.187 DST=192.168.1.113 <1>LEN=1052 TOS=0x00 PREC=0x00 TTL=47 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=56367 SEQ=2

Edit: Ahhh... I had to set my machine as the DMZ for it to finally work.

This is a terrible idea, unless you are extermely confident regarding your computers host firewall configuration filters out all traffic like SMB, UPnP, etc. If you didn't understand that sentence, you should probably undo the setting.

Note to others: This is a bad idea for a fix.

 

[got_milk]

Note to others: This is a bad idea for a fix.

This isn't really a fix anyway, more of a workaround. Putting it in the DMZ moves takes most routing out of the equation and therefore the problem.

 

[admiral2145]

Transfer Speeds

I have a 3tb seagate usb 3.0 external hdd connected to my ac66u. It starts out transfering data at 15 megabytes a second but, after some time it slows down to 7 or 8...Is there a fix or something going wrong with my transfer rate? checked the buffers and the cpu usage on the ac66u and its not over worked or high...


edit... never mind I have a wireless computer backup with acronis to the drive at the same time...

 

[xaviercharles]

I've been having a "NAT not open" issue on the XBOX 360. When ever i try to play Halo 4 it says my NAT is not open. I've checked the N66U under WAN and NAT is enabled. Anyone else having this issue?

 

[RMerlin]

I've been having a "NAT not open" issue on the XBOX 360. When ever i try to play Halo 4 it says my NAT is not open. I've checked the N66U under WAN and NAT is enabled. Anyone else having this issue?

Who knows what that actual error message really means (I find gaming consoles have the worst technical descriptions/error messages I have ever seen in a mass market product - both the XBox and PS3. NAT isn't something that can be "open" or "closed", it's the name of the process used to modify packets). I would make a blind guess and suspect that your modem is also running as a router, causing a dual NAT situation.

Also make sure UPNP is enabled on the router, in case the XBox would use it to open inbound ports.