astlinux-devel Mailing List for AstLinux

>>  > Most probably yes, they wont work as they don't provide binaries
>>  > compiled against uClibc. It's the same problem with g729 channel,
>>  > chan_skype and every other binary distributed by that company. On the
>>  > technical side, you could probably find some way to run them,
>>  > considering you have the code to compile or an alternative compiled
>>  > version like the uclibc g729.
>>  >
>>  > The legal issues involved are a completely different matter, and as as
>>  > far as I know, the Astlinux proyect won't distribute anything not legal
>>  > (I totally agree).
>>
>>The source is not available.  At this time, there is no legal g729 codec
>>or any known chan_skype or this fax channel that is available for
>>Astlinux.  We continue to work with Digium to convince them to compile a
>>binary, but they have been unwilling to do so at this point due to
>>support issues and the requirement to compile new versions if/when they
>>make changes or we make certain changes to Astlinux.
>>
>>If there were enough demand, Digium might make a business decision to
>>provide the binaries.  Time will tell, but based on past history, don't
>>hold your breathe.
>>
>>Darrick

>Well, I will be at the AMOOCON in Rostock (European Asterisk 
>Conference) at next Monday and Tuesday.
>http://www.amoocon.de/
>
>I will hopefully have the chance to talk to Kevin Flemming and Mark 
>Spencer from Digium.
>
>If you (devels) you could provide an exact formulation, what we need 
>for Astlinux, I could give that to them or talk about it.

(I moved that from the users list.)

What type of binary files do we need exactly for the uClibC buildroot 
environment?

Then I could ask the right questions to the guys in Rostock.

Michael

On Apr 30, 2009, at 9:15 AM, Michael Keuter wrote:

>>>
>>>
>>> One wish: could you make "/etc/rc.modules" editable in the Web-GUI.
>>> Or is this too critical for noobs?
>>
>> .....

> The real problem for me is that in the (real) console the "#" key
> (hash) is not working on a German keyboard with default (US)
> key-layout (commenting out stuff won't work that easy). So sometimes
> it would be helpful to have that file in the "Edit-Tab".

> Michael

Ahh, if /etc/rc.modules is writeable, then show it in the Edit tab.

I will add that in the next version.

Lonnie

>  > Hi Lonnie,
>>
>>  I tested it on an i586 with 2 NICs. I disabled one in /etc/rc.modules
>>  and the firewall work also with 1 NIC. I could also disable it in the
>>  WebGUI and after reboot the firewall is inactive. Cool.
>
>Michael, thanks again for the fine testing...
>
>Tip: Changing the firewall disable/enable state, followed by "Restart 
>Firewall" will apply the change without rebooting.
>
>Tip: The same idea applies to the VPN's. (ie, check/uncheck OpenVPN 
>Client, followed by "Restart OpenVPN Client")

OK, I didn't know that. Very nice.

>
>>
>>  One wish: could you make "/etc/rc.modules" editable in the Web-GUI.
>>  Or is this too critical for noobs?
>
>I recall some discussion to add a rc.conf variable that adds/ignores 
>values in the rc.modules file.  The problem is that in /etc/rc script, 
>currently, rc.modules is used before the rc.conf variables are 
>available.
>
>I'm assuming you are using unionfs (editing /etc/rc.modules) to make 
>your changes.
>
>Regardless, even if we made a MODMODS rc.conf variable, it is 
>specialized enough that user.conf would probably where it would be 
>defined.

No I don't need an extra variable in rc.conf for this time :-). If 
the changes are working after a reboot, "rc.modules" is OK for me. (I 
also remember the older discussion, there was a problem detecting the 
NICs in the right order, but that was a different thing).

The real problem for me is that in the (real) console the "#" key 
(hash) is not working on a German keyboard with default (US) 
key-layout (commenting out stuff won't work that easy). So sometimes 
it would be helpful to have that file in the "Edit-Tab".

>Lonnie

Michael

On Apr 30, 2009, at 4:41 AM, Michael Keuter wrote:

>> I've committed a solution, and the supporting web interface.
>>
>> In the web interface, I give a warning when the Firewall is enabled,
>> but has not been configured (ie. the gui.firewall.conf file does not
>> exist).
>>
>> If we need to go further to prevent single EXTIF interface users from
>> accidentally locking themselves out... please voice any suggestions.
>>
>> Lonnie
>
> Hi Lonnie,
>
> I tested it on an i586 with 2 NICs. I disabled one in /etc/rc.modules
> and the firewall work also with 1 NIC. I could also disable it in the
> WebGUI and after reboot the firewall is inactive. Cool.

Michael, thanks again for the fine testing...

Tip: Changing the firewall disable/enable state, followed by "Restart  
Firewall" will apply the change without rebooting.

Tip: The same idea applies to the VPN's. (ie, check/uncheck OpenVPN  
Client, followed by "Restart OpenVPN Client")


>
> One wish: could you make "/etc/rc.modules" editable in the Web-GUI.
> Or is this too critical for noobs?

I recall some discussion to add a rc.conf variable that adds/ignores  
values in the rc.modules file.  The problem is that in /etc/rc script,  
currently, rc.modules is used before the rc.conf variables are  
available.

I'm assuming you are using unionfs (editing /etc/rc.modules) to make  
your changes.

Regardless, even if we made a MODMODS rc.conf variable, it is  
specialized enough that user.conf would probably where it would be  
defined.

> Michael

Lonnie

>I've committed a solution, and the supporting web interface.
>
>In the web interface, I give a warning when the Firewall is enabled, 
>but has not been configured (ie. the gui.firewall.conf file does not 
>exist).
>
>If we need to go further to prevent single EXTIF interface users from 
>accidentally locking themselves out... please voice any suggestions.
>
>Lonnie

Hi Lonnie,

I tested it on an i586 with 2 NICs. I disabled one in /etc/rc.modules 
and the firewall work also with 1 NIC. I could also disable it in the 
WebGUI and after reboot the firewall is inactive. Cool.

One wish: could you make "/etc/rc.modules" editable in the Web-GUI. 
Or is this too critical for noobs?

Michael

Lonnie Abelbeck wrote:
> There has been some talk about supporting Arno's firewall on a single  
> EXTIF interface.
>
> I agree this is a good idea.
>
> Though, a fundamental change is necessary, no longer would [ -n  
> "$INTIF" ] determine if the firewall is started, but rather,
> [ "$FWVERS" = "arno" ] would.
>
> By default in /stat/etc/rc.conf, FWVERS="", disabling the firewall.
>
> Summary:  (for the moment keeping the depreciated astfw)
> 1) FWVERS="arno" # enable Arno's Firewall
>
> 2) FWVERS="astfw" # enable Kristian's Firewall
>
> 3) FWVERS="" # disable Firewall
>
>
> In the web interface, setting FWVERS="arno" would move from the  
> Firewall sub-tab to the Network tab, such as...
>
> Firewall:  _x_ Arno -- {Firewall Configuration}
>
> When checked the firewall is enabled, when unchecked (FWVERS="") the  
> firewall is disabled.
>
> Please sign-off if this is a go.
>
> Lonnie
>   

Since it could be another month before 0.7 gets committed, let's go
ahead and deprecate astfw.

We can work on getting the same functionality working in Arno during
that time.

-Philip

I've committed a solution, and the supporting web interface.

In the web interface, I give a warning when the Firewall is enabled,  
but has not been configured (ie. the gui.firewall.conf file does not  
exist).

If we need to go further to prevent single EXTIF interface users from  
accidentally locking themselves out... please voice any suggestions.

Lonnie

On Apr 29, 2009, at 10:09 AM, Michael Keuter wrote:

>> There has been some talk about supporting Arno's firewall on a single
>> EXTIF interface.
>>
>> I agree this is a good idea.
>>
>> Though, a fundamental change is necessary, no longer would [ -n
>> "$INTIF" ] determine if the firewall is started, but rather,
>> [ "$FWVERS" = "arno" ] would.
>>
>> By default in /stat/etc/rc.conf, FWVERS="", disabling the firewall.
>>
>> Summary:  (for the moment keeping the depreciated astfw)
>> 1) FWVERS="arno" # enable Arno's Firewall
>>
>> 2) FWVERS="astfw" # enable Kristian's Firewall
>>
>> 3) FWVERS="" # disable Firewall
>>
>>
>> In the web interface, setting FWVERS="arno" would move from the
>> Firewall sub-tab to the Network tab, such as...
>
> I do not find anything in the Firewall sub-tab, where could set
> FWVERS, but nevertheless it's a good idea to put it into the Network
> tab, where it belongs.
>
>> Firewall:  _x_ Arno -- {Firewall Configuration}
>>
>> When checked the firewall is enabled, when unchecked (FWVERS="") the
>> firewall is disabled.
>>
>> Please sign-off if this is a go.
>
> For me it's OK.
>
>> Lonnie
>> Michael

