Translation

(itstool) path: note/para
English
If the driver for the wireless interface is not loaded in the <literal>GENERIC</literal> or custom kernel, and the computer is running FreeBSD 12.1, load the corresponding <filename>.ko</filename> in <filename>/boot/loader.conf</filename> by adding <userinput><replaceable>driver</replaceable>_load="YES"</userinput> to that file and rebooting. Another, better way is to load the driver in <filename>/etc/rc.conf</filename> by adding it to <varname>kld_list</varname> (see <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details) in that file and rebooting. This is needed because otherwise the driver is not loaded yet at the time the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface is set up.
853/7930
Context English Portuguese (Brazil) State
For more detail, type <userinput>show lacp neighbor detail</userinput>. Para mais detalhes, digite <userinput>show lacp neighbor detail</userinput>.
To retain this configuration across reboots, add the following entries to <filename>/etc/rc.conf</filename> on the FreeBSD system: Para manter esta configuração através de reinicializações, adicione as seguintes entradas ao <filename>/etc/rc.conf</filename> no sistema FreeBSD:
ifconfig_<replaceable>fxp0</replaceable>="up"
ifconfig_<replaceable>fxp1</replaceable>="up"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto lacp laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.3/24</replaceable>"
ifconfig_<replaceable>fxp0</replaceable>="up"
ifconfig_<replaceable>fxp1</replaceable>="up"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto lacp laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.3/24</replaceable>"
Failover Mode Modo de Failover
Failover mode can be used to switch over to a secondary interface if the link is lost on the master interface. To configure failover, make sure that the underlying physical interfaces are up, then create the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface. In this example, <replaceable>fxp0</replaceable> is the master interface, <replaceable>fxp1</replaceable> is the secondary interface, and the virtual interface is assigned an <acronym>IP</acronym> address of <replaceable>10.0.0.15/24</replaceable>: O modo de failover pode ser usado para alternar para uma interface secundária se o link for perdido na interface principal. Para configurar o failover, certifique-se de que as interfaces físicas subjacentes estejam ativadas e crie a interface <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry>. Neste exemplo, <replaceable>fxp0</replaceable> é a interface principal, <replaceable>fxp1</replaceable> é a interface secundária e a interface virtual recebeu um endereço <acronym>IP</acronym> de <replaceable>10.0.0.15/24</replaceable>:
<prompt>#</prompt> <userinput>ifconfig <replaceable>fxp0</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>fxp1</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> create</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> up laggproto failover laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.15/24</replaceable></userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>fxp0</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>fxp1</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> create</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> up laggproto failover laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.15/24</replaceable></userinput>
The virtual interface should look something like this: A interface virtual deve ser algo como isto:
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal></userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=8&lt;VLAN_MTU&gt;
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0&lt;&gt;
laggport: fxp0 flags=5&lt;MASTER,ACTIVE&gt;
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal></userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=8&lt;VLAN_MTU&gt;
ether 00:05:5d:71:8d:b8
inet 10.0.0.15 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect
status: active
laggproto failover
laggport: fxp1 flags=0&lt;&gt;
laggport: fxp0 flags=5&lt;MASTER,ACTIVE&gt;
Traffic will be transmitted and received on <replaceable>fxp0</replaceable>. If the link is lost on <replaceable>fxp0</replaceable>, <replaceable>fxp1</replaceable> will become the active link. If the link is restored on the master interface, it will once again become the active link. O tráfego será transmitido e recebido em <replaceable>fxp0</replaceable>. Se o link for perdido em <replaceable>fxp0</replaceable>, <replaceable>fxp1</replaceable> se tornará o link ativo. Se o link for restaurado na interface principal, ele se tornará novamente o link ativo.
To retain this configuration across reboots, add the following entries to <filename>/etc/rc.conf</filename>: Para manter essa configuração através de reinicializações, adicione as seguintes entradas ao <filename>/etc/rc.conf</filename>:
ifconfig_<replaceable>fxp0</replaceable>="up"
ifconfig_<replaceable>fxp1</replaceable>="up"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.15/24</replaceable>"
ifconfig_<replaceable>fxp0</replaceable>="up"
ifconfig_<replaceable>fxp1</replaceable>="up"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover laggport <replaceable>fxp0</replaceable> laggport <replaceable>fxp1</replaceable> <replaceable>10.0.0.15/24</replaceable>"
Failover Mode Between Ethernet and Wireless Interfaces Modo de failover entre interfaces Ethernet e sem fio
For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available. With <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry>, it is possible to configure a failover which prefers the Ethernet connection for both performance and security reasons, while maintaining the ability to transfer data over the wireless connection. Para usuários de laptop, geralmente é desejável configurar o dispositivo sem fio como secundário, que é usado somente quando a conexão Ethernet não está disponível. Com <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry>, é possível configurar um failover que preferia a conexão Ethernet por motivos de desempenho e de segurança, mantendo a capacidade de transferência dados através da conexão sem fio.
This is achieved by overriding the Ethernet interface's <acronym>MAC</acronym> address with that of the wireless interface. Isso é obtido substituindo o endereço <acronym>MAC</acronym> da interface Ethernet com o da interface wireless.
In theory, either the Ethernet or wireless MAC address can be changed to match the other. However, some popular wireless interfaces lack support for overriding the MAC address. We therefore recommend overriding the Ethernet MAC address for this purpose. Em teoria, o endereço MAC da Ethernet ou da wireless pode ser alterado para corresponder ao outro. No entanto, algumas interfaces wireless populares não têm suporte para substituir o endereço MAC. Portanto, recomendamos substituir o endereço MAC da Ethernet para esse fim.
If the driver for the wireless interface is not loaded in the <literal>GENERIC</literal> or custom kernel, and the computer is running FreeBSD 12.1, load the corresponding <filename>.ko</filename> in <filename>/boot/loader.conf</filename> by adding <userinput><replaceable>driver</replaceable>_load="YES"</userinput> to that file and rebooting. Another, better way is to load the driver in <filename>/etc/rc.conf</filename> by adding it to <varname>kld_list</varname> (see <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details) in that file and rebooting. This is needed because otherwise the driver is not loaded yet at the time the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface is set up. Se o driver para a interface wireless não estiver carregado no kernel <literal>GENERIC</literal> ou customizado, e o computador estiver rodando o FreeBSD 12.1, carregue o <filename>.ko</filename> correspondente no arquivo <filename>/boot/loader.conf</filename> adicionando <userinput><replaceable>driver</replaceable>_load="YES"</userinput> e reiniciando a maquina. Outra forma melhor, é carregar o driver no arquivo <filename>/etc/rc.conf</filename> adicionando a variável <varname>kld_list</varname> (veja <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> para maiores detalhes) nesse arquivo e reiniciar. Isso é necessário porque de outra forma o driver não estará carregado no tempo em que a interface <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> for configurada.
In this example, the Ethernet interface, <replaceable>re0</replaceable>, is the master and the wireless interface, <replaceable>wlan0</replaceable>, is the failover. The <replaceable>wlan0</replaceable> interface was created from the <replaceable>ath0</replaceable> physical wireless interface, and the Ethernet interface will be configured with the <acronym>MAC</acronym> address of the wireless interface. First, determine the <acronym>MAC</acronym> address of the wireless interface: Neste exemplo, a interface Ethernet, <replaceable>re0</replaceable>, é a interface principal e a interface sem fio, <replaceable>wlan0</replaceable>, é o failover. A interface <replaceable>wlan0</replaceable> foi criada a partir da interface wireless <replaceable>ath0</replaceable>, e a interface Ethernet será configurada com o endereço <acronym>MAC</acronym> da interface wireless. Primeiro, determine o endereço <acronym>MAC</acronym> da interface wireless:
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable></userinput>
wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
ether b8:ee:65:5b:32:59
groups: wlan
ssid Bbox-A3BD2403 channel 6 (2437 MHz 11g ht/20) bssid 00:37:b7:56:4b:60
regdomain ETSI country FR indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60
protmode CTS ampdulimit 64k ampdudensity 8 shortgi -stbctx stbcrx
-ldpc wme burst roaming MANUAL
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
nd6 options=29&lt;PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL&gt;
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable></userinput>
wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
ether b8:ee:65:5b:32:59
groups: wlan
ssid Bbox-A3BD2403 channel 6 (2437 MHz 11g ht/20) bssid 00:37:b7:56:4b:60
regdomain ETSI country FR indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60
protmode CTS ampdulimit 64k ampdudensity 8 shortgi -stbctx stbcrx
-ldpc wme burst roaming MANUAL
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
nd6 options=29&lt;PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL&gt;
Replace <replaceable>wlan0</replaceable> to match the system's wireless interface name. The <literal>ether</literal> line will contain the <acronym>MAC</acronym> address of the specified interface. Now, change the <acronym>MAC</acronym> address of the Ethernet interface: Substitua <replaceable>wlan0</replaceable> para corresponder ao nome da interface wireless do sistema. A linha <literal>ether</literal> conterá o endereço <acronym>MAC</acronym> da interface especificada. Agora, altere o endereço <acronym>MAC</acronym> da interface Ethernet subjacente:
<prompt>#</prompt> <userinput>ifconfig <replaceable>re0</replaceable> ether <replaceable>b8:ee:65:5b:32:59</replaceable></userinput> <prompt>#</prompt> <userinput>ifconfig <replaceable>re0</replaceable> ether <replaceable>b8:ee:65:5b:32:59</replaceable></userinput>
Bring the wireless interface up (replacing <replaceable>FR</replaceable> with your own 2-letter country code), but do not set an <acronym>IP</acronym> address: Suba a interface sem fio (substituindo <replaceable>FR</replaceable> pelo seu próprio código de país com duas letras), mas não defina um endereço <acronym>IP</acronym>:
<prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> create wlandev <replaceable>ath0</replaceable> country <replaceable>FR</replaceable> ssid <replaceable>my_router</replaceable> up</userinput> <prompt>#</prompt> <userinput>ifconfig <replaceable>wlan0</replaceable> create wlandev <replaceable>ath0</replaceable> country <replaceable>FR</replaceable> ssid <replaceable>my_router</replaceable> up</userinput>
Make sure the <replaceable>re0</replaceable> interface is up, then create the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface with <replaceable>re0</replaceable> as master with failover to <replaceable>wlan0</replaceable>: Certifique-se de que a interface <replaceable>re0</replaceable> esteja ativa, então crie a interface <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> com a <replaceable>re0</replaceable> como master com failover para a<replaceable>wlan0</replaceable>:
<prompt>#</prompt> <userinput>ifconfig <replaceable>re0</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> create</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> up laggproto failover laggport <replaceable>re0</replaceable> laggport <replaceable>wlan0</replaceable></userinput>
<prompt>#</prompt> <userinput>ifconfig <replaceable>re0</replaceable> up</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> create</userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal> up laggproto failover laggport <replaceable>re0</replaceable> laggport <replaceable>wlan0</replaceable></userinput>
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal></userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=8&lt;VLAN_MTU&gt;
ether b8:ee:65:5b:32:59
laggproto failover lagghash l2,l3,l4
laggport: re0 flags=5&lt;MASTER,ACTIVE&gt;
laggport: wlan0 flags=0&lt;&gt;
groups: lagg
media: Ethernet autoselect
status: active
<prompt>#</prompt> <userinput>ifconfig <literal>lagg<replaceable>0</replaceable></literal></userinput>
lagg0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
options=8&lt;VLAN_MTU&gt;
ether b8:ee:65:5b:32:59
laggproto failover lagghash l2,l3,l4
laggport: re0 flags=5&lt;MASTER,ACTIVE&gt;
laggport: wlan0 flags=0&lt;&gt;
groups: lagg
media: Ethernet autoselect
status: active
Then, start the <acronym>DHCP</acronym> client to obtain an <acronym>IP</acronym> address: Em seguida, inicie o cliente <acronym>DHCP</acronym> para obter um endereço <acronym>IP</acronym>:
<prompt>#</prompt> <userinput>dhclient <literal>lagg<replaceable>0</replaceable></literal></userinput> <prompt>#</prompt> <userinput>dhclient <literal>lagg<replaceable>0</replaceable></literal></userinput>
ifconfig_<replaceable>re0</replaceable>="ether <replaceable>b8:ee:65:5b:32:59</replaceable>"
wlans_<replaceable>ath0</replaceable>="wlan0"
ifconfig_wlan0="WPA"
create_args_wlan0="country <replaceable>FR</replaceable>"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="up laggproto failover laggport <replaceable>re0</replaceable> laggport wlan0 DHCP"
ifconfig_<replaceable>re0</replaceable>="ether <replaceable>b8:ee:65:5b:32:59</replaceable>"
wlans_<replaceable>ath0</replaceable>="wlan0"
ifconfig_wlan0="WPA"
create_args_wlan0="country <replaceable>FR</replaceable>"
cloned_interfaces="<literal>lagg<replaceable>0</replaceable></literal>"
ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="up laggproto failover laggport <replaceable>re0</replaceable> laggport wlan0 DHCP"
Diskless Operation with <acronym>PXE</acronym> Operação Diskless com <acronym>PXE</acronym>
<personname> <firstname>Jean-François</firstname> <surname>Dockès</surname> </personname> <contrib>Updated by </contrib> <personname> <firstname> Jean-François </firstname> <surname> Dockès </surname> </personname> <contrib> Atualizado por </contrib>
<personname> <firstname>Alex</firstname> <surname>Dupre</surname> </personname> <contrib>Reorganized and enhanced by </contrib> <personname> <firstname> Alex </firstname> <surname> Dupre </surname> </personname> <contrib> Reorganizado e aprimorado por </contrib>

Loading…

If the driver for the wireless interface is not loaded in the <literal>GENERIC</literal> or custom kernel, and the computer is running FreeBSD 12.1, load the corresponding <filename>.ko</filename> in <filename>/boot/loader.conf</filename> by adding <userinput><replaceable>driver</replaceable>_load="YES"</userinput> to that file and rebooting. Another, better way is to load the driver in <filename>/etc/rc.conf</filename> by adding it to <varname>kld_list</varname> (see <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details) in that file and rebooting. This is needed because otherwise the driver is not loaded yet at the time the <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> interface is set up.
Se o driver para a interface wireless não estiver carregado no kernel <literal>GENERIC</literal> ou customizado, e o computador estiver rodando o FreeBSD 12.1, carregue o <filename>.ko</filename> correspondente no arquivo <filename>/boot/loader.conf</filename> adicionando <userinput><replaceable>driver</replaceable>_load="YES"</userinput> e reiniciando a maquina. Outra forma melhor, é carregar o driver no arquivo <filename>/etc/rc.conf</filename> adicionando a variável <varname>kld_list</varname> (veja <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> para maiores detalhes) nesse arquivo e reiniciar. Isso é necessário porque de outra forma o driver não estará carregado no tempo em que a interface <citerefentry><refentrytitle>lagg</refentrytitle><manvolnum>4</manvolnum></citerefentry> for configurada.
a month ago
Browse all component changes

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: note/para
Source string location
book.translate.xml:65535
String age
3 months ago
Source string age
3 months ago
Translation file
books/pt_BR/handbook.po, string 11083