Re: Firewall box stop responding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If you google RFC 1918, it will show that your system has sent a request
for a private subnet out onto the global internet.  I am no IP guru, but
I suspect that you will find the solution somewhere in the linux
responses related to RFC 1918.

Regards,
Les H
On Wed, 2009-01-14 at 14:31 -0200, Leonardo Korndorfer wrote:
> Hi all!
> 
> I'm in a situation that is kinda hard to see what's happening. So I'm
> going straight to the scenario:
> I have a firewall box that somehow stops responding to all services
> such as ssh and squid. It does answer ping.
> Early this morning I was looking to the messages log with tail -f when
> it just stop and then no responses again.
> 
> Does anyone have lived this situation? 
> 
> Here goes an example of the normality of logs when it just stops:
> 
> /* regular log */
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1660
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Connection from UDP:
> [192.168.0.13]:1661
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1661
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Connection from UDP:
> [192.168.0.13]:1662
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1662
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Connection from UDP:
> [192.168.0.13]:1663
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1663
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Connection from UDP:
> [192.168.0.13]:1664
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1664
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Connection from UDP:
> [192.168.0.13]:1665
> Jan 14 13:35:08 mercfw1 snmpd[2040]: Received SNMP packet(s) from UDP:
> [192.168.0.13]:1665
> Jan 14 13:35:06 mercfw1 named[1731]: client 127.0.0.1#38570: RFC 1918
> response from Internet for 11.0.168.192.in-addr.arpa
> /* forced shutdown and normal start log */
> Jan 14 13:49:03 mercfw1 kernel: imklog 3.14.1, log source = /proc/kmsg
> started.
> Jan 14 13:49:03 mercfw1 kernel:
> Inspecting /boot/System.map-2.6.25-14.fc9.i686
> Jan 14 13:49:03 mercfw1 kernel: Loaded 28110 symbols
> from /boot/System.map-2.6.25-14.fc9.i686.
> Jan 14 13:49:03 mercfw1 kernel: Symbols match kernel version 2.6.25.
> Jan 14 13:49:03 mercfw1 kernel: No module symbols loaded - kernel
> modules not enabled.
> 
> The seconds before (13:35:06) are analogous. Nothing evil has
> happened.
> 
> Leonardo Richter Korndorfer
> 
> personal @ http://leokorndorfer.no-ip.org
> http://counter.li.org #384363
> ICQ: 102788426
> 
> -- 
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux