Sorry for the long lines. Trying again, narrower. If I have an open linux box with no rules in effect (open box), I can ssh in and run vuurmuur_conf. vuurmuur -D is not running yet.
During this test process, one of the rules I am about to inject allows "ssh" in. Save the rules, then start vuurmuur -D for the first time, my ssh session is cut off, and I do not see the completion of the starting of the vuurmuur daemon. I also have a serial port console on this headless box. I can see that the vuurmuur daemon started, and applied the rules OK. But the original ssh ethernet session is kaput, it did not show the completion of the daemon startup. Subsequently I can log in with ssh again, while the daemon is running, and the rules are fully in effect. Is this normal to be cut off? Is there a way around it with vuurmuur? I know that if I hand craft some iptables rules, I can avoid this, and have done this OK elsewhere. Thanks, Dick ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Vuurmuur-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vuurmuur-users
