From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-discuss/20120508/007254.html | 77 +++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 zarb-ml/mageia-discuss/20120508/007254.html (limited to 'zarb-ml/mageia-discuss/20120508/007254.html') diff --git a/zarb-ml/mageia-discuss/20120508/007254.html b/zarb-ml/mageia-discuss/20120508/007254.html new file mode 100644 index 000000000..b50f40b43 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120508/007254.html @@ -0,0 +1,77 @@ + + + + [Mageia-discuss] Odd entry in log file + + + + + + + + + +

[Mageia-discuss] Odd entry in log file

+ Frank Griffin + ftg at roadrunner.com +
+ Tue May 8 12:47:00 CEST 2012 +

+
+ +
On 05/07/2012 07:42 PM, imnotpc wrote:
+>
+> 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.
+Waitaminnit.  Yesterday you wrote:
+
+>
+> Wireless Router Attached to the LAN: The LAN facing NIC on the 
+> wireless router has a fixed IP of 192.168.0.100. The wireless 
+> interface is configured to assign IPs in the 192.168.2.0/24 range to 
+> the wireless hosts using DHCP.
+
+If the wireless router DHCP is setup to assign from 192.168.3.0/24, then 
+that's where the 192.168.3.2 is coming from.  Unless your gateway is set 
+to masquerade 192.168.3.0/24, you get exactly what you're seeing.
+
+
+ + + +
+

+ +
+More information about the Mageia-discuss +mailing list
+ -- cgit v1.2.1