|
Broadband-Hamnet™ Forum |
|
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-15- 07:04:51
|
|
|
| W5LMM |
|
| Member |
 |
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
Never mind..
It was a MISCONFIGURATION on the 5Ghz Radio end! |
IP Logged
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-13- 14:08:57
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
eth0.0 Link encap:Ethernet HWaddr 00:13:10:8F:07:77
inet addr:10.19.66.231 Bcast:10.19.66.255 Mask:255.255.255.0
inet6 addr: fe80::213:10ff:fe8f:777/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:389270 errors:0 dropped:0 overruns:0 frame:0
TX packets:1301 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43036498 (41.0 MiB) TX bytes:135488 (132.3 KiB)
eth0.1 Link encap:Ethernet HWaddr 00:13:10:8F:07:77
inet addr:44.30.255.51 Bcast:44.30.255.55 Mask:255.255.255.248
inet6 addr: fe80::213:10ff:fe8f:777/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1259 errors:0 dropped:0 overruns:0 frame:0
TX packets:20055 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:185443 (181.0 KiB) TX bytes:923264 (901.6 KiB)
wl0 Link encap:Ethernet HWaddr 00:13:10:8F:07:79
inet addr:10.143.7.121 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::213:10ff:fe8f:779/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:909867 dropped:0 overruns:0 frame:1125403
TX packets:42704 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:3160787 (3.0 MiB)
Interrupt:4 Base address:0x1000
root@W5LMM-HSMM-1:~# arping -i eth0.1 44.30.255.49
ARPING to 44.30.255.51 from 44.30.255.51 via eth0.1
^^^^^^^^^^^^ ^^^^^^^^^^^^
Weird, or not??
Sent 9 probe(s) (9 broadcast(s))
Received 0 reply (0 request(s), 0 broadcast(s)) |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-13- 06:10:40
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
So, thinking that the problem may be my use of the 10.x for my LAN interface, I changed it on both the BBHN node to 192.168.1.2 and the PC 192.168.1.5 , and....
Same behavior as before. |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-12- 10:44:29
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
Yeah this is seriously driving me looney. It should work. As far as I can tell, everything is setup correctly. It's happening internally to the BBHN node. |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Let's build this in the Phila / Southern NJ area..
2017-02-12- 09:42:49
|
|
|
|
|
|
|
Subject :Re:Let's build this in the Phila / Southern NJ area..
2017-02-12- 09:42:41
|
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-11- 14:56:42
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
So I tried swapping interfaces, ie. putting the HamWan device on the LAN interface, and my LAN connected to the WAN interface on the BBHN node.
SAME behavior as before. Nothing passes beyond the interface connected to the HamWan radio.
Like I said, if I connect the HamWan radio to a PC, I can pass right through the NIC to the radio, and out onto the 44network.
I don't understand why the BBHN node is blocking traffic at the interface. |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Routing issues..
2017-02-11- 08:47:44
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
SO I am certain the problem is WITHIN the BBHN Node itself.
If I connect the HamWan interface to a PC, I can get right out.
If I have the HamWan interface connected to the wan port on the BBHN node, from SSH within that node, I cannot ping the radio! So traffic is not going past the wan port interface ON the node itself.
Any idea on where I should be looking?
THanks!! |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Linksys wrt54g, backfire 10.03 and channel 0, -1..
2017-02-11- 05:44:23
|
|
|
| ES1ALV |
|
| Member |
|
Joined: 2015-03-03- 03:48:31
Posts: 3
Location: |
|
|
|
|
|
Forum :
Hardware
Topic :
Linksys wrt54g, backfire 10.03 and channel 0, -1
Managed to patch b43 drivers from OpenWrt Backfire 10.03, generate new regulatory.bin to extend allowed ranges and patch wpad-mini hotspot service.
Two routers were running on channel 0, one was AP, another client. They were able to ping each other. |
|
IP Logged
|
|
|
|
|
|
Subject :Routing issues..
2017-02-10- 15:37:15
|
|
|
| W5LMM |
|
|
| Member |
|
Joined: 2012-02-13- 18:18:04
Posts: 126
Location: Albuquerque, NM |
|
|
|
|
|
Forum :
Problems & Answers
Topic :
Routing issues
I am trying to figure out how to route from my LAN through a BBHN node out to the 44.net which is accessed through my HamWan node. For those that don't know about HamWan it's a point to point 5.8Ghz ham network and very robust. (http://hamwan.org) Anyhow, for the HamWan network, I have been assigned 44.30.255.48/29 which yields 44.30.255.49 - 44.30.255.54 and a netmask of 255.255.255.248
I have the LAN port of the BBHN node connected to the LAN with a static IP Address and it is accessible from anywhere on my LAN. I have the WAN port connected to the HamWan radio, with IP address of 44.30.255.50 I can see THAT address of that interface, but traffic goes no further for some reason.
On any PC in the LAN, I can route any traffic for 44.0.0.0 to the IP Address of the LAN port of the BBHN node.
Any idea what I am doing wrong?
Here's my config screen.. RIGHT CLICK/VIEW IMAGE
|
|
IP Logged
|
|
Last Edited On: 2017-02-10- 15:54:28 By W5LMM for the Reason
|
|
|
|
|
|
Subject :Linksys wrt54g, backfire 10.03 and channel 0, -1..
2017-02-05- 19:53:20
|
|
|
| ES1ALV |
|
|
| Member |
|
Joined: 2015-03-03- 03:48:31
Posts: 3
Location: |
|
|
|
|
|
Forum :
Hardware
Topic :
Linksys wrt54g, backfire 10.03 and channel 0, -1
Hello and thank you for this interesting project.
I have couple of old unused WRT54G(L) routers and want to experiment with Broadband Hamnet.
Few questions: - Is there any experience with configuring these routers to work out of ISM Wifi channels the same way as with ubq devices, for example on channel 0, -1, etc.
- Looking at OpenWRT source for Backfire 10.03 it seems that there is some room for experiments with b43legacy drivers, which have some problems in psk mode according to OpenWRT wrt54g wiki, but it does not matter for Broadband Hamnet usage as psk is not in use. Anyone has experience with patching b43legacy drivers to make these routers work on channel 0, -1 or can anyone confirm that its HW is capable to tune to these channels?
- Does Broadband Hamnet support Backfire 10.03? Is there any chance to integrate it with this OpenWRT version?
73! |
|
IP Logged
|
|
|
|
|
|
Subject :Linksys wrt54g, backfire 10.03 and channel 0, -1..
2017-02-05- 19:53:04
|
|
|
| ES1ALV |
|
|
| Member |
|
Joined: 2015-03-03- 03:48:31
Posts: 3
Location: |
|
|
|
|
|
Forum :
Hardware
Topic :
Linksys wrt54g, backfire 10.03 and channel 0, -1
Hello and thank you for this interesting project.
I have couple of old unused WRT54G(L) routers and want to experiment with Broadband Hamnet.
Few questions: - Is there any experience with configuring these routers to work out of ISM Wifi channels the same way as with ubq devices, for example on channel 0, -1, etc.
- Looking at OpenWRT source for Backfire 10.03 it seems that there is some room for experiments with b43legacy drivers, which have some problems in psk mode according to OpenWRT wrt54g wiki, but it does not matter for Broadband Hamnet usage as psk is not in use. Anyone has experience with patching b43legacy drivers to make these routers work on channel 0, -1 or can anyone confirm that its HW is capable to tune to these channels?
- Does Broadband Hamnet support Backfire 10.03? Is there any chance to integrate it with this OpenWRT version?
73! |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Webserver..
2017-02-05- 10:35:21
|
|
|
| W9HDG |
|
| Member |
|
Joined: 2013-08-20- 10:35:21
Posts: 17
Location: |
|
|
|
|
|
Forum :
How we used HSMM-MESH™
Topic :
Webserver
Oops!
Apparently my interwebz tubes are plugged up today and I somehow got this posted twice...
My bad... |
|
IP Logged
|
|
Last Edited On: 2017-02-05- 10:37:41 By W9HDG for the Reason Accidentally posted twice
|
|
|
|
|
|
Subject :Re:Webserver..
2017-02-05- 10:35:16
|
|
|
| W9HDG |
|
|
| Member |
|
Joined: 2013-08-20- 10:35:21
Posts: 17
Location: |
|
|
|
|
|
Forum :
How we used HSMM-MESH™
Topic :
Webserver
I was thinking the same there here. I live in the middle of nowhere (The closest Wal-Mart is an hour away). There are 33 hams in the community I live in.
I was thinking of starting with a PBX, try and find some SIP phones (cheap) that I could configure and loan out to other hams. From there goto e-mail, web server, etc.
Could be fun... |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Upgrade WRT54G from bbhn 1.0.0 to 3.1.0..
2017-02-04- 09:22:59
|
|
|
| WD4A |
|
|
| Member |
|
Joined: 2013-07-10- 14:44:14
Posts: 4
Location: Maggie Valley, NC |
|
|
|
|
|
Forum :
Firmware
Topic :
Upgrade WRT54G from bbhn 1.0.0 to 3.1.0
I resolved the issue. Microsoft Edge was changing the suffix from .trx to .man on the 3.1.0 firmware file as it was being saved to my PC. I switched the browser to Firefox which saved the file with the .trx suffix as it should be. Uploads of the new 3.1.0 firmware to the WRT54G nodes proceeded normally after making this discovery.
Al, WD4A |
|
IP Logged
|
|
|
|
|
|
Subject :Re:Upgrade WRT54G from bbhn 1.0.0 to 3.1.0..
2017-02-04- 09:22:44
|
|
|
| WD4A |
|
|
| Member |
|
Joined: 2013-07-10- 14:44:14
Posts: 4
Location: Maggie Valley, NC |
|
|
|
|
|
Forum :
Firmware
Topic :
Upgrade WRT54G from bbhn 1.0.0 to 3.1.0
I resolved the issue. Microsoft Edge was changing the suffix from .trx to .man on the 3.1.0 firmware file as it was being saved to my PC. I switched the browser to Firefox which saved the file with the .trx suffix as it should be. Uploads of the new 3.1.0 firmware to the WRT54G nodes proceeded normally after making this discovery.
Al, WD4A |
|
IP Logged
|
|
|
|
|
|
Subject :Upgrade WRT54G from bbhn 1.0.0 to 3.1.0..
2017-02-04- 04:54:33
|
|
|
| WD4A |
|
|
| Member |
|
Joined: 2013-07-10- 14:44:14
Posts: 4
Location: Maggie Valley, NC |
|
|
|
|
|
Forum :
Firmware
Topic :
Upgrade WRT54G from bbhn 1.0.0 to 3.1.0
I have been away from BBHN for several years. My WRT54G 4-node network is running on 1.0.0. I want to upgrade all nodes to the latest firmware which appears to be 3.1.0. When I visit the firmware download page for Linksys, the only firmware I see to upgrade an exiting mesh node is bbhn-3.1.0-brcm-2.4-squashfs.trx. When I download this file it gets saved under the filename bbhn-3.1.0-brcm-2.4-squashfs.man on my laptop (the suffix changes from .trx to .man). When I use localnode8080 to connect to a node, go to Administration>Firmware Update, select the bbhn-3.1.0-brcom-2.4-squashfs.man file and click Update, I receive an error message saying "Firmware CANNOT be updated - the uploaded file is not recognized." Do I need to upload interim releases instead of trying to go directly from 1.0.0 to 3.1.0? Any help would be appreciated.
Al, WD4A
|
|
IP Logged
|
|
|
|
|
|
Subject :username/password..
2017-01-31- 08:16:03
|
|
|
|
|
|
|
Subject :Re:Can I use this router..
2017-01-28- 00:12:04
|
|
|
| KF5JIM |
|
| Future Astronaut |
 |
Joined: 2013-07-17- 12:13:36
Posts: 250
Location: Nederland |
|
|
|
|
|
|
|
|
Subject :Re:Can I use this router..
2017-01-27- 10:51:06
|
|
|
| NG5V |
|
|
| Admin |
 |
Joined: 2010-01-18- 23:06:23
Posts: 43
Location: |
|
|
|
|
|
Forum :
Hardware
Topic :
Can I use this router
The wrtp54g hardware shows to have enough storage and ram to work. In addition, there are posts in this forum on how to use the existing firmware with an ID byte change. Two items are needed. Do a google search for "device unlock wrtp54g" for the process to become non-vendor specific and upload other firmware. After that, you will need to modify the firmware file to change the ID byte before using our firmware. You can always search for any topic by typing something in the "search" at top right of each page. That starts a full content, dedicated, single site search for anything published here. Be sure and post your results to guide others using this hardware. |
|
IP Logged
|
|
|
|
|
