Displaying 5 results from an estimated 5 matches for "m_pkthdr".
2009 Feb 05
3
impossible packet length ...
Hi,
on 2 different servers, running 7.1-stable + zfs, I get this
error rather frequently:
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from
nfs server sunfire:/dist
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1936028704) from
nfs server sunfire:/dist
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1869363744) from
nfs server sunfire:/dist
2006 Mar 18
2
IPSEC with MAC/MLS support crack
Hi, When I use FreeBSD-6.0 Release (also FreeBSD-5.4),
I found
IPSEC can't coexists with MAC.
When the IpSec is setup, and we connects the TCP
server with IPSEC and MAC support, the server
innevitably crack. Because the m_pkthdr of some mbuf
is mangled by unknown reasons.
Following is my kernel configuration:
options MAC
options MAC_DEBUG
options UFS_EXTATTR
options UFS_EXTATTR_AUTOSTART
options MAC_MLS
# uncomment to put sebsd to kernel, but better to
options IPSEC
options...
2003 May 26
0
ip_input.c
...nes:
;-------------------------------------------------
/* 127/8 must not appear on wire - RFC1122 */
if ((ntohl(ip->ip_dst.s_addr) >> IN_CLASSA_NSHIFT) == IN_LOOPBACKNET ||
(ntohl(ip->ip_src.s_addr) >> IN_CLASSA_NSHIFT) == IN_LOOPBACKNET) {
if ((m->m_pkthdr.rcvif->if_flags & IFF_LOOPBACK) == 0) {
ipstat.ips_badaddr++;
goto bad;
}
}
;-------------------------------------------
If we have such wonderful code inside freeBSD kernel, do we really
need to duplicate in default rc.firewall:
;-----...
2004 Apr 20
1
[patch] Raw sockets in jails
Although RAW sockets can be used when specifying the source
address of packets (defeating one of the aspects of the jail)
some people may find it usefull to use utilities like ping(8)
or traceroute(8) from inside jails.
Enclosed is a patch I have written which gives you the option
of allowing prison-root to create raw sockets inside the prison,
so
2003 May 31
3
Packet flow through IPFW+IPF+IPNAT ?
Hi.
On my FreeBSD 4.8 configured IPFW2+IPF+IPNAT and I use them all:
- IPFW - traffic accounting, shaping, balancing and filtering;
- IPFilter - policy routing;
- IPNAT - masquerading.
I want to know, how IP-packets flow through all of this components?
What's the path?
incoming: IPFW Layer2 -> IPFW&Dummynet -> IPNAT -> IPFilter ?
outgoing: IPFW Layer2 ->