> > > That situation could be caused by either misconfiguring the interfaces > on the honeywall. I did that in the begining and realized that. > Additionaly you can change the init script to listen on the correct > interface. But I think the problem with lack of data is more geared > towards honeywall going into sort of HUNG state where even if you > TCPDUMP the output that you get slows down considerably and tcpdump > begins to MISS packets. Its sort of like listening to traffic > selectively or not listening at all. This was my experience with > tcpdump when i couldn't get any data on walleye interface. > > -Parvinder Bhasin > >
Same here, even the bridge stops working without any notice, sometimes restarting (or stoping) iptables makes the network work again, but other times not even that Max -- <?php $signautre = null; echo $signature; _______________________________________________ Honeywall mailing list [email protected] https://public.honeynet.org/mailman/listinfo/honeywall
