Broadband-Hamnet™ Forum :: Hardware
Welcome Guest   [Register]  [Login]
 Subject :Not quite bricked, but...... 2014-05-06- 16:55:06 
NV8A
Member
Joined: 2014-05-06- 12:08:22
Posts: 3
Location

I already had a WRT54G ver. 1 running as a node -- only problem is that one of the micro coax antenna cables pulled out of the connector. I then picked up a WRT54GS (ver. 1; Serial No. starts with CGN1) and installed bbhn-1.0.0-wrt54gs.bin. Everything was fine until I tried switching it from a node to an access point: I changed the mode and saved the setting and rebooted without first changing the IP address as well. Now I can see its SSID with a WiFi scanner, but I cannot get into the configuration page or even discover what IP it's using: it's connected to the ethernet port of a Windows 7 laptop, but neither

arp -a

nor a ping scanner on the whole 172.x.x.x range finds anything, so I don't know what IP address I would have to use to upload the firmware again using tftp.

I've tried both the regular reset and the 30-30-30 reset to no avail.

Am I going to have to use JTAG on this thing?

IP Logged
 Subject :Re:Not quite bricked, but...... 2014-05-06- 17:06:01 
KF5JIM
Future Astronaut
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland

Question has already been asked many times on the forum before. You can also find your answer on the website. Please check FAQ --> Network FAQs --> I changed my unit to mesh AP and I can't get back in

or

User Documentation --> How to use the web interface --> Mesh Access Point considerations

IP Logged
My opinions and views expressed here are solely my own.
 Subject :Re:Not quite bricked, but...... 2014-05-07- 14:07:31 
NV8A
Member
Joined: 2014-05-06- 12:08:22
Posts: 3
Location

Thanks for that information. I had searched for the word "brick" without finding what I needed.

However, I still did not find the solution to my problems. I still am unable to access the WRT54GS that is now an access point -- not by connecting to it directly at 172.27.0.100 and not by connecting it by ethernet cable to the router that is operating as a mesh node then pointing the browser to 172.27.0.2:8080. In fact even the one that is a mesh node is accessible not at 172.27.0.1:8080 but at 10.110.144.121:8080 (and I am sure that I did not change it to that); the one that is now an access point is not accessible at 10.110.144.122:8080 when connected by ethernet cable to the other one either: in fact

arp -a

shows 10.110.144.122 as the address of the laptop's Ethernet interface and shows nothing with a MAC address corresponding to that of the access point.

A further problem is that the WiFi scanner sees the access point on Channel 6 rather than on Channel 1. I did not change it from whatever the bhnn firmware set it to: the only things I changed were the SSID and then, when it was working OK as a mesh node, I changed it to an access point without changing anything else -- not even the IP address.

IP Logged
Last Edited On: 2014-05-07- 14:11:31 By NV8A for the Reason
 Subject :Re:Not quite bricked, but...... 2014-05-07- 14:33:30 
KF5JIM
Future Astronaut
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland

Have you tried plugging the two nodes together via an Ethernet cable, and either connecting via wireless or a hard Ethernet cable connection to the AP, and navigating to http://172.27.0.2:8080/ ?

IP Logged
My opinions and views expressed here are solely my own.
 Subject :Re:Not quite bricked, but...... 2014-05-07- 15:38:22 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location

Try setting the ip of the computer manually.

the old 2 node trick is no longer valid because the AP now gives 10.x address unless you put in NAT mode.

IP Logged
Note: Most posts submitted from iPhone
 Subject :Re:Re:Not quite bricked, but...... 2014-05-08- 03:14:06 
NV8A
Member
Joined: 2014-05-06- 12:08:22
Posts: 3
Location
[KF5JIM 2014-05-07- 14:33:30]:

Have you tried plugging the two nodes together via an Ethernet cable, and either connecting via wireless or a hard Ethernet cable connection to the AP, and navigating to http://172.27.0.2:8080/ ?

Yes. Nothing accessible at http://172.27.0.2:8080 or even at http://172.27.0.1:8080. The one that is still configured as a mesh node is accessible at http://10.110.144.121:8080 but 10.110.144.122 is the IP address of the laptop's Ethernet interface when I am connected to that Linksys device.
I have discovered that I can in fact get a WiFi connection to the one that is in access point mode, but there doesn't seem to be anything I can do with it. Win7's Network Connection Details shows an Autoconfiguration IPv4 Address of 169.254.95.52 with a Subnet Mask of 255.255.0.0, but
arp -a
gives me
"Interface: 169.254.95.52 --- 0xe
Internet Address      Physical Address      Type
169.254.255.255       ff-ff-ff-ff-ff-ff     static    
224.0.0.22            01-00-5e-00-00-16     static    
224.0.0.251           01-00-5e-00-00-fb     static    
224.0.0.252           01-00-5e-00-00-fc     static    
239.255.255.250       01-00-5e-7f-ff-fa     static    
255.255.255.255       ff-ff-ff-ff-ff-ff     static"
IOW, there is no IP address corresponding to the physical (MAC) address of the Linksys device.
Another thing: Not only is the one that is in access point mode on Channel 6 rather than on Channel 1, but its SSID is no longer "NV8A-3" as I had named it but "BroadbandHamnet-v1".
IP Logged
 Subject :Re:Not quite bricked, but...... 2014-05-08- 05:50:19 
KF5JIM
Future Astronaut
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland

Try this...(I just thought of this)
Go into failsafe mode (we divert after we type "mount_root") on the "not-quite-bricked" router, and in the /etc/nvram file, change/add a line that reads "config=MESH". Next, copy and paste the contents of the /etc/config.mesh/ folder over to the /etc/config/ folder (overwriting everything). Then, reboot.

If that fails to work, the only other option I can think of is to tftp the firmware back to the router.

IP Logged
My opinions and views expressed here are solely my own.
 Subject :Re:Not quite bricked, but...... 2014-05-08- 07:39:35 
KC5DFC
Member
Joined: 2012-03-10- 08:01:04
Posts: 1
Location

You could try using Wireshark to capture the ip when the node boots up.  I have used this on many routers that I do not know the IP, or failed to write down when I configured for some test.  Just direct connect to it and fire up the software on the correct interface and the unit should announce it's IP shortly after you apply power.

IP Logged
Page # 


Powered by ccBoard


SPONSORED AD: