pfsense:network:force_interface_speed_or_duplex_settings
Differences
This shows you the differences between two versions of the page.
pfsense:network:force_interface_speed_or_duplex_settings [2020/11/30 11:01] – created peter | pfsense:network:force_interface_speed_or_duplex_settings [2020/11/30 11:09] (current) – peter | ||
---|---|---|---|
Line 12: | Line 12: | ||
---- | ---- | ||
+ | |||
+ | ===== Force the speed of the network cards and set the Duplex mode ===== | ||
+ | |||
+ | Navigate to **Interfaces -> LAN**. | ||
+ | |||
+ | * Speed and Duplex: | ||
+ | * Click **Save** | ||
+ | * Click **Apply Changes**. | ||
+ | |||
+ | |||
+ | Natigate to **Status -> Interfaces** and check the Media line for the interface in question. | ||
+ | |||
+ | If the selected speed and duplex are listed, then the setting has been applied as expected. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Switch back to autoselect ===== | ||
+ | |||
+ | To switch back to autoselect, use the same settings and select **Default** under **Speed and Duplex**. | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | Notably, this is an issue with many Realtek cards, including network interfaces which utilize the re(4) driver. | ||
+ | |||
+ | The settings appear to apply, but the card remains in a duplex mismatch state. | ||
+ | |||
+ | In these cases you can work around the problem with a small managed switch. | ||
+ | |||
+ | Set the speed and duplex of one port to match the upstream, and then set the port facing the affected NIC to autoselect/ | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ |
pfsense/network/force_interface_speed_or_duplex_settings.1606734077.txt.gz · Last modified: 2020/11/30 11:01 by peter