Project

General

Profile

Actions
Copy link

Bug #88

closed

TXCSUM forced on at boot which breaks wireless bridging

Added by Jim Pingle about 15 years ago. Updated almost 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
2.0
Start date:
09/18/2009
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

When you have a wireless interface bridged to a wired interface, txcsum needs to be disabled on the wired NIC in order for it to properly pass out traffic for non-local hosts across the bridge. It seems to contact the pfsense box itself OK, but nothing beyond.

On boot, txcsum is being forced on (Lines 939-942 of etc/inc/pfsense-utils.inc) which breaks the bridge at boot. Once the system is fully booted, you can go to Interfaces > OPT1 (or whatever the wireless interface is), then click Apply, and once the bridge is set back up, txcsum is disabled on the card.

I tried explicitly setting -txcsum in the code for the bridge setup, but apparently the code from pfsense-utils.inc happens after that point since it seemed to have no effect. Only when I commented out the above mentioned lines in pfsense-utils.inc was I able to get a working bridge on reboot.

Not sure if that check in pfsense-utils.inc needs to be "bridge-aware" or if it's even really necessary.

How to reproduce:
Add ath0 as an OPT, enable, bridge to LAN, add firewall rules, and reboot. Bridge doesn't work. Check ifconfig output, txcsum is present. Either Apply on the interface config page or run "ifconfig <LAN int> -txcsum", bridge works.

Actions
Copy link

Also available in: Atom PDF