summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20120508/007251.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20120508/007251.html')
-rw-r--r--zarb-ml/mageia-discuss/20120508/007251.html94
1 files changed, 94 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120508/007251.html b/zarb-ml/mageia-discuss/20120508/007251.html
new file mode 100644
index 000000000..813d12685
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20120508/007251.html
@@ -0,0 +1,94 @@
+<!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=%3C4FA85DEA.9090104%40Rock3d.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="007250.html">
+ <LINK REL="Next" HREF="007254.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=%3C4FA85DEA.9090104%40Rock3d.net%3E"
+ TITLE="[Mageia-discuss] Odd entry in log file">imnotpc at Rock3d.net
+ </A><BR>
+ <I>Tue May 8 01:42:34 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007250.html">[Mageia-discuss] Odd entry in log file
+</A></li>
+ <LI>Next message: <A HREF="007254.html">[Mageia-discuss] Odd entry in log file
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7251">[ date ]</a>
+ <a href="thread.html#7251">[ thread ]</a>
+ <a href="subject.html#7251">[ subject ]</a>
+ <a href="author.html#7251">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>
+&gt;&gt;<i> Well isn't that interesting. That Comcast IP is the address of the
+</I>&gt;&gt;<i> ISP gateway I use. Both of my firewall/gateway boxes that are logging
+</I>&gt;&gt;<i> martian packets are connected to similar Comcast routers. The routers
+</I>&gt;&gt;<i> are configured in bridge mode so the router DHCP service has no
+</I>&gt;&gt;<i> effect on my connection, but it might still be active on the router.
+</I>&gt;&gt;<i> Also each ISP router also has a wireless interface and that could
+</I>&gt;&gt;<i> still be active. My firewall doesn't block any private IPs coming
+</I>&gt;&gt;<i> from the Internet interface since the ISP routers would never forward
+</I>&gt;&gt;<i> them, so that explains how they get past the firewall.
+</I>&gt;<i>
+</I>&gt;<i> No, I think traceroute doesn't special-case internal IP addresses.
+</I>&gt;<i> Your routing table is (correctly) set up to route traffic for anything
+</I>&gt;<i> other than your known subnets to the external internet, and that's
+</I>&gt;<i> exactly what traceroute is doing. It's your ISP's job to discard
+</I>&gt;<i> internal address packets, not yours.
+</I>&gt;<i>
+</I>&gt;<i> But I think you're on to something with the ISP routers. Is there
+</I>&gt;<i> some reason you don't just run the cable from the cable modem to the
+</I>&gt;<i> external NIC on the gateway PC ? If you're willing to try that, and
+</I>&gt;<i> the martians disappear, it's these routers.
+</I>&gt;<i>
+</I>&gt;<i> Try going into configuration on these routers, and see what their DHCP
+</I>&gt;<i> servers are set up for, and whether the 192.168.3 subnet appears
+</I>&gt;<i> anywhere in there. It's possible that one of your DHCP-using wireless
+</I>&gt;<i> clients is getting an answer to its broadcast from these guys before
+</I>&gt;<i> your internal router, and picking up a 192.168.3.2 IP address from them.
+</I>
+Well the Comcast cable modem was a dead end. I checked it and DHCP is
+disabled, and even if it were enabled it uses a completely different
+subnet. Besides, It would be coming in on eth2 and not eth0. I checked
+the wireless router in the LAN and it uses the 192.168.3.0/24 subnet for
+it's DHCP connections. It has a fixed IP of 192.168.0.100 on the LAN
+interface so I don't know why these IPs would ever be seen by the
+firewall/gateway box, but this looks like the most likely source.
+
+Jeff
+</PRE>
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="007250.html">[Mageia-discuss] Odd entry in log file
+</A></li>
+ <LI>Next message: <A HREF="007254.html">[Mageia-discuss] Odd entry in log file
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7251">[ date ]</a>
+ <a href="thread.html#7251">[ thread ]</a>
+ <a href="subject.html#7251">[ subject ]</a>
+ <a href="author.html#7251">[ 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>