my wireless mac after a reset is showing 00:1D:73:74:09:EC how would i go about setting that up?its not the same sequence since mine is letters. do i just do :
nvram set wan_hwaddr=00:1D:73:74:08:EB
nvram set lan_hwaddr=00:1D:73:74:07:EA
nvram set et0macaddr=00:1D:73:74:07:EA
nvram set et0macaddr_safe=00:1D:73:74:07:EA
my wireless mac after a reset is showing 00:1D:73:74:09:EC how would i go about setting that up?its not the same sequence since mine is letters. do i just do :
nvram set wan_hwaddr=00:1D:73:74:08:EB
nvram set lan_hwaddr=00:1D:73:74:07:EA
nvram set et0macaddr=00:1D:73:74:07:EA
nvram set et0macaddr_safe=00:1D:73:74:07:EA
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Sun Jan 17, 2010 22:05 Post subject:
Sorry - was sleeping!
Yep - that should work fine.
Don't forget the nvram commit and a router reboot.
Also add the gpio disable 14 command if you want the security LED on. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
still not working for me. let me try again since your awake =)
once the commands are on...do you presss RUN Command, save start up save shutdown or save custom script?
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Sun Jan 17, 2010 22:10 Post subject:
You run the commands.
THEN you press SAVE Startup
THEN you reboot the router and make sure those settings show up in the Sys-Info. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
THEN you reboot the router and make sure those settings show up in the Sys-Info.
ok i will do this right now. is the securtiy light supposed to stay lit with the script running? or just when you first run it? i notice the light goes away after a reboot
ok got the script working but still no internet running into my RB. what other factors can be affecting this. im still seeing one wireless SSID. and i know its connecting to my RB since its closer to my computer and its not getting any internet. but once i power off the rb it switches to my AP
Having gone through this thread in its entirety and tested the script provided by DoesItMatter as well as the older scripts (such as the one mrg666 recommends),
I believe this router itself is VERY hit or miss based.
These scripts do *not* work on either of my routers. Implementing the scripts causes all traffic passing to the WAN to halt. I can do dns lookups. I can reach the WAN from the ROUTER, but I cannot reach WAN from clients.
I have 3 whrg300s that have had the issues and I can reliably reproduce the failures every single time.
If any of the devs or gurus want to start doing more advanced testing or anything, send me a pm with aim/icq/yahoo/whatever. I have multiple providers so communicating via an IM protocol would be faster than doing this over forums left and right.
Having gone through this thread in its entirety and tested the script provided by DoesItMatter as well as the older scripts (such as the one mrg666 recommends),
I believe this router itself is VERY hit or miss based.
These scripts do *not* work on either of my routers. Implementing the scripts causes all traffic passing to the WAN to halt. I can do dns lookups. I can reach the WAN from the ROUTER, but I cannot reach WAN from clients.
I have 3 whrg300s that have had the issues and I can reliably reproduce the failures every single time.
If any of the devs or gurus want to start doing more advanced testing or anything, send me a pm with aim/icq/yahoo/whatever. I have multiple providers so communicating via an IM protocol would be faster than doing this over forums left and right.
maybe people having success with bridging are just using N-only?
Having gone through this thread in its entirety and tested the script provided by DoesItMatter as well as the older scripts (such as the one mrg666 recommends),
I believe this router itself is VERY hit or miss based.
These scripts do *not* work on either of my routers. Implementing the scripts causes all traffic passing to the WAN to halt. I can do dns lookups. I can reach the WAN from the ROUTER, but I cannot reach WAN from clients.
I have 3 whrg300s that have had the issues and I can reliably reproduce the failures every single time.
If any of the devs or gurus want to start doing more advanced testing or anything, send me a pm with aim/icq/yahoo/whatever. I have multiple providers so communicating via an IM protocol would be faster than doing this over forums left and right.
maybe people having success with bridging are just using N-only?
In this case, that would not make a difference. N only has no impact on the overall mac issue that has been affecting this router.
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Wed Jan 20, 2010 9:57 Post subject:
Right... but isn't the issue that DD-WRT is having issues with same MACS?
If you're running 2 or more with DD-WRT and change it within DD-WRT, then
to the firmware - it looks like the MAC you assigned it correct?
How else are you detecting the MACS?
If you have a utility that can pull these out or a way to find them,
can you please add to this with a link or how-to? _________________ 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: Thu Jan 21, 2010 6:35 Post subject:
I found you do NOT need to do 30-30-30 reset on this device.
All you need to do is hold the reset button in for about 25 seconds until all the lights are flashing.
Let go, and wait for about 1 minute, then you should be able to access the web gui. _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
If you have a utility that can pull these out or a way to find them,
can you please add to this with a link or how-to?
In general, the best way to properly check anything network related is by using a network analyzer such as Wireshark (http://www.wireshark.org/).
Still, being lazy like I am and since you also have more than one router at your disposal, by far the easiest way to check the actual MACs assigned to a router is by connecting it to another router and see the MACs that appear there.
(For instance put your WAN connection type to DHCP, connect it to the other router and check under Status->Lan which MAC appears for the IP just leased.
If you want to check the Wireless MAC, just configure your router SSID with a unique name and in the other router go to Status->Wireless->Site Survey and see which MAC appears in front of that unique SSID.)
All in all, I am always favorable to anything that simplifies the amount of work needed to perform a task