blob: da1bf462874d81e3f10067b9037569a53dc7ca84 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] Odd entry in log file
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Odd%20entry%20in%20log%20file&In-Reply-To=%3C4FAB1FCB.9080602%40Rock3d.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007262.html">
<LINK REL="Next" HREF="007264.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] Odd entry in log file</H1>
<B>imnotpc</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Odd%20entry%20in%20log%20file&In-Reply-To=%3C4FAB1FCB.9080602%40Rock3d.net%3E"
TITLE="[Mageia-discuss] Odd entry in log file">imnotpc at Rock3d.net
</A><BR>
<I>Thu May 10 03:54:19 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="007262.html">[Mageia-discuss] Mageia 2 RC release is out
</A></li>
<LI>Next message: <A HREF="007264.html">[Mageia-discuss] Odd entry in log file
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7263">[ date ]</a>
<a href="thread.html#7263">[ thread ]</a>
<a href="subject.html#7263">[ subject ]</a>
<a href="author.html#7263">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 05/08/2012 03:33 PM, imnotpc wrote:
><i> On 05/08/2012 02:20 PM, Frank Griffin wrote:
</I>><i> I haven't had time to run tcpdump yet but my current theory is that
</I>><i> the wireless router doesn't or can't NAT certain types of packets and
</I>><i> those are triggering the kernel log messages. Or perhaps it's only
</I>><i> NATing packets from a host with a valid DHCP lease and simply
</I>><i> forwarding anything else that comes in.
</I>
I did install and run tcpdump then I realized that the answer was under
my nose the whole time. The kernel log message gives the MAC address of
the sending and receiving interface. After all this discussion, effort,
and advice, all I really needed to do was find the device with the
sending MAC address. Which, as we suspected, was the wireless router. I
still don't know why it doesn't NAT those particular packets, but in the
big picture it doesn't really matter since they go nowhere.
The only question I have left is can I change a setting to disable the
logging of these packets (or change their log level to debug)? There are
literally thousands of them a day cluttering the log. If I have to I can
filter them out using syslog but I'd prefer a cleaner solution.
Thanks for everyone's advice and effort.
Jeff
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007262.html">[Mageia-discuss] Mageia 2 RC release is out
</A></li>
<LI>Next message: <A HREF="007264.html">[Mageia-discuss] Odd entry in log file
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7263">[ date ]</a>
<a href="thread.html#7263">[ thread ]</a>
<a href="subject.html#7263">[ subject ]</a>
<a href="author.html#7263">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
