[Snort-users] Bug: $eth0_ADDRESS parse error (FIXED?)
erek at ...950...
Sat Feb 7 14:14:08 EST 2004
On Sat, 7 Feb 2004, Tom Barcellona wrote:
> I have been having the same problem that a few people have had in the
> past regarding the $<interface>_ADDRESS error. I had "EXTERNAL_NET =
> !HOME_NET" and HOME_NET =
> Problem was I would always get a Snort parse error. I even tried
> removing all the 10.x.x.x networks and leaving $eth0_ADDRESS by itself.
> Still didn't work.
> I finally got it to work by putting HOME_NET before EXTERNAL_NET.
> Everything parses fine now, no errors. Does this sound right to
Makes perfect sense.
"Please set my EXTERNAL_NET to NOT <insert random memory garbage here>",
and then set HOME_NET to <something>."
Why do you think that in snort.conf HOME_NET is defined _before_
"It looks just like a Telefunken U-47. You'll love it..." -- Frank Zappa
More information about the Snort-users