Re: pf protection against spoofed [source addr] packets

> I then tried to use nemesis to change the spoofed source address from
> 64.156.193.115 to 127.0.0.1 or 192.168.0.x, but nemesis wasn't able to
> do this with the error message "ERROR: Incomplete packet injection.  Only
> wrote -1 bytes."

Sorry my mistake.  I _was_ able to spoof a source address such as 
192.168.0.1, but _not_ 127.0.0.1.  Wondering why; I'd like to see how my 
service reacts when I send a UDP packet with a spoofed source address of 
127.0.0.1, but don't know how to do it.