I like the idea as well. From what I've read on the list, it seems to me 
that arno doesn't yet have all the functionality of astfw. If that's 
true, it doesn't make sense to me to remove astfw and make it difficult 
for those in the list who needs that functionality.
If all the functionality is already there, my point is moot. I don't see 
a reason why (as long as the AstLinux user base is properly educated on 
how to configure the astfw equivalent in arno) arno couldn't be removed. 
You would just need to make sure that everyone has proper warning that 
an upgrade might not be seamless and might  require someone on site.

But hey, that's just my opinion.

 - Justin

Michael Keuter wrote:
>> There has been some talk about supporting Arno's firewall on a single 
>> EXTIF interface.
>>
>> I agree this is a good idea.
>>
>> Though, a fundamental change is necessary, no longer would [ -n 
>> "$INTIF" ] determine if the firewall is started, but rather,
>> [ "$FWVERS" = "arno" ] would.
>>
>> By default in /stat/etc/rc.conf, FWVERS="", disabling the firewall.
>>
>> Summary:  (for the moment keeping the depreciated astfw)
>> 1) FWVERS="arno" # enable Arno's Firewall
>>
>> 2) FWVERS="astfw" # enable Kristian's Firewall
>>
>> 3) FWVERS="" # disable Firewall
>>
>>
>> In the web interface, setting FWVERS="arno" would move from the 
>> Firewall sub-tab to the Network tab, such as...
>>     
>
> I do not find anything in the Firewall sub-tab, where could set 
> FWVERS, but nevertheless it's a good idea to put it into the Network 
> tab, where it belongs.
>
>   
>> Firewall:  _x_ Arno -- {Firewall Configuration}
>>
>> When checked the firewall is enabled, when unchecked (FWVERS="") the 
>> firewall is disabled.
>>
>> Please sign-off if this is a go.
>>     
>
> For me it's OK.
>
>   
>> Lonnie
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Register Now & Save for Velocity, the Web Performance & Operations
>> Conference from O'Reilly Media. Velocity features a full day of
>> expert-led, hands-on workshops and two days of sessions from industry
>> leaders in dedicated Performance & Operations tracks. Use code vel09scf
>> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>> Donations to support AstLinux are graciously accepted via PayPal to 
>> pa...@kr....
>>     
>
>
>
> Michael
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations 
> Conference from O'Reilly Media. Velocity features a full day of 
> expert-led, hands-on workshops and two days of sessions from industry 
> leaders in dedicated Performance & Operations tracks. Use code vel09scf 
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>   

>There has been some talk about supporting Arno's firewall on a single 
>EXTIF interface.
>
>I agree this is a good idea.
>
>Though, a fundamental change is necessary, no longer would [ -n 
>"$INTIF" ] determine if the firewall is started, but rather,
>[ "$FWVERS" = "arno" ] would.
>
>By default in /stat/etc/rc.conf, FWVERS="", disabling the firewall.
>
>Summary:  (for the moment keeping the depreciated astfw)
>1) FWVERS="arno" # enable Arno's Firewall
>
>2) FWVERS="astfw" # enable Kristian's Firewall
>
>3) FWVERS="" # disable Firewall
>
>
>In the web interface, setting FWVERS="arno" would move from the 
>Firewall sub-tab to the Network tab, such as...

I do not find anything in the Firewall sub-tab, where could set 
FWVERS, but nevertheless it's a good idea to put it into the Network 
tab, where it belongs.

>Firewall:  _x_ Arno -- {Firewall Configuration}
>
>When checked the firewall is enabled, when unchecked (FWVERS="") the 
>firewall is disabled.
>
>Please sign-off if this is a go.

For me it's OK.

>Lonnie
>
>
>
>
>------------------------------------------------------------------------------
>Register Now & Save for Velocity, the Web Performance & Operations
>Conference from O'Reilly Media. Velocity features a full day of
>expert-led, hands-on workshops and two days of sessions from industry
>leaders in dedicated Performance & Operations tracks. Use code vel09scf
>and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
>_______________________________________________
>Astlinux-devel mailing list
>Ast...@li...
>https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>Donations to support AstLinux are graciously accepted via PayPal to 
>pa...@kr....



Michael

There has been some talk about supporting Arno's firewall on a single  
EXTIF interface.

I agree this is a good idea.

Though, a fundamental change is necessary, no longer would [ -n  
"$INTIF" ] determine if the firewall is started, but rather,
[ "$FWVERS" = "arno" ] would.

By default in /stat/etc/rc.conf, FWVERS="", disabling the firewall.

Summary:  (for the moment keeping the depreciated astfw)
1) FWVERS="arno" # enable Arno's Firewall

2) FWVERS="astfw" # enable Kristian's Firewall

3) FWVERS="" # disable Firewall


In the web interface, setting FWVERS="arno" would move from the  
Firewall sub-tab to the Network tab, such as...

Firewall:  _x_ Arno -- {Firewall Configuration}

When checked the firewall is enabled, when unchecked (FWVERS="") the  
firewall is disabled.

Please sign-off if this is a go.

Lonnie

