Paine routing was broken, is fixed now
Hello KD7IYT and AE7Q, We had a sector router misconfigured at the Paine site. When KD7IYT joined the network, it tried to route default gateway out his LAN (it pulled DHCP, which it should never do). The situation's been fixed now. --Bart
Sorry about that. I accidentally applied the wrong settings to the Metal when configuring it yesterday. It caused me to lose connection to the Metal and obviously created more of a problem than I was aware of. After doing a factory reset and re-following the client install directions, I then got it to connect properly. FYI.. Some of the client install directions could use some tweaking as they may be misleading for some. The NTP synchronization step should probably be pushed farther to the end of the directions (after connecting to the network). Also, when configuring the local DHCP server, step 2 needs to define the network address, not the local ethernet address (i.e. 192.168.88.0/24, not 192.168.88.1/24 like it shows). Regards, Kyle On Sun, Feb 22, 2015 at 11:32 AM, Bart Kus <me@bartk.us> wrote:
Hello KD7IYT and AE7Q,
We had a sector router misconfigured at the Paine site. When KD7IYT joined the network, it tried to route default gateway out his LAN (it pulled DHCP, which it should never do).
The situation's been fixed now.
--Bart
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
On Sun, Feb 22, 2015 at 12:04 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
Sorry about that. I accidentally applied the wrong settings to the Metal when configuring it yesterday. It caused me to lose connection to the Metal and obviously created more of a problem than I was aware of. After doing a factory reset and re-following the client install directions, I then got it to connect properly.
This wasn't your fault. The sector should never have been configured to request DHCP from you.
FYI.. Some of the client install directions could use some tweaking as they may be misleading for some. The NTP synchronization step should probably be pushed farther to the end of the directions (after connecting to the network). Also, when configuring the local DHCP server, step 2 needs to define the network address, not the local ethernet address (i.e. 192.168.88.0/24, not 192.168.88.1/24 like it shows).
Fixed. If you check the history on that wiki page, you'll see quite a few edits in the last few days. I clarified some things and introduced some new issues (like the DHCP server network). Tom
Kyle, On a related subject, can we get your node's GPS location so we can add it to the map and real-time signal reporting? --Bart On 2/22/2015 12:59 PM, Tom Hayward wrote:
On Sun, Feb 22, 2015 at 12:04 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
Sorry about that. I accidentally applied the wrong settings to the Metal when configuring it yesterday. It caused me to lose connection to the Metal and obviously created more of a problem than I was aware of. After doing a factory reset and re-following the client install directions, I then got it to connect properly. This wasn't your fault. The sector should never have been configured to request DHCP from you.
FYI.. Some of the client install directions could use some tweaking as they may be misleading for some. The NTP synchronization step should probably be pushed farther to the end of the directions (after connecting to the network). Also, when configuring the local DHCP server, step 2 needs to define the network address, not the local ethernet address (i.e. 192.168.88.0/24, not 192.168.88.1/24 like it shows). Fixed.
If you check the history on that wiki page, you'll see quite a few edits in the last few days. I clarified some things and introduced some new issues (like the DHCP server network).
Tom
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
You bet. Here are the exact coordinates of the antenna location: 48.056665, -122.136877 One question to you, what polarization should I be using? I assumed it is vertical, which is how I currently have my 2 foot ARC dish antenna hooked up. Thank you, Kyle On Sun, Feb 22, 2015 at 1:15 PM, Bart Kus <me@bartk.us> wrote:
Kyle,
On a related subject, can we get your node's GPS location so we can add it to the map and real-time signal reporting?
--Bart
On 2/22/2015 12:59 PM, Tom Hayward wrote:
On Sun, Feb 22, 2015 at 12:04 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
Sorry about that. I accidentally applied the wrong settings to the Metal when configuring it yesterday. It caused me to lose connection to the Metal and obviously created more of a problem than I was aware of. After doing a factory reset and re-following the client install directions, I then got it to connect properly.
This wasn't your fault. The sector should never have been configured to request DHCP from you.
FYI.. Some of the client install directions could use some tweaking as
they may be misleading for some. The NTP synchronization step should probably be pushed farther to the end of the directions (after connecting to the network). Also, when configuring the local DHCP server, step 2 needs to define the network address, not the local ethernet address (i.e. 192.168.88.0/24, not 192.168.88.1/24 like it shows).
Fixed.
If you check the history on that wiki page, you'll see quite a few edits in the last few days. I clarified some things and introduced some new issues (like the DHCP server network).
Tom
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
On Sun, Feb 22, 2015 at 2:25 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
One question to you, what polarization should I be using? I assumed it is vertical, which is how I currently have my 2 foot ARC dish antenna hooked up.
The sectors at the Paine / Snohomish County DEM site are horizontally polarized. At Haystack, they're both horizontal and vertical (MIMO). With the ARC dish, I think you want the connector on the side of the feedhorn, not the one coming out the bottom. You stand to gain 20 dB if you're currently using vertical polarization :-) Tom
Alright, I'm glad I asked. I've been averaging -72dB as-is. I'll make the switch over to the other connector and see how that goes. Thank you! Kyle On Sun, Feb 22, 2015 at 2:52 PM, Tom Hayward <tom@tomh.us> wrote:
On Sun, Feb 22, 2015 at 2:25 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
One question to you, what polarization should I be using? I assumed it is vertical, which is how I currently have my 2 foot ARC dish antenna hooked up.
The sectors at the Paine / Snohomish County DEM site are horizontally polarized. At Haystack, they're both horizontal and vertical (MIMO). With the ARC dish, I think you want the connector on the side of the feedhorn, not the one coming out the bottom. You stand to gain 20 dB if you're currently using vertical polarization :-)
Tom
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
I used to have IP address 44.24.240.173. For the past several months I've had IP address 44.24.240.172. I presumed that someone else grabbed .173 during one of the many periods when my radio was unable to connect. I've updated my own DNS accordingly, but since I think there were entries in the HamWAN DNS servers, I suppose I should go update stuff at portal.hamwan.org. Only thing is, I can't maintain a HamWAN connection for any length of time, although it seems to be a bit better in the past month than in August, when I would go for three weeks at a time without even a momentary connection. On 2015-02-22 12:59, Tom Hayward wrote:
On Sun, Feb 22, 2015 at 12:04 PM, Kyle Burgess <kd7iyt@gmail.com> wrote:
Sorry about that. I accidentally applied the wrong settings to the Metal when configuring it yesterday. It caused me to lose connection to the Metal and obviously created more of a problem than I was aware of. After doing a factory reset and re-following the client install directions, I then got it to connect properly. This wasn't your fault. The sector should never have been configured to request DHCP from you.
FYI.. Some of the client install directions could use some tweaking as they may be misleading for some. The NTP synchronization step should probably be pushed farther to the end of the directions (after connecting to the network). Also, when configuring the local DHCP server, step 2 needs to define the network address, not the local ethernet address (i.e. 192.168.88.0/24, not 192.168.88.1/24 like it shows). Fixed.
If you check the history on that wiki page, you'll see quite a few edits in the last few days. I clarified some things and introduced some new issues (like the DHCP server network).
Tom
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
participants (4)
-
Bart Kus -
Dean Gibson AE7Q -
Kyle Burgess -
Tom Hayward