I have been running ipipfilter.1.3 on GeGentooinux
with kernel 2.4.26-r9 for the past couple of months.
My experience with it on Linux has been very good, and
I'd like to thank Darren for making it possible for
Linux users to use his outstanding firewall product to
protect our machines and networks. As always, great
work!
I have run into one problem that I'm hoping to get
resolved. When I run both ipipfilter.1.3 and
VMVMWare.5.2 build-8848 on my laptop, everything works
great until I attempt to shut down my machine. At some
point during the shutdown process, I start receiving
the following messages at the console:
--begin message--
unregister_nenetdevicewaiting for vmvmnetto become
free. Usage count = 4
--end message--
Notes:
- Shutdown continues, albeit at a slower pace, while
these messages are appearing. However, at some point,
the shutdown process hangs while the messages continue
to periodically appear. At that point, the only option
is to power the machine off, and hope that I don't
hose my fifilesystem
- vmvmnetis sometimes the issue; other times, it is
vmvmnet I can't find a correlation between the
interface in the message and a particular
VMVMWareirtual machine (vmvm All my vmvm'sse both
vmvmnetand vmvmnet(one is a NAT interface, the other
is a host-only interface, FYI).
- In ipipfilterules, I reference the interfaces as
vmvmnetand vmvmnet(i.e. pass in on vmvmnet...)
- If either ipipfilterr vmVMWares disabled from
starting, and the other application is started
normally, no shutdown problems occur.
- The problem only manifests itself at shutdown. No
other problems have been observed.
- I hacked my ipipfiltertartup script to check for the
presence of /dedevmvmnetdevices, and to create them
using mkmknodf they don't exist. Didn't help.
- I have tried adding a series of commands to my
ipipfilterhutdown script which flush the state table
and remove all rules before unloading ipipfilter
(ipipfy, ipipfFa, ipipfFSFS Didn't help.
- I have played around with the order of
startup/shutdown of both ipipfilternd VMVMWareDidn't
help. FYI, my default configuration is set up so that
ipipfiltertarts immediately after my network interface
comes up (thus, before VMVMWaretarts).
- I am unsure if this is relevant, but I had to hack
my ipipfiltertartup script to insert two five second
delays in order to get ipipfiltero load and operate
properly on my system. Delay 1 is right before I
ininsmodpipfilterDelay 2 is immediately after the
module load, and right before the ipipff
/path/to/my/ipipfules command.
- For comparison, when I was using
nenetfilterpiptablesith VMVMWareI didn't have any
problems. However, I would much rather use ipipfilter
Anyone have any thoughts about this problem? I could
go to VMVMWareor help, but I have a hunch that it
might be a waste of time and money.
Thanks for any assistance that you can provide.
Cheers,
=-Rob
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
