[LiSA-Devel] [Fwd: Fwd: question about compiling LiSA]

Claudiu Ghioc claudiughioc at gmail.com
Mon Oct 21 11:44:09 EEST 2013 

Hello,

Regarding the bugs reported by the user "chicany", I was thinking we
should update him with our conclusion. The "show run-config" bug is
solved but the rest of them could not be replicated on my virtual
machine. Neither on Andreea's.

What do you think?


On Fri, Oct 4, 2013 at 12:12 AM, Radu Rendec <radu.rendec at mindbit.ro> wrote:
> FYI...
>
> -------- Forwarded Message --------
> From: chicany <chicany at gmail.com>
> To: radu.rendec at mindbit.ro <radu.rendec at mindbit.ro>
> Subject: Fwd: [LiSA-Devel] question about compiling LiSA
> Date: Wed, 2 Oct 2013 23:45:11 -0400
>
> Hello, any update regarding fixing bugs in LiSA dev version? Thanks.
> -brezular
>
>
> ---------- Forwarded message ----------
> From: chicany <chicany at gmail.com>
> Date: 2013/9/29
> Subject: Re: [LiSA-Devel] question about compiling LiSA
> To: Claudiu Ghioc <claudiughioc at gmail.com>
>
>
> Hi Claudio,
>
> 1. LiSA compilation
>
> I didn't touch the variable. Below is the content of Makefile.variables.
> ifndef IMPL         #IMPL = lisa         IMPL = linux         #IMPL =
> openwrt endif
>
> I tried to change the content of the file as  following but they are errors
> during compilation. Please check the attachment.
>
> ifndef IMPL         IMPL = lisa         #IMPL = linux         #IMPL =
> openwrt endif
>
>
>
> 2. Ethernet interfaces
>
> The interface eth0 was up when I tried to configure it.
>
> box(config)#interface ethernet 0 Command rejected: interface eth0 does not
> exist box(config)#interface ethernet 0 box(config-if)#description test
>
>
>
> box#show running-config interface ethernet 0 Building configuration...
>
> Current configuration : 103 bytes ! interface Ethernet 0  description test
> switchport trunk allowed vlan 1-4094  switchport mode access end
>
> As you can see, interface description is saved to running-config. We can
> normally configure interface but first time is an interface configured. the
> warning message is displayed "Command rejected: interface eth0 does not
> exist"
>
> Cheers,
>
> -brezular
>
> 2013/9/27 Claudiu Ghioc <claudiughioc at gmail.com>
>
> Hello,
>
>
>
> Thank you for your feedback regarding the functionality of LiSA. The first 4
> problems will be dealt with as soon as possible. The 5th reported issue is
> not actually a problem because you should definitely have root privileges
> when configuring the hostname. The same for the other operations (bridge and
> interface configurations).
>
> Could you also tell us please if you changed the back-end implementation in
> "userspace/scripts/Makefile.variables"? The default one is using the two
> Linux kernel modules, bridge and 8021q, and this option can be changed
> through the "IMPL" variable in the above mentioned file.
>
> Regarding the third issue, I personally checked yesterday the same command.
> I was able to configure an Ethernet interface on my system. Could you
> confirm please that the interface was up when you tried to configure it?
>
>
>
> Have a nice day!
>
>
>
> On Thu, Sep 26, 2013 at 10:00 PM, chicany <chicany at gmail.com> wrote:
>
> Hello team,
>
> I have my Qemu image with installed Core Linux 5.0 (3.8.10) ready. I
> successfully compiled LiSA Devel version available on git (26.9. 2013).
>
> I'm not going to send LiSA extension to Core repository until it proves that
> basic configuration is working -  swiching, vlan, trunks etc.
>
>
>
> I used command sudo swcli for LiSA configuration and notice the following
> problems:
>
>
>
> 1. running-config
>
> all the vlans - from 2 to 4093 are presented in a running-config, each on
> separate line. I guess, VLANs should haven't be presented in running-config
> because no vlan had been created so far. And it is annoying e.g. if you want
> to check interface configuration in running-config you have to go through
> all the vlans. It is because interface configuration is displayed after vlan
> configuration.
>
>
>
> test#show run
>
> Building configuration...
>
>
>
> Current configuration : 48025 bytes
>
> !
>
> hostname test
>
> !
>
> !
>
> no ip igmp snooping
>
> !
>
> vlan 2
>
> !
>
> vlan 3
>
> !
>
> vlan 4
>
> .
>
> .<output truncated>
>
> .
>
> !vlan 4093
>
>
>
> interface Ethernet 0
>
>  description test
>
>  switchport trunk allowed vlan 10
>
>  switchport mode trunk
>
>
>
> 2. VLANs are not presented in show vlan command
>
> when I create VLAN, I should get in (config-vlan) prompt and configure vlan
> name. Instead of it I get back to the prompt (config)#
>
>
>
> box(config)#vlan 10
>
> box(config)#
>
>
>
> VLAN 10 is not presented in show vlan command.
>
>
>
> test#show vlan
>
> VLAN Name                             Status    Ports
>
> ---- -------------------------------- ---------
> -------------------------------
>
> test#
>
>
>
> 3. Ethernet interface configuration
>
>
>
> test(config)#interface ethernet 0
>
> Command rejected: interface eth0 does not exist
>
> test(config)#
>
> test(config)#
>
> test(config)#interface ethernet 0
>
> test(config-if)#
>
>
>
> First, it was complaining that ethernet 0 doesn't exist. But the second time
> I was able to get in to (config-if) prompt and normally configure switchport
> parameters such as trunk, allowed vlan etc.
>
>
>
> 4. VLAN interface configuration
>
>
>
> VLAN interface can't be configure. Please, see the output below.
>
>
>
> test(config)#interface vlan 20
>
> Command rejected: ioctl() failed (19 - No such device)
>
> test(config)#
>
>
>
> 5. running swcli without root privilegies
>
>
>
> I\m not sure if it is a desired option or not but when you start swcli as a
> normal user (no root) you can't configure hostname.
>
>
>
> test(config)#hostname switch
>
> Command rejected: Operation not permitted
>
> test(config)#
>
>
>
>
>
> So far I haven't tested if switching is working. First I must create a LiSA
> binary extension and then I can test LiSA against other devices inside GNS3.
> But first the mentioned problems should be fixed. I hope I compiled LiSA
> properly. The output of  make and make install command is attached. Thank
> you.
>
>
>
> -brezular
>
>
>
>
>
> 2013/9/25 Radu Rendec <radu.rendec at mindbit.ro>
>
> Hi,
>
> I've managed to get the devel branch compile properly, but there seems to be
> something wrong with the "bridge+8021q" backend - which is what we want to
> use in order to avoid patching the kernel. I've already posted the issue to
> the devel list, so the developer who wrote that module may have a chance to
> investigate what's going on.
>
> Anyway, I still want to port the kernel module to newer kernels. If I
> succeed, then perhaps we can use the "stable" version and the patched
> kernel, and then make an update when the "devel" version is fixed.
>
> Thanks,
>
> Radu
>
>
>
> On Tue, 2013-09-24 at 06:34 -0400, chicany wrote:
>
> Hello Radu,
> thank you for your answer. I really appreciate your effort to help me to get
> LiSA working on Linux Core. As for your question I'm thinking about
> compiling a devel version of LiSA against the standard kernel 3.8.10. The
> newest Core 5.0. based on this kernel  was released the last week so I guess
> they will use this kernel in several next Core versions.
> I'm not worried about the bugs in a devel version. I think using the devel
> version will be a great opportunity to catch some new bugs :)
>
> Is it possible to compile the current version of LiSA that is on git against
> the standard Core Linux kernel 3.8.10 (non- LiSA patched kernel)  or I have
> to wait for the LiSA update from your side?
>
>
> I'm really exciting to make LiSA binary package (extension). The last week I
> sent the newest Openvswitch 1.11.0 extension together with Quagga 0.22.4
> extension to Core repo. I made a Qemu / Vbox image that has installed those
> two extensions. It can be used for learning routing / switching on Linux. I
> will do the similar image with Quagga and LiSA. They both have CLI like
> Cisco so some people would find it useful.
>
>
> If I'm successful in my "mission" I will write detailed tutorial about LiSA
> installation on Core.
>
>
> Thank you very much.
>
>
> -brezular
>
>
> 2013/9/23 Radu Rendec <radu.rendec at mindbit.ro>
>
> Hi,
>
> I really like the idea of integrating LiSA into Linux Core. At this point
> I'm looking at all possible ways to make LiSA more widely known to users and
> I think integrating it into a linux distribution is a great opportunity. So
> I'll do my best to support you with this initiative.
>
> There's been a lot of fresh development in LiSA during the past few months
> and now we have 2 versions:
>
> the "stable" version, which is the version that I built rpm packages for and
> the version that you used for building the centos image and for integrating
> into GNS3
> the "devel" version, which is now only available directly from the git
> repository on github ( https://github.com/lisa-project/lisa-user )
>
> The "devel" version doesn't necessarily require a patched kernel. It can be
> compiled against the LiSA kernel module (and in this case it still requires
> a patched kernel), but it can also be compiled against the standard "bridge"
> and "8021q" kernel and in this case it works with a regular (unpatched)
> kernel.
>
> However, there are 2 issues with the "devel" version:
>
> it's not as tested as the "stable" version and it may have (more) bugs
> there's something broken in the build system, but I think I can fix this
> within the next 1 or 2 days
>
> The "stable" version only works with a patched kernel. At this point, the
> newest kernel version that we ported the module for is 2.6.32. Porting it to
> 3.x shouldn't be such a big issue - after all, moving from 2.6.x to 3.x was
> just a versioning change in linux and the code base is the same. But I won't
> be able to look into this before the weekend.
>
> I'll make the port for kernel 3.0.21 first, but in the mean time, please let
> me know if you plan to use Core 5.0 - because in this case I'll have to
> support kernel 3.8.10 as well.
>
> Kind regards,
>
> Radu
>
>
> On Mon, 2013-09-23 at 15:14 -0400, chicany wrote:
>
> Hello Radu,
>
>
> I would like to install LiSA on Linux Core
> http://distro.ibiblio.org/tinycorelinux/ and make an extension that is added
> to Core repo. Actual Core Linux 4.7.7 uses kernel 3.0.21, Core 5.0 uses the
> kernel 3.8.10.
> There are kernel and lisa rpms for centos and fedora on your page but I want
> to build a new kernel and lisa on existing tinycore kernel
> http://distro.ibiblio.org/tinycorelinux/5.x/x86/release/src/kernel/
>
>
> You have done the same in the past when you built LiSa on Tinycore linux
> installed on Commell's LE-564 embedded SBC.
>
>
> I suppose I have to patch kernel and then enable Linux Multilayer switch in
> kernel or as module. The I have to compile my own kernel. I can see the
> patches in rpm directory for particular Centos or fedora kernel. But they
> are for kernel 2.6.x only, mine is 3.x
> I don't want to build rpm packages. They are not used by Core / Tinycore
> Linux. If it is possible I just want to rebuild kernel, install LiSA
> userspace.
>
>
> Can you give me a hand with it? I just need to point in right direction.
>
>
>
> Thank you.
>
>
> -brezular
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> LiSA-Devel mailing list
> LiSA-Devel at lisa.mindbit.ro
> http://lisa.mindbit.ro/mailman/listinfo/lisa-devel
>
>
>
>
>
> --
>
> Claudiu Ghioc
>
> Software Developer
> Email: claudiu.ghioc at gmail.com
> +(40) 745 783 796
>
>
>
>
>
>
>
> _______________________________________________
> LiSA-Devel mailing list
> LiSA-Devel at lisa.mindbit.ro
> http://lisa.mindbit.ro/mailman/listinfo/lisa-devel
>



-- 
Claudiu Ghioc
Software Developer
Email: claudiu.ghioc at gmail.com
+(40) 745 783 796

More information about the LiSA-Devel mailing list