Jun 15 23:50:55 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=1498 F=0x0000 T=107 (#11)
Jun 15 23:50:57 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=1502 F=0x0000 T=107 (#11)
Jun 15 23:50:58 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=1503 F=0x0000 T=107 (#11)
Jun 15 23:52:12 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=2353 F=0x0000 T=107 (#11)
Jun 15 23:52:13 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=2356 F=0x0000 T=107 (#11)
Jun 15 23:52:15 bluetrout kernel: Packet log: input DENY eth0 PROTO=17
192.168.0.2:137 a.b.c.d:137 L=78 S=0x00 I=2357 F=0x0000 T=107 (#11)
Now, the interesting things are these:
[1] 192.168.0.2 is an DHCP leased address on our internal (eth1), masq'd
network -- powered OFF. How could it come in eth0, anyway?
[2] a.b.c.d is a static address in our DMZ (eth2), which is on and on
which I am running an active SSH session.
What do you think?
--
Best Regards,
mds
mds resource
888.250.3987
"Dare to fix things before they break . . . "
"Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . . "
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
