Anyone know what is and what cause this log entry???
Oct 17 12:29:28 mewtwo kernel: IPur2 .1, on devur2 .1, on dev e2 .1, on
dev eth.1, on dev eth0
Oct 17 12:29:28 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
b0 4c 00 3d 8b 08 06 ........L.=...
On 2012-10-17 16:33, VampirD wrote:
> Anyone know what is and what cause this log entry???
>
>
> Oct 17 12:29:28 mewtwo kernel: IPur2 .1, on devur2 .1, on dev e2 .1, on
> dev eth.1, on dev eth0
> Oct 17 12:29:28 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
> b0 4c 00 3d 8b 08 06 ........L.=...
>
Is that the exact content of the log entries, of have you edited them?
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Is the exact content, I have not touch any character on it, only copy
and paste here
On 10/17/2012 09:57 AM, VampirD wrote:
> Is the exact content, I have not touch any character on it, only copy
> and paste here
I am pretty sure it does not come from the kernel. The first message indicates a
hierarchy eth0 => eth.1 => e2.1 => devur.1 => IPur.1. What are you doing that is
unusual on this network?
That system is the proxy and firewall server, I have no change anything
recently, but the proxy is randomly refusing connections and today is
refusing me from ssh or kicking me with a broken pipe message.
I have entries like
Oct 12 09:01:10 mewtwo kernel: IPv4ef10, on dev etef10, on dev ethf10,
on dev eth010, on dev eth0
Oct 12 09:01:10 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
1e 90 eb 8c 64 08 06 ...........d..
Oct 12 09:01:10 mewtwo kernel: IPv4ef10, on dev etef10, on dev ethf10,
on dev eth010, on dev eth0
Oct 12 09:01:10 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
1e 90 eb 8c 64 08 06 ...........d..
Oct 12 09:01:11 mewtwo kernel: IPv4ef10, on dev etef10, on dev ethf10,
on dev eth010, on dev eth0
Oct 12 09:01:11 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
1e 90 eb 8c 64 08 06 ...........d..
Oct 17 12:29:28 mewtwo kernel: IPur2 .1, on devur2 .1, on dev e2 .1, on
dev eth.1, on dev eth0
Oct 17 12:29:28 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
b0 4c 00 3d 8b 08 06 ........L.=...
Oct 17 12:33:02 mewtwo kernel: IPur1 .1, on devur1 .1, on dev e1 .1, on
dev eth.1, on dev eth0
Oct 17 12:33:02 mewtwo kernel: ll header: 00000000: ff ff ff ff ff ff 00
b0 4c 00 3d 8b 08 06 ........L.=...
Oct 17 10:19:52 mewtwo kernel: 2228.540183] IPv4: martian source
192.168.0.51 from 192.168.0.1, on dev eth0
Oct 17 10:19:52 mewtwo kernel: 2228.540188] ll header: 00000000: ff ff
ff ff ff ff 00 b0 4c 00 3d 8b 08 06 ........L.=...
and with logwatch I get this report
--------------------- Kernel Begin ------------------------
1 Time(s): IPv4:
1e.169.254.122.1e.169.254.122.1e.169.254.122.12.169.254.122.127169.254.122.127
1 Time(s): IPv4: host 16g to 192.168.0g to 192.168.0. to 192.168.0.3
to 192.168.0.3
2 Time(s): IPv4: host 16g to 192.168.0g to 192.168.0. to 192.168.0.4
to 192.168.0.4
2 Time(s): IPv4: host 192g to 169.254.7g to 169.254.7. to
169.254.7.5 to 169.254.7.5
1 Time(s): IPv4e 40, on dev ete 40, on dev eth 40, on dev eth040, on
dev eth0
3 Time(s): IPv4ef10, on dev etef10, on dev ethf10, on dev eth010, on
dev eth0
1 Time(s): ll header: 00000000: d8 5d 4c 81 8d 6a 00 1d 92 4c 88 02 08
00 .]L..j...L....
3 Time(s): ll header: 00000000: ff ff ff ff ff ff 00 1e 90 eb 8c 64 08
06 ...........d..
1 Time(s): r81: eth1: link up: eth1: link up
---------------------- Kernel End -------------------------
Solved, two damaged switches