>Michael:
>
>The outstanding news is that anyone can contribute to Arno's Iptables
>Firewall, including you.  :-)
>
>Seriously though, it shouldn't be too hard to take
>/usr/share/arno-iptables-firewall/plugins/50ssh-brute-force-protection.plugin
>(or whatever it's called) and tweak it to do the same sort of
>rate-limiting with UDP traffic to port 5060 (or 5060-5064 or whatever).
>
>Try doing that... getting it working, and we can see about submitting it
>to Arno as part of the user contributed list of plugins.
>
>He's very receptive.  :-)
>
>-Philip

Hi Philip,

I tried it, but it doesn't seem to work with UDP connections.
There is also another limitation: the maximum rate (from the .conf file) is 20.

Michael

Lonnie Abelbeck wrote:
> On Apr 27, 2009, at 8:00 PM, Philip Prindeville wrote:
>
>   
>> Remind me:  what stops us from operating with only $EXTIF set in the
>> pbx-only case?
>>
>> -Philip
>>     
>
> iptables.init would take some rewriting to make an [ -z $INTIF ] and  
> arno work (of course if aswfw wasn't there it would be easier...)
>
> It appears to me that the astlinux.shim gracefully defaults to a  
> single external interface, except for the NAT=1.
>
> If we were to do this, there has to be some way (and be the default)  
> to disable the arno firewall, either FWVERS="" or FWVERS="no",  
> currently the firewall is disabled with [ -z $INTIF ].
>
> Lonnie
>   

Well, let's seriously consider deprecating astfw in trunk.

Then we can focus on adding whatever missing functionality there is.

-Philip

On Apr 27, 2009, at 8:00 PM, Philip Prindeville wrote:

> Remind me:  what stops us from operating with only $EXTIF set in the
> pbx-only case?
>
> -Philip

iptables.init would take some rewriting to make an [ -z $INTIF ] and  
arno work (of course if aswfw wasn't there it would be easier...)

It appears to me that the astlinux.shim gracefully defaults to a  
single external interface, except for the NAT=1.

If we were to do this, there has to be some way (and be the default)  
to disable the arno firewall, either FWVERS="" or FWVERS="no",  
currently the firewall is disabled with [ -z $INTIF ].

Lonnie

Remind me:  what stops us from operating with only $EXTIF set in the 
pbx-only case?

-Philip

Lonnie Abelbeck wrote:
> Philip,
>
> I thought we could eliminate some special cases, and dnsmasq requires  
> an internal interface.
>
> Is adding a dummy0 hack'ish to you?
>
> Lonnie
>
>
> On Apr 27, 2009, at 6:22 PM, Philip Prindeville wrote:
>
>   
>> Wouldn't it be easier to just special case the instance of PBX mode to
>> only require $EXTIF being set?
>>
>> -Philip
>>
>>
>> Lonnie Abelbeck wrote:
>>     
>>> Would setting in the linux.config...
>>>
>>> CONFIG_DUMMY=m
>>>
>>> allow us to create a dummy0 ethernet device?
>>>
>>> http://cateee.net/lkddb/web-lkddb/DUMMY.html
>>>
>>> Lonnie
>>>
>>> On Apr 27, 2009, at 5:55 PM, Lonnie Abelbeck wrote:
>>>
>>>
>>>       
>>>> On Apr 27, 2009, at 5:38 PM, Darrick Hartman (lists) wrote:
>>>>
>>>>
>>>>         
>>>>> Lonnie Abelbeck wrote:
>>>>>
>>>>>           
>>>>>> On Apr 27, 2009, at 5:07 PM, John Novack wrote:
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> May I assume this firewall module is not usable with boards that
>>>>>>> only have a single Ethernet port?
>>>>>>>
>>>>>>>
>>>>>>> John Novack
>>>>>>>
>>>>>>>               
>>>>>> Basically, yes 2+ interfaces are required.
>>>>>>
>>>>>>             
>>>>> Lonnie,
>>>>>
>>>>> While not possible with the current Astlinux setup, it IS entirely
>>>>> possible to run Arno's Firewall with only one interface.  I do this
>>>>> all
>>>>> the time to replace the stock iptables firewall on my Linux  
>>>>> installs.
>>>>> Even if a device is not providing routing functionality or acting  
>>>>> as
>>>>> the
>>>>> edge device in a network, it's still a sane security practice to
>>>>> have a
>>>>> firewall in place.
>>>>>
>>>>> Right now we have a test for intif prior to starting the firewall.
>>>>> It
>>>>> could be argued that it may be desirable to have a firewall enabled
>>>>> at
>>>>> all times.
>>>>>
>>>>> Darrick
>>>>>
>>>>>           
>>>> moved to the devel list...
>>>>
>>>> I would propose a dummy interface, such that PBX Only mode could be
>>>> eliminated, and the firewall and dnsmasq could be always enabled.
>>>>
>>>> But, let's hope single port users have a serial console, one miss
>>>> configure of the firewall, oops!  re-flash CF card.
>>>>
>>>> Does Linux support a /dev/null ethernet interface?
>>>>
>>>> Lonnie
>>>>
>>>>         
>>>       

Darrick Hartman (lists) wrote:
> Lonnie Abelbeck wrote:
>   
>> Philip,
>>
>> I thought we could eliminate some special cases, and dnsmasq requires  
>> an internal interface.
>>
>> Is adding a dummy0 hack'ish to you?
>>     
>
> It's hackish to me, so I'll assume that it's beyond hackish to Philip.
>
>   

That would be correct.

-Philip

Lonnie Abelbeck wrote:
> Philip,
> 
> I thought we could eliminate some special cases, and dnsmasq requires  
> an internal interface.
> 
> Is adding a dummy0 hack'ish to you?

It's hackish to me, so I'll assume that it's beyond hackish to Philip.


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Philip,

I thought we could eliminate some special cases, and dnsmasq requires  
an internal interface.

Is adding a dummy0 hack'ish to you?

Lonnie


On Apr 27, 2009, at 6:22 PM, Philip Prindeville wrote:

> Wouldn't it be easier to just special case the instance of PBX mode to
> only require $EXTIF being set?
>
> -Philip
>
>
> Lonnie Abelbeck wrote:
>> Would setting in the linux.config...
>>
>> CONFIG_DUMMY=m
>>
>> allow us to create a dummy0 ethernet device?
>>
>> http://cateee.net/lkddb/web-lkddb/DUMMY.html
>>
>> Lonnie
>>
>> On Apr 27, 2009, at 5:55 PM, Lonnie Abelbeck wrote:
>>
>>
>>> On Apr 27, 2009, at 5:38 PM, Darrick Hartman (lists) wrote:
>>>
>>>
>>>> Lonnie Abelbeck wrote:
>>>>
>>>>> On Apr 27, 2009, at 5:07 PM, John Novack wrote:
>>>>>
>>>>>
>>>>>> May I assume this firewall module is not usable with boards that
>>>>>> only have a single Ethernet port?
>>>>>>
>>>>>>
>>>>>> John Novack
>>>>>>
>>>>> Basically, yes 2+ interfaces are required.
>>>>>
>>>> Lonnie,
>>>>
>>>> While not possible with the current Astlinux setup, it IS entirely
>>>> possible to run Arno's Firewall with only one interface.  I do this
>>>> all
>>>> the time to replace the stock iptables firewall on my Linux  
>>>> installs.
>>>> Even if a device is not providing routing functionality or acting  
>>>> as
>>>> the
>>>> edge device in a network, it's still a sane security practice to
>>>> have a
>>>> firewall in place.
>>>>
>>>> Right now we have a test for intif prior to starting the firewall.
>>>> It
>>>> could be argued that it may be desirable to have a firewall enabled
>>>> at
>>>> all times.
>>>>
>>>> Darrick
>>>>
>>> moved to the devel list...
>>>
>>> I would propose a dummy interface, such that PBX Only mode could be
>>> eliminated, and the firewall and dnsmasq could be always enabled.
>>>
>>> But, let's hope single port users have a serial console, one miss
>>> configure of the firewall, oops!  re-flash CF card.
>>>
>>> Does Linux support a /dev/null ethernet interface?
>>>
>>> Lonnie
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code  
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
> .
>
>

Wouldn't it be easier to just special case the instance of PBX mode to 
only require $EXTIF being set?

-Philip


Lonnie Abelbeck wrote:
> Would setting in the linux.config...
>
> CONFIG_DUMMY=m
>
> allow us to create a dummy0 ethernet device?
>
> http://cateee.net/lkddb/web-lkddb/DUMMY.html
>
> Lonnie
>
> On Apr 27, 2009, at 5:55 PM, Lonnie Abelbeck wrote:
>
>   
>> On Apr 27, 2009, at 5:38 PM, Darrick Hartman (lists) wrote:
>>
>>     
>>> Lonnie Abelbeck wrote:
>>>       
>>>> On Apr 27, 2009, at 5:07 PM, John Novack wrote:
>>>>
>>>>         
>>>>> May I assume this firewall module is not usable with boards that
>>>>> only have a single Ethernet port?
>>>>>
>>>>>
>>>>> John Novack
>>>>>           
>>>> Basically, yes 2+ interfaces are required.
>>>>         
>>> Lonnie,
>>>
>>> While not possible with the current Astlinux setup, it IS entirely
>>> possible to run Arno's Firewall with only one interface.  I do this
>>> all
>>> the time to replace the stock iptables firewall on my Linux installs.
>>> Even if a device is not providing routing functionality or acting as
>>> the
>>> edge device in a network, it's still a sane security practice to
>>> have a
>>> firewall in place.
>>>
>>> Right now we have a test for intif prior to starting the firewall.   
>>> It
>>> could be argued that it may be desirable to have a firewall enabled  
>>> at
>>> all times.
>>>
>>> Darrick
>>>       
>> moved to the devel list...
>>
>> I would propose a dummy interface, such that PBX Only mode could be
>> eliminated, and the firewall and dnsmasq could be always enabled.
>>
>> But, let's hope single port users have a serial console, one miss
>> configure of the firewall, oops!  re-flash CF card.
>>
>> Does Linux support a /dev/null ethernet interface?
>>
>> Lonnie
>>     
>
>   

Would setting in the linux.config...

CONFIG_DUMMY=m

allow us to create a dummy0 ethernet device?

http://cateee.net/lkddb/web-lkddb/DUMMY.html

Lonnie

On Apr 27, 2009, at 5:55 PM, Lonnie Abelbeck wrote:

>
> On Apr 27, 2009, at 5:38 PM, Darrick Hartman (lists) wrote:
>
>> Lonnie Abelbeck wrote:
>>> On Apr 27, 2009, at 5:07 PM, John Novack wrote:
>>>
>>>> May I assume this firewall module is not usable with boards that
>>>> only have a single Ethernet port?
>>>>
>>>>
>>>> John Novack
>>>
>>> Basically, yes 2+ interfaces are required.
>>
>> Lonnie,
>>
>> While not possible with the current Astlinux setup, it IS entirely
>> possible to run Arno's Firewall with only one interface.  I do this
>> all
>> the time to replace the stock iptables firewall on my Linux installs.
>> Even if a device is not providing routing functionality or acting as
>> the
>> edge device in a network, it's still a sane security practice to
>> have a
>> firewall in place.
>>
>> Right now we have a test for intif prior to starting the firewall.   
>> It
>> could be argued that it may be desirable to have a firewall enabled  
>> at
>> all times.
>>
>> Darrick
>
> moved to the devel list...
>
> I would propose a dummy interface, such that PBX Only mode could be
> eliminated, and the firewall and dnsmasq could be always enabled.
>
> But, let's hope single port users have a serial console, one miss
> configure of the firewall, oops!  re-flash CF card.
>
> Does Linux support a /dev/null ethernet interface?
>
> Lonnie

On Apr 27, 2009, at 5:38 PM, Darrick Hartman (lists) wrote:

> Lonnie Abelbeck wrote:
>> On Apr 27, 2009, at 5:07 PM, John Novack wrote:
>>
>>> May I assume this firewall module is not usable with boards that
>>> only have a single Ethernet port?
>>>
>>>
>>> John Novack
>>
>> Basically, yes 2+ interfaces are required.
>
> Lonnie,
>
> While not possible with the current Astlinux setup, it IS entirely
> possible to run Arno's Firewall with only one interface.  I do this  
> all
> the time to replace the stock iptables firewall on my Linux installs.
> Even if a device is not providing routing functionality or acting as  
> the
> edge device in a network, it's still a sane security practice to  
> have a
> firewall in place.
>
> Right now we have a test for intif prior to starting the firewall.  It
> could be argued that it may be desirable to have a firewall enabled at
> all times.
>
> Darrick

moved to the devel list...

I would propose a dummy interface, such that PBX Only mode could be  
eliminated, and the firewall and dnsmasq could be always enabled.

But, let's hope single port users have a serial console, one miss  
configure of the firewall, oops!  re-flash CF card.

Does Linux support a /dev/null ethernet interface?

Lonnie

As for depmod, Ubuntu 9.04 does have a newer version, 3.7 compared to 3.3 on
the old Ubuntu...
david@david-ubuntu-9:~$ depmod --help
depmod 3.7-pre9 -- part of module-init-tools
depmod -[aA] [-n -e -v -q -V -r -u -w -m]
      [-b basedirectory] [forced_version]
depmod [-n -e -v -q -r -u -w] [-F kernelsyms] module1.ko module2.ko ...
If no arguments (except options) are given, "depmod -a" is assumed

depmod will output a dependancy list suitable for the modprobe utility.


Options:
-a, --all            Probe all modules
-A, --quick          Only does the work if there's a new module
-e, --errsyms        Report not supplied symbols
-m, --map            Create the legacy map files
-n, --show           Write the dependency file on stdout only
-V, --version        Print the release version
-v, --verbose        Enable verbose mode
-w, --warn Warn on duplicates
-h, --help           Print this usage message

The following options are useful for people managing distributions:
-b basedirectory
    --basedir basedirectory    Use an image of a module tree.
-F kernelsyms
    --filesyms kernelsyms      Use the file instead of the
                               current kernel symbols.
david@david-ubuntu-9:~$

On Sun, Apr 26, 2009 at 9:30 PM, David Kerr <Da...@ke...> wrote:

> OK, I've figured out the problem (but not how to fix).
>
> But first...
> Platform is an Alix 2c3 running geni586-serial version of astlinux.
> I've attached a file that is capture from serial port during boot.  Once
> booted I logged on and... cat /etc/rc.modules  (lots of modules listed)
> ps -w (yes, udevd is running)
> cd /var/log
> cat messages (so you can see the syslog)
>
> As for diff between astlinux.config and .config... There is not much to
> see, I removed a couple of packages that I don't need, like wireless stuff,
> but this is exactly the same as when I build on the older version of Ubuntu.
> But here is the diff...
>
> david@david-ubuntu-9:~/astlinux-trunk$ diff astlinux.config .config
> 37c37
> < BR2_JLEVEL=2
> ---
> > BR2_JLEVEL=1
> 172c172
> < BR2_PACKAGE_ASTERISKAPPBUNDLE=y
> ---
> > # BR2_PACKAGE_ASTERISKAPPBUNDLE is not set
> 186d185
> < BR2_PACKAGE_HOSTAP=y
> 210c209
> < BR2_PACKAGE_MADWIFI=y
> ---
> > # BR2_PACKAGE_MADWIFI is not set
> 239,242c238
> < BR2_PACKAGE_RHINO=y
> < # BR2_PACKAGE_RHINO_v1 is not set
> < # BR2_PACKAGE_RHINO_v22 is not set
> < BR2_PACKAGE_RHINO_v24=y
> ---
> > # BR2_PACKAGE_RHINO is not set
> 261c257
> < BR2_PACKAGE_WANPIPE=y
> ---
> > # BR2_PACKAGE_WANPIPE is not set
> 265c261
> < BR2_PACKAGE_WIRELESS_TOOLS=y
> ---
> > # BR2_PACKAGE_WIRELESS_TOOLS is not set
> 335c331
> < # BR2_TARGET_GENI586_SERIAL is not set
> ---
> > BR2_TARGET_GENI586_SERIAL=y
> david@david-ubuntu-9:~/astlinux-trunk$
>
>
> Now if you examine the log file you'll see that the errors are of the
> form...
> WARNING: Could not open 'kernel/drivers/net/slhc.ko': No such file or
> directory
> which is true... the files are in
> /lib/modules/2.6.26.8-astlinux/kernel/bla.bla.bla
> On a hunch I did...
> cd /
> cp -r /lib/modules/2.6.26.8-astlinux/* .
> which moved everything to the root directory. On reboot it worked.
>
> So, now I know that the kernel is not looking in the right place, for some
> reason the /lib/modules/2.6.26.8-astlinux/ is not getting prefixed to the
> name of each module.
>
> Any suggestions where I might look to try and fix?
> Darrick, does this fit with your depmod theory?
>
> By-the-way, the log file produced by script is 59,119 lines long and some
> 6MB in size. I may build again overnight on the working older Ubuntu and
> capture a log on it, then compare.
>
> Thanks,
> David
>
>
>
>
>
> On Sun, Apr 26, 2009 at 8:46 PM, Darrick Hartman (lists) <
> dha...@dj...> wrote:
>
>> Philip A. Prindeville wrote:
>>
>>> That's not a kernel issue, that's a boot script issue.
>>>
>>> binfmt_misc.ko is loaded up if minihttpd gets started.
>>>
>>> What is in your /etc/rc.modules file?  These should all have been loaded.
>>>
>>> What platform is this running on?
>>>
>>> Does your build include BR2_PACKAGE_UDEV=y?  (Kris or Darrick:  why is
>>> this an optional package with the default 'n'???)
>>>
>>> Udevd will probe your machine for devices and load the appropriate
>>> devices.  It should be run in /etc/rc in daemon mode.
>>>
>>> Does "ps -w | grep udevd" turn up anything?
>>>
>>> Send a diff of your .config file versus astlinux.config ...  Also attach
>>> the first 2 minutes following boot of your /var/log/messages file...
>>>
>>>
>> Philip--
>>
>> udev is enabled by default in the default astlinux.config.  That should
>> not be optional and should not have a default of 'n'.  In either case,
>> unless someone explicitly turned it off, it is enabled.
>>
>> David--
>>
>> To me it sounds like the depmod utility (or some other aspect related to
>> the kernel build) in the new fancy shiny version of Ubuntu handles things
>> differently than prior versions did.  That's what you get for trying out
>> something shiny and new :)  (mostly kidding)
>>
>> Darrick
>> --
>> Darrick Hartman
>> DJH Solutions, LLC
>> http://www.djhsolutions.com
>>
>
>

PC Engines ALIX.2 v0.98
640 KB Base Memory

15360
31744
48128
64512
80896
97280
113664
130048
146432
162816
179200
195584
211968
228352
244736
261120 KB Extended Memory

01F0 Master 044A                                         
Phys C/H/S 1966/16/63 Log C/H/S 983/32/63

SYSLINUX 3.35 2007-01-28 CBIOS Copyright (C) 1994-2007 H. Peter Anvin
boot: 
Loading runnix...............................
Loading runnix.img.................
Ready.
Linux version 2.6.20 (kris@krislap) (gcc version 3.4.2) #1 PREEMPT Tue May 1 15:21:29 EDT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 00000000000a0000 end: 00000000000a0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000000ff00000 end: 0000000010000000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 00000000fff00000 size: 0000000000100000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
 BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
256MB LOWMEM available.
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->    65536
  HighMem     65536 ->    65536
early_node_map[1] active PFN ranges
    0:        0 ->    65536
DMI not present or invalid.
Allocating PCI resources starting at 20000000 (gap: 10000000:eff00000)
Detected 498.054 MHz processor.
Built 1 zonelists.  Total pages: 65024
Kernel command line: initrd=runnix.img console=ttyS0,19200n8 root=/dev/ram0 rw init=/runnix runimg=auto ide=nodma BOOT_IMAGE=runnix 
ide_setup: ide=nodma : Prevented DMA
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 254980k/262144k available (2258k kernel code, 6612k reserved, 829k data, 148k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffef000 - 0xfffff000   (  64 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xd0800000 - 0xff7fe000   ( 751 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
      .init : 0xc0406000 - 0xc042b000   ( 148 kB)
      .data : 0xc0334872 - 0xc0403f0c   ( 829 kB)
      .text : 0xc0100000 - 0xc0334872   (2258 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 997.00 BogoMIPS (lpj=498501)
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 128K (32 bytes/line)
Compat vDSO mapped to ffffe000.
CPU: AMD Geode(TM) Integrated Processor by AMD PCS stepping 02
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfcc2b, last bus=0
PCI: Using configuration type 1
Setting up standard PCI resources
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: PnP BIOS support was not detected.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 896k freed
scx200: NatSemi SCx200 Driver
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
Registering unionfs 2.0
io scheduler noop registered
io scheduler cfq registered (default)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
scx200_gpio: no SCx200 gpio present
sc1200wdt: build 20020303
sc1200wdt: io parameter must be specified
Serial: 8250/16550 dr250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Intel(R) PRO/1000 Network Driver - version 7.3.15-k2
Copyright (c) 1999-2006 Intel Corporation.
pcnet32.c:v1.33 27.Jun.2006 tsb...@al...
via-rhine.c:v1.10-LK1.4.2 Sept-11-2006 Written by Donald Becker
eth0: VIA Rhine III (Management Adapter) at 0x11000, 00:0d:b9:12:e9:10, IRQ 10.
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link c5e1.
eth1: VIA Rhine III (Management Adapter) at 0x11400, 00:0d:b9:12:e9:11, IRQ 11.
eth1: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
eth2: VIA Rhine III (Management Adapter) at 0x11800, 00:0d:b9:12:e9:12, IRQ 12.
eth2: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
PPP generic driver version 2.4.2
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <ma...@qu...>
airo(): Probing for PCI adapters
airo(): Finished probing for PCI adapters
Loaded prism54 driver, version 1.2
usbcore: registered new interface driver zd1201
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
winbond-840.c:v1.01-e (2.4 port) Sep-11-2006  Donald Becker <be...@sc...>
  http://www.scyld.com/network/drivers.html
uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: , ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 1981728 sectors (1014 MB) w/1KiB Cache, CHS=1966/16/63
 hda: hda1 hda2
ehci_hcd 0000:00:0f.5: EHCI Host Controller
ehci_hcd 0000:00:0f.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0f.5: irq 15, io mem 0xefffd000
ehci_hcd 0000:00:0f.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ohci_hcd 0000:00:0f.4: OHCI Host Controller
ohci_hcd 0000:00:0f.4: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0f.4: irq 15, io mem 0xefffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usbcore: registered new interface driver catc
drivers/usb/net/catc.c: v2.8 CATC EL1210A NetMate USB Ethernet driver
usbcore: registered new interface driver kaweth
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver gl620a
usbcore: registered new interface driver net1080
usbcore: registered new interface driver plusb
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...>
All bugs added by David S. Miller <da...@re...>
Using IPI Shortcut mode
RAMDISK: Compressed image found at block 0
Time: tsc clocksource has been installed.
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 148k freed
proc mounted
Verifying astlinux-trunk-2627.run...
astlinux-trunk-2627.run verified
Root mounted
Custom initrd /mnt/base/os/initrd.img found
Custom kernel /mnt/root/boot/bzImage found
Copying kernel and initrd to ramdisk...
Unmounting image...
Trying kexec...
Starting new kernel
Linux version 2.6.26.8-astlinux (david@david-ubuntu-9) (gcc version 4.1.2) #1 PREEMPT Sun Apr 26 16:29:15 EDT 2009
PAT not supported by CPU.
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000100 - 00000000000a0000 (usable)
 BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
 BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
256MB LOWMEM available.
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->    65536
  HighMem     65536 ->    65536
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->    65536
DMI not present or invalid.
ACPI Error (tbxfroot-0218): A valid RSDP was not found [20080321]
Allocating PCI resources starting at 20000000 (gap: 10000000:eff00000)
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: root=/dev/ram0 rw init=/linuxrc astlinux=geni586 astimg=astlinux-trunk-2627.run astkd=auto asturw=auto astlive astlive ide=nodma console=ttyS0,19200n8
ide_setup: ide=nodma : Prevented DMA
 -- OBSOLETE OPTION, WILL BE REMOVED SOON!
No local APIC present or hardware disabled
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Detected 498.056 MHz processor.
Console: colour dummy device 80x25
console [ttyS0] enabled
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 255580k/262144k available (2026k kernel code, 6040k reserved, 890k data, 200k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffa7000 - 0xfffff000   ( 352 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xd0800000 - 0xff7fe000   ( 751 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
      .init : 0xc03dc000 - 0xc040e000   ( 200 kB)
      .data : 0xc02faaf7 - 0xc03d9480   ( 890 kB)
      .text : 0xc0100000 - 0xc02faaf7   (2026 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
Calibrating delay using timer specific routine.. 997.22 BogoMIPS (lpj=498613)
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 128K (32 bytes/line)
CPU: AMD Geode(TM) Integrated Processor by AMD PCS stepping 02
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
ACPI: Core revision 20080321
ACPI Exception (tbxface-0629): AE_NO_ACPI_TABLES, While loading namespace from ACPI tables [20080321]
ACPI: Unable to load the System Description Tables
net_namespace: 644 bytes
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfcc2b, last bus=0
PCI: Using configuration type 1 for base access
Setting up standard PCI resources
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 419k freed
squashfs: version 3.4 (2008/08/26) Phillip Lougher
Registering unionfs 2.5.1 (for 2.6.26.8)
msgmni has been set to 500
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
floppy0: no floppy controllers found
brd: module loaded
loop: module loaded
Uniform Multi-Platform E-IDE driver
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD5536: 0000:00:0f.2 (rev 01) UDMA100 controller
AMD5536: IDE controller (0x1022:0x209a rev 0x01) at  PCI slot 0000:00:0f.2
AMD5536: not 100% native mode: will probe irqs later
AMD5536: IDE port disabled
    ide0: BM-DMA at 0xff00-0xff07
Clocksource tsc unstable (delta = 217960749 ns)
hda: , ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
ide_generic: I/O resource 0x170-0x177 not free.
hda: max request size: 128KiB
hda: 1981728 sectors (1014 MB) w/1KiB Cache, CHS=1966/16/63
 hda: hda1 hda2
aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
stex: Promise SuperTrak EX Driver version: 3.6.0000.1
Driver 'sd' needs updating - please use bus_type methods
ehci_hcd 0000:00:0f.5: EHCI Host Controller
ehci_hcd 0000:00:0f.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0f.5: irq 15, io mem 0xefffd000
ehci_hcd 0000:00:0f.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ohci_hcd 0000:00:0f.4: OHCI Host Controller
ohci_hcd 0000:00:0f.4: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0f.4: irq 15, io mem 0xefffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input0
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
Using IPI Shortcut mode
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 200k freed
Looking for AstLinux image...
AstLinux image found!
Configuring for unionfs...
Checking asturw filesystem
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda2 is mounted.

Asturw filesystem clean.
Copying AstLinux files to RAM...
unmounting squashfs image
unmounting /cdrom
Pivoting...

init started: Bunionfs: new lower inode mtime (bindex=1, name=console)
usyBox v1.12.4 (2009-04-26 16:34:48 EDT)
unionfs: new lower inode mtime (bindex=1, name=etc)
unionfs: new lower inode mtime (bindex=1, name=etc)
Runnix vfat partition re-mounted read-only
going to runlevel default...
No Zap hardware - loading ztdummy
WARNING: Could not open 'kernel/drivers/net/slhc.ko': No such file or directory
WARNING: Could not open 'kernel/drivers/net/ppp_generic.ko': No such file or directory
WARNING: Could not open 'kernel/drivers/net/wan/hdlc.ko': No such file or directory
WARNING: Could not open 'misc/zaptel.ko': No such file or directory
FATAL: Could not open 'misc/ztdummy.ko': No such file or directory
Bringing up eth1 as 192.168.1.1
ifconfig: SIOCSIFADDR: No such device
route: SIOCADDRT: No such device
udhcpc: SIOCGIFINDEX: No such device
Starting syslogd...
Starting crond...
Starting iptables...
Arno's Iptables Firewall Script v1.9.1-BETA2-DEVEL
-------------------------------------------------------------------------------
NOTE: External interface eth0 does NOT exist (yet?)
NOTE: Internal interface eth1 does NOT exist (yet?)
Sanity checks passed...OK
Checking/probing IPv4 Iptables modules:
 modprobe ip_tables (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
 modprobe ip_conntrack (1): WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko': No such file or directory
 modprobe ip_conntrack_ftp (1): WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/nf_conntrack_ftp.ko': No such file or directory
 modprobe ipt_conntrack (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_conntrack.ko': No such file or directory
 modprobe ipt_limit (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_limit.ko': No such file or directory
 modprobe ipt_state (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_state.ko': No such file or directory
 modprobe ipt_multiport (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_multiport.ko': No such file or directory
 modprobe iptable_filter (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/iptable_filter.ko': No such file or directory
 modprobe iptable_mangle (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/iptable_mangle.ko': No such file or directory
 modprobe ipt_REJECT (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ipt_REJECT.ko': No such file or directory
 modprobe ipt_LOG (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ipt_LOG.ko': No such file or directory
 modprobe ipt_TCPMSS (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_TCPMSS.ko': No such file or directory
 modprobe ip_nat_ftp (1): WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/nf_conntrack_ftp.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_nat.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/nf_nat_ftp.ko': No such file or directory
 modprobe iptable_nat (1): WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_nat.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/iptable_nat.ko': No such file or directory
 modprobe ipt_MASQUERADE (1): WARNING: Could not open 'kernel/net/netfilter/nf_conntrack.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko': No such file or directory
WARNING: Could not open 'kernel/net/ipv4/netfilter/nf_nat.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ipt_MASQUERADE.ko': No such file or directory
 modprobe ipt_TOS (1): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/netfilter/xt_DSCP.ko': No such file or directory
 Module check done...
Setting the kernel ring buffer to only log panic messages to the console
Setup kernel settings:
 Setting the max. amount of simultaneous connections to 16384
 WARNING: ...ip_conntrack_max could NOT be set. This may be a problem!
 Setting default conntrack timeouts
 WARNING: ...conntrack_udp_timeout could NOT be set. This may be a problem!
 WARNING: ...conntrack_udp_timeout_stream could NOT be set. This may be a problem!
 Enabling protection against source routed packets
 Enabling packet forwarding
 Enabling reduction of the DoS'ing ability
 Enabling anti-spoof with rp_filter
 Enabling SYN-flood protection via SYN-cookies
 Disabling the logging of martians
 Disabling the acception of ICMP-redirect messages
 Setting default TTL=64
 Disabling ECN (Explicit Congestion Notification)
 Enabling kernel support for dynamic IP's
 Flushing route table
 Kernel setup done...
Initializing firewall chains
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
 Setting default INPUT/FORWARD policy to DROP
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Using loglevel "info" for syslogd

Setting up firewall rules:
-------------------------------------------------------------------------------
Enabling setting the maximum packet size via MSS
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Enabling mangling TOS
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `mangle': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables (3): WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file...
 
[truncated message content]

Philip A. Prindeville wrote:
> That's not a kernel issue, that's a boot script issue.
> 
> binfmt_misc.ko is loaded up if minihttpd gets started.
> 
> What is in your /etc/rc.modules file?  These should all have been loaded.
> 
> What platform is this running on?
> 
> Does your build include BR2_PACKAGE_UDEV=y?  (Kris or Darrick:  why is this an optional package with the default 'n'???)
> 
> Udevd will probe your machine for devices and load the appropriate devices.  It should be run in /etc/rc in daemon mode.
> 
> Does "ps -w | grep udevd" turn up anything?
> 
> Send a diff of your .config file versus astlinux.config ...  Also attach the first 2 minutes following boot of your /var/log/messages file...
> 

Philip--

udev is enabled by default in the default astlinux.config.  That should 
not be optional and should not have a default of 'n'.  In either case, 
unless someone explicitly turned it off, it is enabled.

David--

To me it sounds like the depmod utility (or some other aspect related to 
the kernel build) in the new fancy shiny version of Ubuntu handles 
things differently than prior versions did.  That's what you get for 
trying out something shiny and new :)  (mostly kidding)

Darrick
-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

That's not a kernel issue, that's a boot script issue.

binfmt_misc.ko is loaded up if minihttpd gets started.

What is in your /etc/rc.modules file?  These should all have been loaded.

What platform is this running on?

Does your build include BR2_PACKAGE_UDEV=y?  (Kris or Darrick:  why is this an optional package with the default 'n'???)

Udevd will probe your machine for devices and load the appropriate devices.  It should be run in /etc/rc in daemon mode.

Does "ps -w | grep udevd" turn up anything?

Send a diff of your .config file versus astlinux.config ...  Also attach the first 2 minutes following boot of your /var/log/messages file...

-Philip


David Kerr wrote:
> I'll kick off a build using the script command you suggest. In the
> meantime, I run lsmod on the booted system and it shows *no* loaded
> modules, in contrast to a working system that has probably two dozen
> loaded modules.
> 
> I looked in /lib/modules/2.6.26.8-astlinux/kernel/fs/binfmt_misc.ko and
> it is there, as are lots of other modules.
> 
> Something appears to be wrong with module loading into the kernel.
> 
> What should I look for in the log file generated by the script command?
> 
> Thanks,
> David
> 
> 
> 
> On Sun, Apr 26, 2009 at 2:50 PM, Philip A. Prindeville
> <phi...@re...
> <mailto:phi...@re...>> wrote:
> 
>     Try:
> 
>     script -c "make all runfs" build.log
> 
>     and also on your booted system, do:
> 
>     % lsmod
> 
>     and look for binfmt_misc ...  Is it loaded?  Is there a:
> 
>     -rw-rw-r--    1 root     root        12952 Apr  3 00:38
>     /lib/modules/2.6.26.8-astlinux/kernel/fs/binfmt_misc.ko
> 
> 
>     file?
> 
>     -Philip
> 
> 
>     David Kerr wrote:
>     > Does script do more than capture the output from make?  I have been
>     > using...
>     >
>     > time make | tee output.txt
>     >
>     > which captures output into a file as well as on the screen.
>     >
>     > Also, I double checked mounted file systems and found a difference...
>     >
>     > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
>     >
>     > is listed on the WORKING version, but not on the non-working version.
>     >  Does this give any clues?
>     >
>     > David
>     >
>     > On Sun, Apr 26, 2009 at 1:26 PM, Darrick Hartman
>     > <dha...@dj... <mailto:dha...@dj...>
>     <mailto:dha...@dj...
>     <mailto:dha...@dj...>>> wrote:
>     >
>     >     David,
>     >
>     >     I'm not an Ubuntu user so I can't say exactly what changed in
>     Ubuntu
>     >     between prior releases and this new one.  Sounds like some of the
>     >     development binaries were changed and may be causing some of the
>     >     issues
>     >     you're seeing.
>     >
>     >     You're looking at the symptom, but not the root cause.  To
>     really find
>     >     out what's going on, you'd need to build a new image running
>     inside
>     >     script, then examine the resultant script file to look for
>     oddities.
>     >
>     >     Having said that, I haven't built an image from trunk in a few
>     weeks.
>     >     Philip has build several lately on Fedora 9 (I believe).
>     >
>     >     So, to build and have it captured to a file, use the 'script'
>     >     program as
>     >     follows:
>     >
>     >     script foobarbuild.txt
>     >     (should say something like starting script with output to
>     >     foobarbuild.txt)
>     >
>     >     Then continue with make as normal.  When done with make, type
>     exit to
>     >     end the script.  You can then examine the foobarbuild.txt
>     >
>     >     Darrick
>     >
>     >     David Kerr wrote:
>     >     > I'm still struggling with this...  I rebuilt from scratch
>     overnight
>     >     > (including toolchain) trunk 2627 with the same results...
>     >     version built
>     >     > on Ubuntu 9.04 does not run, get messages listed in my
>     previous post
>     >     > during boot.
>     >     >
>     >     > I do get to a login prompt, so I can login and attempt to
>     >     diagnose the
>     >     > problem. I looked for the kernel modules that are failing with
>     >     the  "No
>     >     > such file or directory" message and they ARE there...
>     >     > in ./lib/modules/2.6.26.8-astlinux/kernel which is exactly
>     the same
>     >     > place place as on the working version.
>     >     >
>     >     > I captured all the messages generated during each build, and did
>     >     a file
>     >     > compare using TkDiff program. There are no differences that I
>     >     can see
>     >     > that would have anything to do with this.
>     >     >
>     >     > I am using the same CF card for both boots, so there are no
>     >     differences
>     >     > in the asturw partition, or kd.
>     >     >
>     >     > I'm not sure what else to look for. Any suggestions would be
>     >     welcome.
>     >     >
>     >     > Thanks
>     >     > David
>     >     >
>     >     >
>     >     >
>     >     > ---------- Forwarded message ----------
>     >     > From: *David Kerr* <Da...@ke... <mailto:Da...@ke...>
>     <mailto:Da...@ke... <mailto:Da...@ke...>>
>     >     <mailto:Da...@ke... <mailto:Da...@ke...>
>     <mailto:Da...@ke... <mailto:Da...@ke...>>>>
>     >     > Date: Sat, Apr 25, 2009 at 6:11 PM
>     >     > Subject: Building on Ubuntu 9.04
>     >     > To: AstLinux Developers Mailing List
>     >     > <ast...@li...
>     <mailto:ast...@li...>
>     >     <mailto:ast...@li...
>     <mailto:ast...@li...>>
>     >     > <mailto:ast...@li...
>     <mailto:ast...@li...>
>     >     <mailto:ast...@li...
>     <mailto:ast...@li...>>>>
>     >     >
>     >     >
>     >     > So, I decided to install an Ubuntu 9.04 image and try and build
>     >     Astlinux
>     >     > on it.  I installed all the required packages, set sh to bash,
>     >      and the
>     >     > whole thing (trunk 2425) builds. But it doesn't run.  Building
>     >     on my old
>     >     > Ubunty 8.04 image works.  Capturing output from my Alix serial
>     >     port....
>     >     >
>     >     > WORKING VERSION... (built on Ubuntu 8.04)
>     >     > Copying AstLinux files to RAM...
>     >     > unmounting squashfs image
>     >     > unmounting /cdrom
>     >     > Pivoting...
>     >     >
>     >     > init started: Bunionfs: new lower inode mtime (bindex=1,
>     >     name=console)
>     >     > usyBox v1.12.4 (2009-04-25 12:48:54 EDT)
>     >     > unionfs: new lower inode mtime (bindex=1, name=etc)
>     >     > Linux Tulip driver version 1.1.15 (Feb 27, 2007)
>     >     > eepro100.c:v1.09j-t 9/29/99 Donald Becker
>     >     > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
>     >     Savochkin
>     >     > <sa...@sa... <mailto:sa...@sa...>
>     <mailto:sa...@sa... <mailto:sa...@sa...>>
>     >     <mailto:sa...@sa... <mailto:sa...@sa...>
>     <mailto:sa...@sa... <mailto:sa...@sa...>>>> and others
>     >     > natsemi dp8381x driver, version 2.1, Sept 11, 2006
>     >     >   originally by Donald Becker <be...@sc...
>     <mailto:be...@sc...>
>     >     <mailto:be...@sc... <mailto:be...@sc...>>
>     <mailto:be...@sc... <mailto:be...@sc...>
>     >     <mailto:be...@sc... <mailto:be...@sc...>>>>
>     >     >   2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
>     >     > 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
>     >     > 8139too Fast Ethernet driver 0.9.28
>     >     > via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
>     >     > eth0: VIA Rhine III (Management Adapter) at 0xe0000000,
>     >     > 00:0d:b9:12:e9:10, IRQ 10.
>     >     > eth0: MII PHY found at address 1, status 0x786d advertising 05e1
>     >     Link c5e1.
>     >     > eth1: VIA Rhine III (Management Adapter) at 0xe0040000,
>     >     > 00:0d:b9:12:e9:11, IRQ 11.
>     >     > eth1: MII PHY found at address 1, status 0x7849 advertising 05e1
>     >     Link 0000.
>     >     > eth2: VIA Rhine III (Management Adapter) at 0xe0080000,
>     >     > 00:0d:b9:12:e9:12, IRQ 12.
>     >     > eth2: MII PHY found at address 1, status 0x7849 advertising 05e1
>     >     Link 0000.
>     >     > pcnet32.c:v1.35 21.Apr.2008 tsb...@al...
>     <mailto:tsb...@al...>
>     >     <mailto:tsb...@al...
>     <mailto:tsb...@al...>>
>     >     > <mailto:tsb...@al...
>     <mailto:tsb...@al...>
>     >     <mailto:tsb...@al...
>     <mailto:tsb...@al...>>>
>     >     > Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
>     >     > Copyright (c) 1999-2006 Intel Corporation.
>     >     > ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
>     >     > unionfs: new lower inode mtime (bindex=1, name=etc)
>     >     > Runnix vfat partition re-mounted read-only
>     >     > going to runlevel default...
>     >     > No Zap hardware - loading ztdummy
>     >     > PPP generic driver version 2.4.2
>     >     > HDLC support module revision 1.22
>     >     > Zapata Telephony Interface Registered on major 196
>     >     > Zaptel Version: 1.4.12.1
>     >     > Zaptel Echo Canceller: MG2
>     >     > ztdummy: High Resolution Timer started, good to go
>     >     > Bringing up eth1eth1: link down
>     >     >  as 192.168.1.1
>     >     > udhcpc (v1.12.4) started
>     >     > eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
>     >     > Sending discover...
>     >     >
>     >     >
>     >     >
>     >     > BROKEN VERSION... (Built on Ubuntu 9.04)
>     >     > Copying AstLinux files to RAM...
>     >     > unmounting squashfs image
>     >     > unmounting /cdrom
>     >     > Pivoting...
>     >     >
>     >     > init started: Bunionfs: new lower inode mtime (bindex=1,
>     >     name=console)
>     >     > usyBox v1.12.4 (2009-04-25 16:10:37 EDT)
>     >     > unionfs: new lower inode mtime (bindex=1, name=etc)
>     >     > unionfs: new lower inode mtime (bindex=1, name=etc)
>     >     > Runnix vfat partition re-mounted read-only
>     >     > going to runlevel default...
>     >     > No Zap hardware - loading ztdummy
>     >     > WARNING: Could not open 'kernel/drivers/net/slhc.ko': No such
>     >     file or
>     >     > directory
>     >     > WARNING: Could not open 'kernel/drivers/net/ppp_generic.ko':
>     No such
>     >     > file or directory
>     >     > WARNING: Could not open 'kernel/drivers/net/wan/hdlc.ko': No
>     >     such file
>     >     > or directory
>     >     > WARNING: Could not open 'misc/zaptel.ko': No such file or
>     directory
>     >     > FATAL: Could not open 'misc/ztdummy.ko': No such file or
>     directory
>     >     > Bringing up eth1 as 192.168.1.1
>     >     > ifconfig: SIOCSIFADDR: No such device
>     >     > route: SIOCADDRT: No such device
>     >     > udhcpc: SIOCGIFINDEX: No such device
>     >     > Starting syslogd...
>     >     >
>     >     >
>     >     > As you can see, something has got screwed up with kernel device
>     >     drivers.
>     >     >
>     >     > I have cleaned out build_i586 and rebuilt twice. Same problems.
>     >      Anyone
>     >     > got any suggestion of where I should look?
>     >     >
>     >     > Thanks
>     >     >
>     >     > David
>     >
> 
> 

I'll kick off a build using the script command you suggest. In the meantime,
I run lsmod on the booted system and it shows *no* loaded modules, in
contrast to a working system that has probably two dozen loaded modules.
I looked in /lib/modules/2.6.26.8-astlinux/kernel/fs/binfmt_misc.ko and it
is there, as are lots of other modules.

Something appears to be wrong with module loading into the kernel.

What should I look for in the log file generated by the script command?

Thanks,
David



On Sun, Apr 26, 2009 at 2:50 PM, Philip A. Prindeville <
phi...@re...> wrote:

> Try:
>
> script -c "make all runfs" build.log
>
> and also on your booted system, do:
>
> % lsmod
>
> and look for binfmt_misc ...  Is it loaded?  Is there a:
>
> -rw-rw-r--    1 root     root        12952 Apr  3 00:38
> /lib/modules/2.6.26.8-astlinux/kernel/fs/binfmt_misc.ko
>
>
> file?
>
> -Philip
>
>
> David Kerr wrote:
> > Does script do more than capture the output from make?  I have been
> > using...
> >
> > time make | tee output.txt
> >
> > which captures output into a file as well as on the screen.
> >
> > Also, I double checked mounted file systems and found a difference...
> >
> > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> >
> > is listed on the WORKING version, but not on the non-working version.
> >  Does this give any clues?
> >
> > David
> >
> > On Sun, Apr 26, 2009 at 1:26 PM, Darrick Hartman
> > <dha...@dj... <mailto:dha...@dj...>> wrote:
> >
> >     David,
> >
> >     I'm not an Ubuntu user so I can't say exactly what changed in Ubuntu
> >     between prior releases and this new one.  Sounds like some of the
> >     development binaries were changed and may be causing some of the
> >     issues
> >     you're seeing.
> >
> >     You're looking at the symptom, but not the root cause.  To really
> find
> >     out what's going on, you'd need to build a new image running inside
> >     script, then examine the resultant script file to look for oddities.
> >
> >     Having said that, I haven't built an image from trunk in a few weeks.
> >     Philip has build several lately on Fedora 9 (I believe).
> >
> >     So, to build and have it captured to a file, use the 'script'
> >     program as
> >     follows:
> >
> >     script foobarbuild.txt
> >     (should say something like starting script with output to
> >     foobarbuild.txt)
> >
> >     Then continue with make as normal.  When done with make, type exit to
> >     end the script.  You can then examine the foobarbuild.txt
> >
> >     Darrick
> >
> >     David Kerr wrote:
> >     > I'm still struggling with this...  I rebuilt from scratch overnight
> >     > (including toolchain) trunk 2627 with the same results...
> >     version built
> >     > on Ubuntu 9.04 does not run, get messages listed in my previous
> post
> >     > during boot.
> >     >
> >     > I do get to a login prompt, so I can login and attempt to
> >     diagnose the
> >     > problem. I looked for the kernel modules that are failing with
> >     the  "No
> >     > such file or directory" message and they ARE there...
> >     > in ./lib/modules/2.6.26.8-astlinux/kernel which is exactly the same
> >     > place place as on the working version.
> >     >
> >     > I captured all the messages generated during each build, and did
> >     a file
> >     > compare using TkDiff program. There are no differences that I
> >     can see
> >     > that would have anything to do with this.
> >     >
> >     > I am using the same CF card for both boots, so there are no
> >     differences
> >     > in the asturw partition, or kd.
> >     >
> >     > I'm not sure what else to look for. Any suggestions would be
> >     welcome.
> >     >
> >     > Thanks
> >     > David
> >     >
> >     >
> >     >
> >     > ---------- Forwarded message ----------
> >     > From: *David Kerr* <Da...@ke... <mailto:Da...@ke...>
> >     <mailto:Da...@ke... <mailto:Da...@ke...>>>
> >     > Date: Sat, Apr 25, 2009 at 6:11 PM
> >     > Subject: Building on Ubuntu 9.04
> >     > To: AstLinux Developers Mailing List
> >     > <ast...@li...
> >     <mailto:ast...@li...>
> >     > <mailto:ast...@li...
> >     <mailto:ast...@li...>>>
> >     >
> >     >
> >     > So, I decided to install an Ubuntu 9.04 image and try and build
> >     Astlinux
> >     > on it.  I installed all the required packages, set sh to bash,
> >      and the
> >     > whole thing (trunk 2425) builds. But it doesn't run.  Building
> >     on my old
> >     > Ubunty 8.04 image works.  Capturing output from my Alix serial
> >     port....
> >     >
> >     > WORKING VERSION... (built on Ubuntu 8.04)
> >     > Copying AstLinux files to RAM...
> >     > unmounting squashfs image
> >     > unmounting /cdrom
> >     > Pivoting...
> >     >
> >     > init started: Bunionfs: new lower inode mtime (bindex=1,
> >     name=console)
> >     > usyBox v1.12.4 (2009-04-25 12:48:54 EDT)
> >     > unionfs: new lower inode mtime (bindex=1, name=etc)
> >     > Linux Tulip driver version 1.1.15 (Feb 27, 2007)
> >     > eepro100.c:v1.09j-t 9/29/99 Donald Becker
> >     > eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V.
> >     Savochkin
> >     > <sa...@sa... <mailto:sa...@sa...>
> >     <mailto:sa...@sa... <mailto:sa...@sa...>>> and others
> >     > natsemi dp8381x driver, version 2.1, Sept 11, 2006
> >     >   originally by Donald Becker <be...@sc...
> >     <mailto:be...@sc...> <mailto:be...@sc...
> >     <mailto:be...@sc...>>>
> >     >   2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
> >     > 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
> >     > 8139too Fast Ethernet driver 0.9.28
> >     > via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
> >     > eth0: VIA Rhine III (Management Adapter) at 0xe0000000,
> >     > 00:0d:b9:12:e9:10, IRQ 10.
> >     > eth0: MII PHY found at address 1, status 0x786d advertising 05e1
> >     Link c5e1.
> >     > eth1: VIA Rhine III (Management Adapter) at 0xe0040000,
> >     > 00:0d:b9:12:e9:11, IRQ 11.
> >     > eth1: MII PHY found at address 1, status 0x7849 advertising 05e1
> >     Link 0000.
> >     > eth2: VIA Rhine III (Management Adapter) at 0xe0080000,
> >     > 00:0d:b9:12:e9:12, IRQ 12.
> >     > eth2: MII PHY found at address 1, status 0x7849 advertising 05e1
> >     Link 0000.
> >     > pcnet32.c:v1.35 21.Apr.2008 tsb...@al...
> >     <mailto:tsb...@al...>
> >     > <mailto:tsb...@al...
> >     <mailto:tsb...@al...>>
> >     > Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
> >     > Copyright (c) 1999-2006 Intel Corporation.
> >     > ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
> >     > unionfs: new lower inode mtime (bindex=1, name=etc)
> >     > Runnix vfat partition re-mounted read-only
> >     > going to runlevel default...
> >     > No Zap hardware - loading ztdummy
> >     > PPP generic driver version 2.4.2
> >     > HDLC support module revision 1.22
> >     > Zapata Telephony Interface Registered on major 196
> >     > Zaptel Version: 1.4.12.1
> >     > Zaptel Echo Canceller: MG2
> >     > ztdummy: High Resolution Timer started, good to go
> >     > Bringing up eth1eth1: link down
> >     >  as 192.168.1.1
> >     > udhcpc (v1.12.4) started
> >     > eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
> >     > Sending discover...
> >     >
> >     >
> >     >
> >     > BROKEN VERSION... (Built on Ubuntu 9.04)
> >     > Copying AstLinux files to RAM...
> >     > unmounting squashfs image
> >     > unmounting /cdrom
> >     > Pivoting...
> >     >
> >     > init started: Bunionfs: new lower inode mtime (bindex=1,
> >     name=console)
> >     > usyBox v1.12.4 (2009-04-25 16:10:37 EDT)
> >     > unionfs: new lower inode mtime (bindex=1, name=etc)
> >     > unionfs: new lower inode mtime (bindex=1, name=etc)
> >     > Runnix vfat partition re-mounted read-only
> >     > going to runlevel default...
> >     > No Zap hardware - loading ztdummy
> >     > WARNING: Could not open 'kernel/drivers/net/slhc.ko': No such
> >     file or
> >     > directory
> >     > WARNING: Could not open 'kernel/drivers/net/ppp_generic.ko': No
> such
> >     > file or directory
> >     > WARNING: Could not open 'kernel/drivers/net/wan/hdlc.ko': No
> >     such file
> >     > or directory
> >     > WARNING: Could not open 'misc/zaptel.ko': No such file or directory
> >     > FATAL: Could not open 'misc/ztdummy.ko': No such file or directory
> >     > Bringing up eth1 as 192.168.1.1
> >     > ifconfig: SIOCSIFADDR: No such device
> >     > route: SIOCADDRT: No such device
> >     > udhcpc: SIOCGIFINDEX: No such device
> >     > Starting syslogd...
> >     >
> >     >
> >     > As you can see, something has got screwed up with kernel device
> >     drivers.
> >     >
> >     > I have cleaned out build_i586 and rebuilt twice. Same problems.
> >      Anyone
> >     > got any suggestion of where I should look?
> >     >
> >     > Thanks
> >     >
> >     > David
> >
>
>