On 05-Jan-2001 Bret Hughes opined:
>
> Logcheck found these in my logs on my firewall. What on earth is port
> 0? Coming from port 8 all all places what the heck is that? I get a
> ton of stuff banging on this box all the time but I never noticed port
> 0
> before. Not to say it isn't buried in all the 111, 23 21 etc. but at
> least I know what they are trying there :)
>
>
>
> Unusual System Events
> =-=-=-=-=-=-=-=-=-=-=
> Jan 4 10:31:17 tulfw1 kernel: Packet log: input DENY eth1 PROTO=1
> 151.164.62.11:8 xxx.xxx.xxx.xxx:0 L=56 S=0x00 I=3899 F=0x4000 T=250
> (#6)
> Jan 4 10:31:17 tulfw1 kernel: Packet log: input DENY eth1 PROTO=1
> 151.164.62.11:8 xxx.xxx.xxx.xxx:0 L=56 S=0x00 I=3900 F=0x4000 T=250
> (#6)
> Jan 4 10:31:18 tulfw1 kernel: Packet log: input DENY eth1 PROTO=1
> 151.164.62.11:8 xxx.xxx.xxx.xxx:0 L=56 S=0x00 I=3901 F=0x4000 T=250
> (#6)
>
> Any insight appreciated.
I have no idea what you're getting hit with. But, gnapster claims in the
README that one of its settings uses port 0 if the client is behind a
firewall that can't connect directly or something like that (whatever
they were trying to get at was a little unclear anyway). Maybe somebody
is using a misconfigured client, or maybe the kiddies are hard at work
trying to champion a new non-existant entry path.
Or, maybe I just have no idea.
--
Sometimes you have to stride boldly up to life,
look it straight in the eye, and say "huh?"
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
