[Bug 212331] pfil processing order
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212331 --- Comment #8 from srijannandi --- ipfw is doing it's job perfectly well. It's just that I use ipfw for bandwidth shaping and also have captive portal running on ipfw. Rest all firewall'ing and nat'ting features are used in pf. So, I have ipfw processing packets destined to port 80. As soon as it receives a packet for destination port 80, it throws the user a captive portal login page. The user than logs in using his/her username and password. After which the packet is marked as authenticated and passed on to pf for further processing. pf then allows or denies the traffic as per the rule configured. This works fine, without issues. As soon as I enable a route-to rule in pf to pass this traffic via a specific gateway, then when a packet is received by FreeBSD for destination port 80, ipfw no longer comes into picture and pf shorts this packet and start processing it. Therefore, in this scenario, I no longer get the captive portal page. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 211219] NIC status does not pass into a state of "no carrier" after disconnecting the cable.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 --- Comment #3 from Alexey --- Yes, this card has been configured in the rc.conf -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Vlan offloaded checksums
Hello,
I have a network driver that supports hardware checksums.
Thanks to offset parameters, it also supports VLAN checksums.
However, it does not handle hardware tagging (not sure the underlying network
adapter can actually do it)
Unfortunately, the VLAN hardware checksums seem to be done only if
IFCAP_VLAN_HWTAGGING is set [1]
I do not understand this assertion: if I force the propagation of the hardware
checksuming only based on the IFCAP_VLAN_HWCSUM, it works fine with my driver.
What do you think?
Emeric
[1]:
In ./net/if_vlan.c, function vlan_capabilities :
/*
* If the parent interface can do checksum offloading
* on VLANs, then propagate its hardware-assisted
* checksumming flags. Also assert that checksum
* offloading requires hardware VLAN tagging.
*/
if (p->if_capabilities & IFCAP_VLAN_HWCSUM)
ifp->if_capabilities = p->if_capabilities & IFCAP_HWCSUM;
if (p->if_capenable & IFCAP_VLAN_HWCSUM &&
p->if_capenable & IFCAP_VLAN_HWTAGGING) {
ifp->if_capenable = p->if_capenable & IFCAP_HWCSUM;
ifp->if_hwassist = p->if_hwassist & (CSUM_IP | CSUM_TCP |
CSUM_UDP | CSUM_SCTP);
} else {
ifp->if_capenable = 0;
ifp->if_hwassist = 0;
}
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Vlan offloaded checksums
On Mon, Sep 12, 2016 at 06:09:02PM +0200, Emeric POUPON wrote: > Hello, > > I have a network driver that supports hardware checksums. > Thanks to offset parameters, it also supports VLAN checksums. > However, it does not handle hardware tagging (not sure the underlying network > adapter can actually do it) > > Unfortunately, the VLAN hardware checksums seem to be done only if > IFCAP_VLAN_HWTAGGING is set [1] > I do not understand this assertion: if I force the propagation of the > hardware checksuming only based on the IFCAP_VLAN_HWCSUM, it works fine with > my driver. > > What do you think? > As you said some NICs do not rely on VLAN H/W tagging to make VLAN checksum offloading work. But current vlan(4) assumes VLAN H/W tagging is prerequisite condition to support VLAN checksum offloading. The same is true for TSO support over VLAN. I don't know what NIC you're referring to but it's rare to see controllers that don't support VLAN H/W tagging on PC/Servers. But it might be common NIC feature found on SoCs. If H/W requires offset parameters for checksum offloading you may already have to parse mbufs in the driver to extract that information and it would add additional overheads. If you really want to enable VLAN H/W checksum offloading in your driver you may be able to add VLAN tag handling in the parser and announce VLAN H/W tagging capability to network stack. You may not notice performance differences with VLAN H/W checksum offloading though. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Regression WPA? 10.2 -> 10.3 stopped working
Hi! have you tried say, 10.3 kernel with 10.2 userland? does it still work? -adrian ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
