![](https://seccdn.libravatar.org/avatar/99c4bf793f5887128fa31f921cb2605b.jpg?s=120&d=mm&r=g)
On Wed, 27 Sep 2000, Tim Duggan wrote:
Sep 27 10:10:09 barley kernel: Packet log: input DENY ppp0 PROTO=6 other person:1198 me:2443 L=48 S=0x00 I=54283 F=0x4000 T=113 SYN (#107)
Quick summary of message: input chain, denied the packet, interface ppp0, PROTO=6 (it is a tcp packet), from "other person":port 1198, to "me":port 2443, L(length)= 48 bytes, S(service field info?), I(ID info), F(fragment info), T(time to live in jumps/hops), SYN flag set (as opposed to ACK). Finally the part we want (#107). This is the rule number that started the whole thing. Nice of it to say where to start looking, 107 is a long way down the list. So, which one is 107?
Good question. I printed out the firewall script and I can only count 70. So I'm likely counting incorrectly.
Now I'd understand if it was the other way around but then I might just be confused.
It would be more confusing if you were given an M$ style error message to start with, like "Windows has encountered an error and cannot continue - OK".:-)
What I meant was the that I might understand if the firewall was blocking me sending out the packet but it's blocking an incoming packet. My limited understanding of the the ipchains rules is that the incoming packet is being allowed. ipchains -L prints out about 70 lines. Is there a better option for printing out all the rules? Thanks Nick -- ----------------------------- Anybody got plans for an ark? ----------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq