Re: How to secure Ethernet environment on L4 Linux ?

Matthias Lange <[email protected]>
Newsgroups gmane.comp.micro-kernel.l4.devel
Message-ID <[email protected]>
Hi,

On 21.04.2014, at 03:44, Taeung <[email protected]> wrote:

> Hi, Matthias.
> 
> Thank you for answering.
> 
> Sorry, I apologize for the late response. 
> 
> I've configured the NIC driver as follows.. '[*]Network support ' and '[*]Network device driver support'.
> 
> I don't know how to init the driver,but when I run 'ifconfig', I saw nothing.

What I meant was, do you see any log output from the driver when L4Linux is booting? You can check the driver sources for ‘printk’ or ‘pr_[info,err,dbg]’ statements so that you know what you have to look for.

Matthias.

> So, I guess that the cause is 'init' could not have been run.
> When I've done booting L4Linux, I found '/etc' folder is not enough.
> And I found '/proc' and '/sys' is empty. 
> So, I've manually mounted '/proc' and '/sys'.
> And I'm trying to run 'ifup -a' but I've failed secure Ethernet on L4 Linux.
> 
> What I mistake ? 
> 
> (Mentioned above is same as mail before last)
> 
> And I'm doubting 'arm-rv.io' and  'l4lx_xs.cfg' I'm using.
> Must I modify them ?  
> 
> If you give me small hints, I'd apperciate. 
> Thank you !! 
> 
> For reference.
> 
> I'm using 'entry L4Linux_XS' as follows
> ========================
> entry L4Linux_XS
> roottask moe rom/l4lx_xs.cfg
> module l4re
> module ned
> module l4lx_xs.cfg
> module io
> module arm-rv.io
> module vmlinuz.arm
> module ramdisk-arm.rd
> ========================
> arm-rv.io in example folder is..
> ========================
> hw-root
> {
>   NIC => new Device()
>   {
>     .hid = "smsc911x";
>     new-res Mmio(0x4e000000 .. 0x4e000fff);
>     new-res Irq(60);
>   }
> }
> 
> l4lx => new System_bus()
> {
>   NIC => wrap(hw-root.NIC);
> } 
> ========================
> l4lx_xs.cfg is ..
> ========================
> -- vim:set ft=lua:
> 
> local lxname = "vmlinuz";
> if L4.Info.arch() == "arm" then
>   lxname = "vmlinuz.arm";
> end
> 
> L4.default_loader:start(
>   { caps = {
>       log = L4.Env.log:m("rws"),
>     },
>     l4re_dbg = L4.Dbg.Warn,
>     log = { "l4linux", "yellow" },
>   },
>   "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" ..  L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=/bin/sh");
> ========================
> 
> - Taeung -
> 
> 
> 
> On 04/18/2014 09:21 PM, Matthias Lange wrote:
>> Hi,
>> 
>> On 18.04.2014, at 13:24, Taeung <[email protected]> wrote:
>>> Hello, Adam and L4 Hackers.
>>> Thanks for answering.
>>> 
>>> When I run 'ifconfig', nothing have happened.
>>> I guess that the cause is /etc folder in ramdisk is not enough to run 'init'. 
>>> 
>>> Would you mind if I ask you another question ? 
>>> 
>>> Must also I modify 'arm-rv.io' ? 
>>> or must I modify 'l4lx_xs.cfg' ? 
>>> or Do not I need do it ? 
>>> 
>>> If I have to modify them , how to modify  ? 
>>> (I'm using Freescale imx6q SABRE SD board.)
>>> 
>>> If you give a bit me hints, I'd appreciate.
>> Do you have configured the NIC driver into L4Linux? Do you see L4Linux trying to init the driver. I fear your questions are to generic to give a specific answer.
>> 
>> Matthias.
>> 
>> 
>> --
>> [email protected] - Tel. 0351-41 888 614
>> 
>> Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
>> Geschäftsführer: Dr.-Ing. Michael Hohmuth
>> 
> 

-- 
Matthias Lange, [email protected]

Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
signature.asc (application/pgp-signature, 163 B)
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlNVNQ8ACgkQOeivt3XjYv82yACfXbO/VNp6PMlsCSjtRyxJAYWC
1CsAn0n4BQ49LntN0PFloRLmIXS5Sgbc
=3OJj
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.