<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Applied.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Ich habe das anfangs ähnlich gesehen, deshalb habe ich erst etwas daran geändert, als sich die Anfragen gehäuft haben…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> franken-dev [mailto:franken-dev-bounces@freifunk.net] <b>On Behalf Of </b>Fabian Bläse<br><b>Sent:</b> Donnerstag, 25. Oktober 2018 16:05<br><b>To:</b> Adrian Schmutzler <freifunk@adrianschmutzler.de>; franken-dev@freifunk.net<br><b>Subject:</b> Re: [PATCH] fff-network: Make CLIENT default status for one-/two-port devices<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p><span style='font-family:"Calibri",sans-serif'>Hallo Adrian,</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>ich finde für jede der möglichen Portkombinationen mindestens einen Grund, warum man das als default haben wollen würde. Daher wäre eigentlich "aktuelles Verhalten beibehalten" für mich das naheliegende.</span><o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Geräte können ja immer auch per Link-Local Adresse + ssh konfiguriert werden. Sowohl auf BATMAN, WAN, als auch CLIENT.</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Aber da es mir schlussendlich egal ist und CLIENT vermutlich doch das sinnvollste ist, weil man im Zweifel von dort aus auf jedem bekannten Weg (WebUI, ssh, ..) in jeden Modus kommt...</span><o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Reviewed-by: Fabian Bläse <<a href="mailto:fabian@blaese.de">fabian@blaese.de</a>></span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>Fabian</span> <o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>On 19.09.18 00:44, Adrian Schmutzler wrote:</span> <br><span style='font-family:"Calibri",sans-serif'>> The V2 firmware requires initialization of the WiFi interfaces</span> <br><span style='font-family:"Calibri",sans-serif'>> by a hood file. If a one-port (or two-port) device is isolated,</span> <br><span style='font-family:"Calibri",sans-serif'>> it won't get this information from other WiFi nodes (w2sta mode).</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> In addition, it cannot be connected to the internet, as this would</span> <br><span style='font-family:"Calibri",sans-serif'>> require the port to be in WAN mode. It is also not possible to</span> <br><span style='font-family:"Calibri",sans-serif'>> connect a client device for configuration, since WiFi is not</span> <br><span style='font-family:"Calibri",sans-serif'>> configured and the LAN port is in BATMAN mode.</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> To enable configuration of an isolated one-port/two-port device,</span> <br><span style='font-family:"Calibri",sans-serif'>> this patch thus changes the default port config to CLIENT, so</span> <br><span style='font-family:"Calibri",sans-serif'>> the user can choose the desired configuration more easily.</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> For two-port, we will have one port WAN and the second port</span> <br><span style='font-family:"Calibri",sans-serif'>> CLIENT.</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> Fixes #110</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> Signed-off-by: Adrian Schmutzler <<a href="mailto:freifunk@adrianschmutzler.de">freifunk@adrianschmutzler.de</a>></span> <br><span style='font-family:"Calibri",sans-serif'>> ---</span> <br><span style='font-family:"Calibri",sans-serif'>> src/packages/fff/fff-network/ar71xx/network.mode | 4 ++--</span> <br><span style='font-family:"Calibri",sans-serif'>> 1 file changed, 2 insertions(+), 2 deletions(-)</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><br><span style='font-family:"Calibri",sans-serif'>> diff --git a/src/packages/fff/fff-network/ar71xx/network.mode b/src/packages/fff/fff-network/ar71xx/network.mode</span> <br><span style='font-family:"Calibri",sans-serif'>> index 09cd715f..f3a27939 100644</span> <br><span style='font-family:"Calibri",sans-serif'>> --- a/src/packages/fff/fff-network/ar71xx/network.mode</span> <br><span style='font-family:"Calibri",sans-serif'>> +++ b/src/packages/fff/fff-network/ar71xx/network.mode</span> <br><span style='font-family:"Calibri",sans-serif'>> @@ -22,9 +22,9 @@</span> <br><span style='font-family:"Calibri",sans-serif'>> ## For example this is the case for: gl-ar150, tl-mr3020-v1, tl-wa850re-v1,</span> <br><span style='font-family:"Calibri",sans-serif'>> ## tl-wa860re-v1, tl-wa901nd-v2, ubnt-bullet-m, ubnt-loco-m-xw, ubnt-nano-m,</span> <br><span style='font-family:"Calibri",sans-serif'>> ## ubnt-unifi</span> <br><span style='font-family:"Calibri",sans-serif'>> -ETHMODE="BATMAN"</span> <br><span style='font-family:"Calibri",sans-serif'>> +ETHMODE="CLIENT"</span> <br><span style='font-family:"Calibri",sans-serif'>> ## Devices featuring 2 ethernet ports are configured by SPECIFIERs ressembling</span> <br><span style='font-family:"Calibri",sans-serif'>> ## the labels on the PORT itself. For the cpe210 these are called LAN0 and LAN1.</span> <br><span style='font-family:"Calibri",sans-serif'>> ## Therefore they are configured as follows:</span> <br><span style='font-family:"Calibri",sans-serif'>> LAN0MODE="WAN"</span> <br><span style='font-family:"Calibri",sans-serif'>> -LAN1MODE="BATMAN"</span> <br><span style='font-family:"Calibri",sans-serif'>> +LAN1MODE="CLIENT"</span> <br><span style='font-family:"Calibri",sans-serif'>> </span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div></div></body></html>