The guys at dd-wrt fixed the NAT Loopback since 19969 changeset:
http://svn.dd-wrt.com:8000/changeset/19969
This code was removed from the Firewall Script:
Yes, I'm actually using Phuzi0n's NAT loopback code in my builds.
The guys at dd-wrt fixed the NAT Loopback since 19969 changeset:
http://svn.dd-wrt.com:8000/changeset/19969
This code was removed from the Firewall Script:
I just flash to 260 and the driver for the radio is the same as your 19B version, that is, if I interpret it correctly in the log.
Dec 31 19:00:07 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.20
Dec 31 19:00:07 kernel: wl_module_init: passivemode set to 0x0
Dec 31 19:00:07 kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Dec 31 19:00:07 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 31 19:00:07 kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Dec 31 19:00:07 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Dec 31 19:00:07 kernel: Algorithmics/MIPS FPU Emulator v1.5
So it looks like it has the same drivers as 220?
I don't think that Merlin himself won't know what changes were made in 260 vs 246 until Asus releases the source code for 260. IIRC, Merlin said it usually takes a few days after the new firmware version's release for that to occur.Just looked at my notes , 220 worked well 246 had lota of dropped connections , went back to 220 . This is strange as you're saying 260 uses the same drivers as 246 , be interested in the changes made to make 260 stable .
Thanks for all the work Merlin
If you mean the fact that LAN to LAN connections are all NATted, yes, my firmware uses a completely different NAT loopback that resolves this issue. Otherwise, your double NAT issue probably comes from your modem also applying NAT on top of your router's NAT.
Yikes, unstability is still in 260. Wireless clients disconnects and having a hard time connecting. Disabling GRO seems to settle it a bit. I'll give it time and see if it stays stable this way.
Update: 2.4 band wireless in 260 is just as unstable as 246, it seems nothing was fix in this firmware version. No wonder there is no mention of fixing wireless instability in the changelog. I give up back to RMerlin's stable 19b.
I have six wireless clients, all running 2.4ghz. 3 ipads on video call at same time for 3 hours, 2 desktop (both on watching hd video streams for 4 hours) and 1 laptop. No disconnection.
But did you have stability issues with build 246? Not everyone was affected by it, for some reason.
For what it's worth Merlin I had issues with the 5GHz band with build 246. Namely, I could not connect to the 5GHz band. As soon as I flashed your build 246.19b all was well. I am running build 260 with GRO disabled and all seems well. I can connect to the 5GHz band like nobody's business. Also, I haven't seen any issues with Parental Control yet. If PC should puke again I will notify Asus but so far so good.I'd be really interested in hearing from people who had major wireless stability issues with 246 to know if build 260 resolved them? So I'll know which wireless driver I'll use for my own build.
Well now IPV6 is broken! Anyone else verify....
CC
mine is broken also,
I'll try resetting it like you did and see what happens
I've found that IPv6 doesn't always come up after upgrading firmware and doing a reboot. Sometimes it takes an extra reboot or two to fully come up. I've also gone back to reset and then rebooted a couple of times. But it does come up after a single reboot when upgrading firmware sometimes.
I've waited 3 hrs and no ipv6
ao maybe I'll try that,did you get it to work on the 260 firmware?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!