[HamWAN PSDR] Another new guy

Nigel Vander Houwen nigel at k7nvh.com
Thu Feb 27 22:00:07 PST 2014


Beat me to it Cory!

In any case, like Cory said, it will be specific to your individual situation (which is why it's not in our instructions), so hop in the channel, and we can help get you set up!

Nigel

On Feb 27, 2014, at 9:58 PM, Cory (NQ1E) <cory at nq1e.hm> wrote:

> Hi Bob,
> 
> Your device is online and able to reach all the way out to the
> internet though the HamWAN network.  However, the Ethernet port side
> of your device doesn't have an IP address assigned to it, so it won't
> be able to route any traffic yet.
> 
> The rest of the configuration depends on how you want to connect it to
> your network.  Join the chat room when you're ready to work on that
> and we can help you out with it in real-time.
> 
> http://webchat.freenode.net/?nick=HamWAN..&channels=#HamWAN
> 
> -Cory
> NQ1E
> 
> 
> [NQ1E at KE7JL-Capitol-Park] > /system resource print
>                   uptime: 10h49m31s
>                  version: 6.7
>               build-time: Nov/29/2013 13:37:20
>              free-memory: 41.0MiB
>             total-memory: 64.0MiB
>                      cpu: MIPS 24Kc V7.4
>                cpu-count: 1
>            cpu-frequency: 400MHz
>                 cpu-load: 4%
>           free-hdd-space: 110.8MiB
>          total-hdd-space: 128.0MiB
>  write-sect-since-reboot: 260
>         write-sect-total: 589
>               bad-blocks: 0%
>        architecture-name: mipsbe
>               board-name: RB Metal 5SHPn
>                 platform: MikroTik
> [NQ1E at KE7JL-Capitol-Park] >
> [NQ1E at KE7JL-Capitol-Park] > ping google.com
> HOST                                     SIZE TTL TIME  STATUS
> 173.194.33.72                              56  55 107ms
> 173.194.33.72                              56  55 163ms
> 173.194.33.72                              56  55 257ms
>    sent=3 received=3 packet-loss=0% min-rtt=107ms avg-rtt=175ms max-rtt=257ms
> 
> [NQ1E at KE7JL-Capitol-Park] >
> [NQ1E at KE7JL-Capitol-Park] > /tool traceroute 8.8.8.8
> # ADDRESS                          LOSS SENT    LAST     AVG    BEST
> WORST STD-DEV STATUS
> 1 44.24.240.17                       0%    3   9.3ms    14.8     6.3
>  28.8      10
> 2 44.24.240.6                        0%    3   7.3ms    17.1     3.3
>  40.8    16.8
> 3 44.24.240.78                       0%    3  18.2ms      33    14.4
>  66.3    23.6
> 4 44.24.242.8                        0%    3   125ms   136.6     124
> 160.8    17.1
> 5 198.178.136.1                      0%    3 110.3ms   103.7    48.9
> 151.9    42.3
> 6 204.13.9.1                         0%    3 106.3ms    80.5    66.9
> 106.3    18.2
> 7 157.130.180.45                     0%    3   109ms   126.1     109
> 151.9    18.5
> 8                                  100%    3 timeout
> 9 152.63.84.14                       0%    3 118.8ms   135.7   118.8
> 150.5      13
> 10 152.179.241.10                     0%    3 171.1ms   187.1   139.4
> 250.7    46.8
> 11 72.14.239.100                      0%    3 164.1ms   162.8   161.5
> 164.1     1.3
> 12 66.249.94.20                       0%    2 204.9ms   215.1   204.9
> 225.3    10.2 <MPLS:L=367096,E=4>
> 13 64.233.174.133                     0%    2 309.2ms   253.1     197
> 309.2    56.1
> 14                                  100%    2 timeout
> 15 8.8.8.8                            0%    2 158.9ms   230.7   158.9
> 302.4    71.8
> 
> [NQ1E at KE7JL-Capitol-Park] >
> [NQ1E at KE7JL-Capitol-Park] > /ip address print
> Flags: X - disabled, I - invalid, D - dynamic
> #   ADDRESS            NETWORK         INTERFACE
> 0 D 44.24.240.27/28    44.24.240.16    wlan1-gateway
> [NQ1E at KE7JL-Capitol-Park] >
> 
> On Thu, Feb 27, 2014 at 9:28 PM, Bob <ke7jl at comcast.net> wrote:
>> Once I understood that that I needed to use the terminal it was easy, just a
>> matter of copy and paste.  I did keep notes that I will be happy to share.
>> 
>> My next goal is to be able to be able to get my RMS Gateway connected to the
>> WL2K CMSs.  As I am currently configured I cannot seem to get out to the
>> internet.  Any ideas?
>> 
>> Bob
>> 
>> -----Original Message-----
>> From: PSDR [mailto:psdr-bounces at hamwan.org] On Behalf Of Nigel Vander Houwen
>> Sent: Thursday, February 27, 2014 6:22 PM
>> To: Puget Sound Data Ring
>> Subject: Re: [HamWAN PSDR] Another new guy
>> 
>> Hello Bob,
>> 
>> It's looking like you managed to connect! I see your modem associated with
>> the site at Capitol Park! Congratulations!
>> 
>> Nigel
>> _______________________________________________
>> PSDR mailing list
>> PSDR at hamwan.org
>> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
>> 
>> 
>> _______________________________________________
>> PSDR mailing list
>> PSDR at hamwan.org
>> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
> 
> _______________________________________________
> PSDR mailing list
> PSDR at hamwan.org
> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org





More information about the PSDR mailing list