diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120508/007258.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120508/007258.html | 76 |
1 files changed, 76 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120508/007258.html b/zarb-ml/mageia-discuss/20120508/007258.html new file mode 100644 index 000000000..42d5395a8 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120508/007258.html @@ -0,0 +1,76 @@ +<!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=%3C4FA973D3.8010807%40Rock3d.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007257.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=%3C4FA973D3.8010807%40Rock3d.net%3E" + TITLE="[Mageia-discuss] Odd entry in log file">imnotpc at Rock3d.net + </A><BR> + <I>Tue May 8 21:28:19 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="007257.html">[Mageia-discuss] Odd entry in log file +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#7258">[ date ]</a> + <a href="thread.html#7258">[ thread ]</a> + <a href="subject.html#7258">[ subject ]</a> + <a href="author.html#7258">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 05/08/2012 03:17 PM, Maarten Vanraes wrote: +><i> Op dinsdag 08 mei 2012 02:05:44 schreef imnotpc: +</I>><i> [...] +</I>>>><i> promiscuous mode means you're passing through from layer 2 to layer 3 +</I>>>><i> irrespective of mac address (ie: even if it's not for you) +</I>>>><i> +</I>>>><i> iptables is not complaining +</I>>>><i> +</I>>>><i> martians is kernel level, (resource path filtering (for asynchronous +</I>>>><i> routing)), before iptables even comes into play. +</I>>><i> So the kernel would log the martian before iptables sees it? That +</I>>><i> explains why it isn't dropped by the firewall. But that begs the +</I>>><i> question, is there any point in using iptables rules to block packets +</I>>><i> from other subnets if iptables will never see them? Just about every +</I>>><i> sample firewall ruleset I've ever seen does this either explicitly or by +</I>>><i> allowing them to fall through to the default DROP rule. Now that I'm +</I>>><i> thinking back, in 10+ years of Linux LAN experience I've never seen a +</I>>><i> martian packet logged by any of my firewalls. i just assumed it was good +</I>>><i> network management ;-) +</I>><i> yes, because rp_filter level can be adjusted in the kernel :-) +</I>><i> +</I>Ah, so it was my good network management then, hehe. Good info, thanks. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007257.html">[Mageia-discuss] Odd entry in log file +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#7258">[ date ]</a> + <a href="thread.html#7258">[ thread ]</a> + <a href="subject.html#7258">[ subject ]</a> + <a href="author.html#7258">[ 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> |