<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Well, you're OK to have a bridge too. In that case, whatever is on
the Ethernet side of that modem will pull DHCP from the sector
directly, and not be behind a NAT.<br>
<br>
--Bart<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/31/2019 10:47 PM, Randy Neals
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHDTD7qUsziBP9BoV8YYQTqEtB3t9C5UXG=ULtMHzfLDf1Oz9g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div dir="auto">Steve,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Your client radio (DynaDish5) should have two DHCP
configurations. DHCP Client and DHCP Server.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Your wlan interface should be configured as a
“station”, and in that mode you attach the DHCP Client to the
WLAN interface.</div>
<div dir="auto"><br>
</div>
<div dir="auto">There should be no bridge on a DynaDish.</div>
<div dir="auto">There’s nothing to bridge as you will be routing
between the Wlan interface and the Ethernet interface, along
with network address translation.</div>
<div dir="auto"><br>
</div>
<div dir="auto">The client configurations on the website are
generally correct for most installations.</div>
<div dir="auto">There are some steps that would be better if in a
different order, but not too far off.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Feb 14, 2019 at 3:24
PM Steve - WA7PTM <<a href="mailto:psdr-list@aberle.net"
moz-do-not-send="true">psdr-list@aberle.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks to
Doug, we determined that dhcp on this unit needs to point to
<br>
the "bridge" as opposed to the "wlan1" interface. That
change got the <br>
DynaDish connected last night, but there are still some DNS
issues to be <br>
resolved before it is fully functional.<br>
<br>
Hopefully, we will end up with an improved set of
step-by-step instructions.<br>
<br>
Steve<br>
<br>
<br>
Doug Kingston wrote on 2/13/19 12:08 PM:<br>
> I can take care of these updates. I'll work with
Steve.<br>
> <br>
> -Doug-<br>
> <br>
> On Wed, Feb 13, 2019 at 12:00 PM Steve - WA7PTM <<a
href="mailto:psdr-list@aberle.net" target="_blank"
moz-do-not-send="true">psdr-list@aberle.net</a>><br>
> wrote:<br>
> <br>
>> Is anyone maintaining the<br>
>><br>
>> <a
href="https://www.hamwan.org/Standards/Network%20Engineering/Client%20Node%20Configuration.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.hamwan.org/Standards/Network%20Engineering/Client%20Node%20Configuration.html</a><br>
>> web page?<br>
>><br>
>> The reasons I ask are:<br>
>><br>
>> • Step 1 will not work as listed as the command is
wrong (should be<br>
>> "/system package update install" in RouterOS
v6.43.12) and if some<br>
>> preliminary steps are not taken (moving the default
network to one<br>
>> connected to the Internet with a "/ip address add
address=a.b.c.d/xx<br>
>> interface=ether1" command and establishing a
default gateway with a "/ip<br>
>> route add gateway <a href="http://a.b.c.gw"
rel="noreferrer" target="_blank" moz-do-not-send="true">a.b.c.gw</a>"
command), then the update will fail.<br>
>><br>
>> • Step 21 on a Dynadish5 results in a "failure:
incompatible band and<br>
>> channel-width" message unless "channel-width=5mhz"
is added to the command.<br>
>><br>
>> • Step 22 on a Dynadish5 results in a "failure: can
not run on slave<br>
>> interface" message.<br>
>><br>
>> This last one has me stumped, and I have been
unable to determine a<br>
>> workaround. Has anyone else encountered and solved
this problem?<br>
>><br>
>> Thanks,<br>
>> Steve<br>
>><br>
>><br>
>> _______________________________________________<br>
>> PSDR mailing list<br>
>> <a href="mailto:PSDR@hamwan.org" target="_blank"
moz-do-not-send="true">PSDR@hamwan.org</a><br>
>> <a
href="http://mail.hamwan.net/mailman/listinfo/psdr"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>
>><br>
> <br>
> <br>
> _______________________________________________<br>
> PSDR mailing list<br>
> <a href="mailto:PSDR@hamwan.org" target="_blank"
moz-do-not-send="true">PSDR@hamwan.org</a><br>
> <a href="http://mail.hamwan.net/mailman/listinfo/psdr"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>
> <br>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank"
moz-do-not-send="true">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.net/mailman/listinfo/psdr"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>
</blockquote>
</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Sent from mobile.</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PSDR mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a>
<a class="moz-txt-link-freetext" href="http://mail.hamwan.net/mailman/listinfo/psdr">http://mail.hamwan.net/mailman/listinfo/psdr</a>
</pre>
</blockquote>
<br>
</body>
</html>