Posted: Tue Jun 16, 2009 4:55 Post subject: Re: SSH
jubei wrote:
cbutters wrote:
I didn't see that this had been asked, but is there the chance that the SSH features (for tunnelling purposes) will ever be enabled on the whr-g300n firmware?
Thanks for all the support and effort for making dd-wrt available for this device.
I use SSH for tunneling with this router just fine. You need to enable BOTH SSHD's - remote management and the normal SSHD
DOH!, Wow thanks for the tip, I'm back in business. I missed enabling sshd on the services page. Thanks !
hy there finally flashed my g300n with ddwrt, working fine so far but i have some problems configuring the virtual servers/port mappings for several applications. when i try to map a udp or tcp port and click ok the fields are empty again?
and another question: is it possible to overclock the device?
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Sat Jun 27, 2009 10:11 Post subject:
I can try and play around with the virtual port mapping when I get home.
As far as overclocking goes, I wouldn't try it.
The WHR-G300N already runs at 384 mhz while most of the other routers usually run 200-300 mhz.
Not sure if overclocking is even supported on this.
You could try, but you could end up with a bricked unit as well. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Sat Jun 27, 2009 10:33 Post subject:
This one is particularly risky because this one is the RaSoc chipset, not Atheros or Broadcom
Not sure if there is any JTAG info out there.
Running stock, it ran really good, but I upgraded to 2x WNDR3300's because I wanted to play around with the 5GHZ connections on Wireless-N. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
I'm having some very weird problems with WHR-G300N.
Running all different version of Eko BS2 v24 preSP2 gives the same result, even this latest version SVN 12387.
Two WHR-G300N, same hardware version. From the web configuration page, one of the WHR-G300N shows the same MAC for both LAN MAC and WLAN MAC!!
So I tried to telnet to the router to get more info:
WHR-G300N 1:
vlan1,eth2,br0,br0:0 00:1D:73:11:11:12 LAN MAC vlan2 00:1D:73:11:11:13 WAN MAC ra0,wds[0-9] 00:1D:73:D1:2B:54 WLAN MAC apcli0: 00:1D:73:D1:2B:55
etherip0: 5A:27:7D:E4:99:20
WHR-G300N 2:
ra0,br0,br0:0,wds[0-9] 00:0C:43:30:52:60 WLAN,LAN MAC ether2,vlan1 00:0C:43:30:52:77
apcli0,vlan2 00:0C:43:30:52:61 WAN MAC etherip0: 12:B3:80:1E:B4:50
As one can see, the vlan1,vlan2,br0,br0:0 aren't assigned consistently, and it seems that there is no rules for LAN interface to be assigned to a specific interface.
So my questions are:
-Which one should be the LAN interface?
-Which one should be the WLAN interface? (my guess is ra0)
-Which one should be WAN interface?
-How about other interfaces (vlan1, br0,apcli0)? What I can do to make them assign consistently?
It looks like that the problems I'm having with this router might be caused by this virtual/physical interface assignment problem.
Many thanks to make the firmware work with WHR-G300N!!
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Tue Jun 30, 2009 6:18 Post subject:
The latest build 12387 works on the WHR-G300N
There are multiple postings on how to flash.
Best method I've had for first flashing was TFTP flash.
After that, you can update via the web interface. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
Posted: Sat Jul 04, 2009 8:16 Post subject: No TFTP flashing window?
After several hours of futile attempts to catch the right flashing moment with WHR-G300N (either through cmd command or TFTP GUI) I have to declare that the described TFTP procedure is not working on my router. Router is completely unresponsive to pings or any other TCP/IP requests for at least 30 seconds - until the moment when it is up and fully functional (with Buffalo's default firmware).
The Model description at the bottom claims it is BUF-WHRG300N-01
Before I start pondering the serial cable connection for flashing, does anybody share some other suggestions regarding TFTP flashing?
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Sat Jul 04, 2009 9:55 Post subject:
More info!
What OS? What type of network card?
Have you tried hooking up a switch between the network card and the WHR-G300N?
It took me quite a few tries to do the TFTP
Originally, I could NOT get it to catch on a Vista machine.
Put it on a different XP machine with a different NIC, caught it the first time. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
I can attest as well that it takes a bit of luck to get the TFTP to work with this router.
Initially, I was relying on MAC Cloning to work, so that I could assign the MAC from my old router to my new G300N. That is not needed if you do the following:
Remove power from your cable modem. Remove any battery backup in the cable modem. Wait for 30 or so seconds. Power up your router and plug in the ethernet feed from the cable modem. Let the router boot. Return to the cable modem and reinsert the battery, and plug it in.
When the cable modem boots up, the first device it will see is your router and it'll assign it an IP address.
No more need for MAC Cloning for this case. In general, though, if you need MAC Cloning to work, you are out of luck.
Posted: Mon Jul 06, 2009 5:17 Post subject: TFTP and compound TCP
OK, here is an interesting finding:
Windows Vista, Windows 7 and Windows Server 2008 are all using Compound TCP that delays the initial TCP handshake for so much that all these platforms miss the narrow TFTP timeframe required by routers like WHR-G300N.
Simple TCP drivers on Win XP and Linux work fine - I tried Debian, Suse, Ubuntu and WinXP and they are all able to catch the TFTP window.
May I suggest that we add something like this into the wiki:
In order to catch the narrow window for TFTP flash, you should use platforms with simple TCP/IP implementations that don't have CTCP implemented: WinXP or Linux will do, but not Vista, Win7 or W2K8.[/url]