The socket sendto INVALID ARGUMENT ERROR returned

Dear all I wrote a code to send a tcp packet on a raw socket, but the sendto function return some errors on argument what can make this error occur ??? thanx the code : char datagram[4096]; . socket(s, SOCK_RAW, IPPROTO_TCP); .//filling the tcp/ip header int one = 1; const int

Re: The socket sendto INVALID ARGUMENT ERROR returned

soheil soheil wrote: Dear all I wrote a code to send a tcp packet on a raw socket, but the sendto function return some errors on argument what can make this error occur ??? thanx the code : char datagram[4096]; . socket(s, SOCK_RAW, IPPROTO_TCP); s = socket(AF_INET, ); -- Lev Walki

Adding bridge table lookup via sysctl()

Hi all, I am doing some work based on the FreeBSD 4.7 bridge code, and want to add some "userland" table lookup capabilities. Right now I did this for a sysctl call: (BTW, sorry if the code aesthetics are not the best, I promise to clean that up later): ##

catching bad ICMP errors - very odd

I have inserted this ipfw rule, based on guidance from the archives: count icmp from any to any icmptype 4,5,9,10,12,13,14,15,16,17,18 Now, I am watching that count rule, and it keeps growing. This means that people are sending me packets other than types 0,3,8,11. So I wanted to see what they

Re: The socket sendto INVALID ARGUMENT ERROR returned

I'm afraid I made a mistake ;) But what is the error about THANX From: Lev Walkin <[EMAIL PROTECTED]> To: soheil soheil <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: The socket sendto INVALID ARGUMENT ERROR returned Date: Fri, 24 Jan 2003 00:53:30 -0800 soheil soheil wrote: Dear all I w

Re: catching bad ICMP errors - very odd

is this with ipfw1 or ipfw2 or both ? cheers luigi On Fri, Jan 24, 2003 at 03:56:54AM -0800, Josh Brooks wrote: > > I have inserted this ipfw rule, based on guidance from the archives: > > count icmp from any to any icmptype 4,5,9,10,12,13,14,15,16,17,18 > > Now, I am watching

problem with fxp interface in promisc mode

Hello! Can anybody help me? Please, look at send-pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=47432 Shortly, my problem is: FreeBSD 4.7-RELEASE-p2 with fxp and xl interface. Running tcpdump or trafshow on fxp interface causes the fatal trap 12 message, and system goes down. It happens on fxp

Re: catching bad ICMP errors - very odd

ipfw1 On Fri, 24 Jan 2003, Luigi Rizzo wrote: > is this with ipfw1 or ipfw2 or both ? > > cheers > luigi > > On Fri, Jan 24, 2003 at 03:56:54AM -0800, Josh Brooks wrote: > > > > I have inserted this ipfw rule, based on guidance from the archives: > > > > count icmp from any to any ic

Re: catching bad ICMP errors - very odd

In reply to Luigi Rizzo <[EMAIL PROTECTED]> : > is this with ipfw1 or ipfw2 or both ? > > cheers > luigi > > On Fri, Jan 24, 2003 at 03:56:54AM -0800, Josh Brooks wrote: > > > > I have inserted this ipfw rule, based on guidance from the archives: > > > > count icmp from any to any

Re: catching bad ICMP errors - very odd

Hello, Josh. You wrote 24 January 2003, 14:56:54: JB> I have inserted this ipfw rule, based on guidance from the archives: JB> count icmp from any to any icmptype 4,5,9,10,12,13,14,15,16,17,18 JB> Now, I am watching that count rule, and it keeps growing. This means that JB> people are sending