<div dir="ltr">Hello team,<div><br></div><div>We seem to have some problems reported by chicany (see the email below). I believe he didn't choose other back-end implementation in Makefile.variables so the back-end was the default one, "linux" (bridge + 8021q).</div>
<div><br></div><div>1. I noticed the first problem yesterday with "show run-config" displaying all the possible VLANs. This can be fixed quickly. I will start looking into it.</div><div>2. This must be a bug in CLI.</div>
<div>3. Configuring an ethernet interface works for me. Any reasons why it doesn't work for him? Maybe the interface is down?</div><div>4. This must be a bug related to "linux" implementation. We should investigate the other 4 issues.</div>
<div>5. I don't know exactly whether hostname configuration should work for unprivileged users. Any thoughts?</div><div><br></div><div>Have a nice day!</div><div><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">chicany</b> <span dir="ltr"><<a href="mailto:chicany@gmail.com">chicany@gmail.com</a>></span><br>Date: Thu, Sep 26, 2013 at 10:00 PM<br>Subject: Re: [LiSA-Devel] question about compiling LiSA<br>
To: Radu Rendec <<a href="mailto:radu.rendec@mindbit.ro">radu.rendec@mindbit.ro</a>>, <a href="mailto:lisa-devel@lisa.mindbit.ro">lisa-devel@lisa.mindbit.ro</a><br><br><br><div dir="ltr">Hello team,<div>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). </div>
<div>I'm not going to send LiSA extension to Core repository until it proves that basic configuration is working - swiching, vlan, trunks etc.</div>
<div><br></div><div>I used command <b>sudo</b> <b>swcli </b>for LiSA configuration and notice the following problems:</div><div><br></div><div><b><u>1. running-config</u></b></div><div>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.</div>
<div><br></div><div><div>test#<font color="#38761d">s<b>how run</b></font></div><div>Building configuration...</div><div><br></div><div>Current configuration : 48025 bytes</div><div>!</div><div>hostname test</div><div>!</div>
<div>!</div><div>no ip igmp snooping</div><div>!</div><div>vlan 2</div><div>!</div><div>vlan 3</div><div>!</div><div>vlan 4</div></div><div>.</div><div><font color="#cc0000">.<output truncated></font></div><div>.</div>
<div>!vlan 4093</div><div><br></div><div><div>interface Ethernet 0</div><div> description test</div><div> switchport trunk allowed vlan 10</div><div> switchport mode trunk</div></div><div><br></div><div><b><u>2. VLANs are not presented in show vlan command</u></b></div>
<div>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)#</div><div><br></div><div><div>box(config)#<font color="#38761d"><b>vlan 10</b></font></div>
<div>box(config)#</div></div><div><br></div><div>VLAN 10 is not presented in show vlan command.</div><div><br></div><div><div>test#<font color="#38761d"><b>show vlan </b></font></div><div>VLAN Name Status Ports</div>
<div>---- -------------------------------- --------- -------------------------------</div><div>test#</div></div><div><br></div><div><b><u>3. Ethernet interface configuration</u></b></div><div><br></div><div><div>test(config)#<font color="#38761d"><b>interface ethernet 0</b></font></div>
<div>Command rejected: interface eth0 does not exist</div><div>test(config)#</div><div>test(config)#</div><div>test(config)#<font color="#38761d"><b>interface ethernet 0</b></font></div></div><div>test(config-if)#<br></div>
<div><br></div><div>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.</div>
<div><br></div><div><b><u>4. VLAN interface configuration</u></b><br></div><div><br></div><div>VLAN interface can't be configure. Please, see the output below.</div><div><br></div><div><div>test(config)#<b><font color="#274e13">interface vlan 20</font></b></div>
<div>Command rejected: ioctl() failed (19 - No such device)</div><div>test(config)#</div></div><div><br></div><div><b><u>5. running swcli without root privilegies</u></b></div><div><br></div><div><div>I\m not sure if it is a desired option or not but when you start <b><font color="#38761d">swcli</font></b> as a normal user (no root) you can't configure hostname.</div>
<div><br></div><div>test(config)#<b><font color="#38761d">hostname switch</font></b></div><div>Command rejected: Operation not permitted</div><div>test(config)#</div></div><div><br></div><div><br></div><div>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 <b><font color="#38761d">make</font></b> and <b><font color="#38761d">make install </font></b>command is attached. Thank you.</div>
<div><br></div><div>-brezular </div><div><br></div></div><div class=""><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/25 Radu Rendec <span dir="ltr"><<a href="mailto:radu.rendec@mindbit.ro" target="_blank">radu.rendec@mindbit.ro</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><u></u>
<div>
Hi,<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
<br>
Radu<div><div><br>
<br>
On Tue, 2013-09-24 at 06:34 -0400, chicany wrote:
<blockquote type="CITE">
Hello Radu,
</blockquote>
<blockquote type="CITE">
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.
</blockquote>
<blockquote type="CITE">
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 :)
</blockquote>
<blockquote type="CITE">
</blockquote>
<blockquote type="CITE">
Is it possible to compile the <u>current</u> 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?
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
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.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
If I'm successful in my "mission" I will write detailed tutorial about LiSA installation on Core.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Thank you very much.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
-brezular
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
2013/9/23 Radu Rendec <<a href="mailto:radu.rendec@mindbit.ro" target="_blank">radu.rendec@mindbit.ro</a>>
</blockquote>
<blockquote type="CITE">
<blockquote>
Hi,<br>
<br>
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.<br>
<br>
There's been a lot of fresh development in LiSA during the past few months and now we have 2 versions:
<ul>
<li>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
</li><li>the "devel" version, which is now only available directly from the git repository on github ( <a href="https://github.com/lisa-project/lisa-user" target="_blank">https://github.com/lisa-project/lisa-user</a> )
</li></ul>
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.<br>
<br>
However, there are 2 issues with the "devel" version:
<ul>
<li>it's not as tested as the "stable" version and it may have (more) bugs
</li><li>there's something broken in the build system, but I think I can fix this within the next 1 or 2 days
</li></ul>
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.<br>
<br>
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.<br>
<br>
Kind regards,<br>
<br>
Radu
</blockquote>
</blockquote>
<blockquote type="CITE">
<blockquote>
<br>
<br>
On Mon, 2013-09-23 at 15:14 -0400, chicany wrote: <br>
<blockquote type="CITE">
Hello Radu,<br>
<br>
<br>
I would like to install LiSA on Linux Core <a href="http://distro.ibiblio.org/tinycorelinux/" target="_blank">http://distro.ibiblio.org/tinycorelinux/</a> 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. <br>
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 <a href="http://distro.ibiblio.org/tinycorelinux/5.x/x86/release/src/kernel/" target="_blank">http://distro.ibiblio.org/tinycorelinux/5.x/x86/release/src/kernel/</a><br>
<br>
<br>
You have done the same in the past when you built LiSa on Tinycore linux installed on Commell's LE-564 embedded SBC.<br>
<br>
<br>
<font color="#000000">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</font><br>
<font color="#000000">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.</font><br>
<font color="#000000"> </font><br>
<br>
Can you give me a hand with it? I just need to point in right direction.<br>
<br>
<br>
<br>
Thank you.<br>
<br>
<br>
-brezular<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
LiSA-Devel mailing list<br>
<a href="mailto:LiSA-Devel@lisa.mindbit.ro">LiSA-Devel@lisa.mindbit.ro</a><br>
<a href="http://lisa.mindbit.ro/mailman/listinfo/lisa-devel" target="_blank">http://lisa.mindbit.ro/mailman/listinfo/lisa-devel</a><br>
<br></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Claudiu Ghioc<div>Software Developer<br>Email: <a href="mailto:claudiu.ghioc@gmail.com" target="_blank">claudiu.ghioc@gmail.com</a><br>+(40) 745 783 796</div>
</div>
</div></div>