[K12OSN] NAT not starting on bootup

[Petre Scheie]

Here's a snippet from /var/log/messages.  Notice on line 11 that it 
mentions ip_conntrack, which suggests that the NAT startup script ran as 
it should.  There's no further mention of ip_conntrack until the time 
that I ran the script again manually about 90 minutes later.  So, it 
would seem that something knocked it down.  Since I started it manually, 
it's been fine.  This is consistent with what I saw the last time I 
booted the machine, that once I run the startup script manually, NAT 
stays up.

Mar  9 10:09:07 kelley4gov kernel: EXT3 FS on sda3, internal journal
Mar  9 10:09:07 kelley4gov kernel: kjournald starting.  Commit interval 
5 seconds
Mar  9 10:09:07 kelley4gov kernel: EXT3 FS on sda1, internal journal
Mar  9 10:09:07 kelley4gov kernel: EXT3-fs: mounted filesystem with 
ordered data mode.
Mar  9 10:09:07 kelley4gov kernel: SELinux: initialized (dev sda1, type 
ext3), uses xattr
Mar  9 10:09:07 kelley4gov kernel: SELinux: initialized (dev tmpfs, type 
tmpfs), uses transition SIDs
Mar  9 10:09:07 kelley4gov kernel: Adding 2096472k swap on /dev/sda2. 
Priority:-1 extents:1 across:2096472k
Mar  9 10:09:07 kelley4gov kernel: SELinux: initialized (dev 
binfmt_misc, type binfmt_misc), uses genfs_contexts
Mar  9 10:09:07 kelley4gov kernel: ip_tables: (C) 2000-2002 Netfilter 
core team
Mar  9 10:09:07 kelley4gov kernel: Netfilter messages via NETLINK v0.30.
Mar  9 10:09:07 kelley4gov kernel: ip_conntrack version 2.4 (8192 
buckets, 65536 max) - 232 bytes per conntrack
Mar  9 10:09:07 kelley4gov kernel: SELinux: initialized (dev rpc_pipefs, 
type rpc_pipefs), uses genfs_contexts
Mar  9 10:09:07 kelley4gov kernel: Bluetooth: Core ver 2.8
Mar  9 10:09:07 kelley4gov kernel: NET: Registered protocol family 31
Mar  9 10:09:07 kelley4gov kernel: Bluetooth: HCI device and connection 
manager initialized
Mar  9 10:09:07 kelley4gov kernel: Bluetooth: HCI socket layer initialized
Mar  9 10:09:07 kelley4gov kernel: Bluetooth: L2CAP ver 2.8


Burke Almquist wrote:
> Check the logs at startup, if it is failing to start, or crashing  right 
> after boot, it should give you an idea why. Does it say anything.
> 
> On Mar 9, 2006, at 12:54 PM, Petre Scheie wrote:
> 
>> The power went out this morning and when it came back on the  K12LTSP 
>> server booted with no problems, and the thin clients were  able to 
>> connect as normal.  But I also have some Windows boxes on  the same 
>> network and they get their addresses from the LTSP server  and treat 
>> it (the server) as the default gateway, which was  working.  So far, 
>> so good.  But the Windows boxes couldn't connect  to the internet.  
>> After poking around a bit I concluded that NAT  wasn't running: there 
>> was no /proc/net/ipconntrack file.  The /etc/ init.d/nat script 
>> doesn't support the 'status' switch, so I just  ran 'service nat 
>> start', /proc/net/ipconntrack appeared, and the  Windows boxes were 
>> able to get to the internet.
>>
>> I noticed the same problem a couple months ago when I first  installed 
>> the server at the site, that NAT was not working after  bootup.  
>> chkconfig shows NAT to be on for runlevels  2-5.  What  would cause it 
>> to not start at boot?
>>
>> Petre
>>
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12osn
>> For more info see <http://www.k12os.org>
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>