Version 1.3.12

[ng3700v2]

Mix - Yes, I did power cycle the modem even though I haven't had to do that in the past when switching routers in and out.

[Domino_55]

Eric,

Thanks for commit! Ok, I will use the github in the future.

[Domino_55]

Domino_55:
I had a few minutes to play with your wndr3700v2 image. It flashed successfully, and I could play with the gargoyle web interface; but I couldn't get it to acquire an IP address from my cable modem. I even SSH'd into the router and bounced the interfaces (ifconfig xxx down/up). Is there something else I need to do?

Anyway, I just wanted to give some quick feedback since I won't have a chance to play with it again until this evening. Thanks again for the contribution and getting this far with it!

Sorry, but I can't help to you, because I don't have wndr3700v2. I could only help for compiling an image for it.

[olo]

I encounter weird Gargoyle behavior while I left the router with no connections and try to connect a few hours later. It seems like DHCP can't assign the addresses and Wi-Fi doesn't work. After manually configuring the computer's interface I can access the router which needs a reboot in order to enable it start assigning addresses again. I have Asus WL-500-gP V2. I'm not sure if the error exists with previous version - 1.3.11. Version 1.3.9 worked flawlessly. Any ideas?

[ng3700v2]

Domino_55/Max -
Got a chance to do some more testing. I changed the LAN IP to 10.1.1.1 on my WNDR3700v2 and connected the WAN port to my WRT54GL (my active router running Tomato while I figure out how to get the 3700 up and running with gargoyle). I experienced the same behavior here as with the cable modem -- the 3700 did not pick up a WAN IP from the DHCP server running on the WRT54GL as expected. I wondered if the dhcp client was broken, so I hardcoded a WAN IP of 192.168.1.54/255.255.255.0 with gateway 192.168.1.1 and saved the changes. It still did not appear to be working, and I was unable to even ping the 192.168.1.54 address from my other systems on the 192.168.1.0 network. A power-cycle (for kicks) of the 3700 didn't resolve the issue either. It simply appears that the WAN port on the WNDR3700v2 is simply not functioning at all even though I do get a link-light when plugging in the cable.

Perhaps the /etc/config/network parameters are incorrect... I will do some poking around on the definitions to see if can come up with anything.

I will keep you posted on any progress.


Thanks again for the help!
Any other tips/advice would be appreciated!

[ng3700v2]

Update: turns out it was the WAN-eth0.2 definition in the /etc/config/network that was causing the WAN port to not receive an IP address from the cable modem. I loaded OpenWRT onto the wndr3700v2 to get another look at its network configuration. I had success using the default OpenWRT configuration after reflashing with Gargoyle. However, the none of the bandwidth monitoring or "web usage" monitors seem to work. Is there a way I can "bounce" these modules outside of the web interface?

Thanks!

[Domino_55]

ng3700v2,

The eth0.2 WAN ifname is very interesting by default. On a clean Gargoyle install what is the output of the following command?

Code: Select all

awk 'BEGIN{FS="[ \t]+:[ \t]"} /machine/ {print $2}' /proc/cpuinfo

And what is the content of the /etc/config/network file of course on a clean install?

[Cezary]

For WNDR3700v2 wan should be eth1, not eth0.2

[Eric]

ng3700v2/Domino_55: You may want to try a build from the latest source.

Within the last few days I've introduced a different mechanism for detecting what the default interfaces should be, which is what I think is causing this problem. Before there was an ugly, hackish system for guessing the right interface. I've replaced this with a new system that's a little bit cleaner that checks what the interface is on the first boot and then saves it for future reference. I'm not quite ready to do another release yet (there is still at least one minor bug on the status/overview page relating to this), but I think this update will solve the problem of the wrong interface being set, as well as make the TP-Link 941NDv3 router work correctly (several people have reported problems due to the odd switch configuration).

[ng3700v2]

Eric/Domino_55:
Good news! I decided to figure out how to build images on my own using an Ubuntu 10.10 virtual Linux guest under Sun (now Oracle) VirtualBox. It was surprisingly simple but just took a little while to compile. I flashed the Netgear WNDR3700v2 with the newly built gargoyle image, and everything seems to be working beautifully. The /etc/config/network was correct out of the box! The bandwidth monitoring and web usage is now working as well. Perhaps Eric's latest updates resolved my issues? On a side-note, I also discovered that the DHCP server was not functioning correctly on the prior image, but it appears to be ok now.

Domino - the output of your requested "awk" command is: NETGEAR WNDR3700v2.

I would be more than happy to post my wndr3700v2 image if someone else would like to try it...

Thanks for all of the help guys and keep up the great work!