setfib+pf

Hi, I originally posted my message to questions, however no response for about a week. Therefore I'm reposting here. Original question available at http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190056.html For those who prefer reading human text, here are my questions: I'd like

RE: Broadcast packet not being sent

Problem solved. I have to explicitly set cond.iface before sending the packet. User error... -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Peter Steele Sent: Monday, January 12, 2009 4:02 PM To: freebsd-net@freebsd.org Subject: B

Broadcast packet not being sent

I am using scapy to construct a UDP broadcast packet. The code I'm using is: packet=Ether(dst="ff:ff:ff:ff:ff:ff")/IP(dst="255.255.255.255")/UDP(dpor t=3)/payload sendp(packet) Send 1 packets. This works fine when I have an IP assigned to the box. However, when no IP is assigned, I ge

Re: HEADSUP: arp-v2 has been committed

Garrett Cooper wrote: I think setting it to a value of 0 has two good points... In code that does: if (XXX & RTF_LLINFO) { yyy() } the optimiser should simply remove the code, or at worst give an error messages that makes people go look for the answer, and secondly, the conditional #if

Re: HEADSUP: arp-v2 has been committed

On Mon, Jan 12, 2009 at 12:37 PM, Julian Elischer wrote: > Garrett Cooper wrote: > > I think setting it to a value of 0 has two good points... > > In code that does: > if (XXX & RTF_LLINFO) { >yyy() > } > the optimiser should simply remove the code, > or at worst give an error messages tha

Re: HEADSUP: arp-v2 has been committed

On Mon, Jan 12, 2009 at 10:25 AM, Li, Qing wrote: > I have revived the RTF_LLINFO definition in route.h. > A new kernel option "COMPAT_ROUTE_FLAGS" is introduced, all > for providing binary compatibility for existing ports. > I could have made the RTF_LLINFO bit only applicable with _KERNEL. > > W

Network is unreachable and other related errors

Hello all, Wondering if anyone else experiences errors such as "Network is unreachable" and the like when using security auditing tools like nmap, nessus, etc. I found a PR from a long time ago that appears relevant but it was abandoned: http://www.freebsd.org/cgi/query-pr.cgi?pr=102741&cat=

Re: kern/119432: [arp] route add -host <host> -iface <nic> causes arp entry with nic's arp address [regression]

The following reply was made to PR kern/119432; it has been noted by GNATS. From: Axel Scheepers To: bug-follo...@freebsd.org, a...@axel.truedestiny.net Cc: Subject: Re: kern/119432: [arp] route add -host -iface causes arp entry with nic's arp address [regression] Date: Mon, 12 Ja

RE: HEADSUP: arp-v2 has been committed

I have revived the RTF_LLINFO definition in route.h. A new kernel option "COMPAT_ROUTE_FLAGS" is introduced, all for providing binary compatibility for existing ports. I could have made the RTF_LLINFO bit only applicable with _KERNEL. Without rehashing the discussion we all had on this topic on b

Current problem reports assigned to n...@freebsd.org

Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker

Current problem reports assigned to freebsd-net@FreeBSD.org

Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker