<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/wanem/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/wanem/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/wanem/bugs/</id><updated>2012-05-30T23:00:32Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Kernel panic</title><link href="https://sourceforge.net/p/wanem/bugs/21/" rel="alternate"/><published>2012-05-30T23:00:32Z</published><updated>2012-05-30T23:00:32Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net26b79ee671ec2fdd23d21ef5da0973513d7eb376</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I seem to keep getting the kernel panic shown in the attached screenshot.  I have WANem set up between two servers.  On the WANem system, I created a bridge between eth2 and eth3, which are the interfaces connected to my two servers, as described in this link:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://reloadin10.com/2008/08/22/wanem-bridging-interfaces/" rel="nofollow"&gt;http://reloadin10.com/2008/08/22/wanem-bridging-interfaces/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This seems to work in terms of being able to ping one server from the other.  But, with any significant amount of traffic, I see this kernel panic on the WANem system.&lt;/p&gt;
&lt;p&gt;This is with WANem 2.3&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>No Multicast Support in Kernel</title><link href="https://sourceforge.net/p/wanem/bugs/20/" rel="alternate"/><published>2010-01-19T10:24:56Z</published><updated>2010-01-19T10:24:56Z</updated><author><name>King of the ring</name><uri>https://sourceforge.net/u/kingofthering/</uri></author><id>https://sourceforge.netc569f30ecfa0588c18e04f2808d1b9205cc8bb49</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Nambiar,&lt;br /&gt;
I tried to set up multicast routing on wanem! Most kernel settings seem to be available! Unfortunately the setting&lt;/p&gt;
&lt;p&gt;"# CONFIG_IP_MROUTE is not set" in the kernel config (/boot/config-2.6.24.4)&lt;/p&gt;
&lt;p&gt;which is required to run a multicast router like pimd:&lt;/p&gt;
&lt;p&gt;Get:1 &lt;a href="http://ftp.jp.debian.org" rel="nofollow"&gt;http://ftp.jp.debian.org&lt;/a&gt; testing/main pimd 2.1.0-alpha29.17-9 [80.6kB]&lt;br /&gt;
Fetched 80.6kB in 4s (19.7kB/s)&lt;br /&gt;
Selecting previously deselected package pimd.&lt;br /&gt;
(Reading database ... 53014 files and directories currently installed.)&lt;br /&gt;
Unpacking pimd (from .../pimd_2.1.0-alpha29.17-9_i386.deb) ...&lt;br /&gt;
Setting up pimd (2.1.0-alpha29.17-9) ...&lt;br /&gt;
Starting pimd: pimd: 14:59:33.589 cannot enable multicast routing in kernel: Protocol not available&lt;br /&gt;
invoke-rc.d: initscript pimd, action "start" failed.&lt;br /&gt;
dpkg: error processing pimd (--configure):&lt;br /&gt;
subprocess post-installation script returned error exit status 255&lt;br /&gt;
Errors were encountered while processing:&lt;br /&gt;
pimd&lt;/p&gt;
&lt;p&gt;Are there any special things to mention when rebuilding the kernel? &lt;/p&gt;
&lt;p&gt;Thx,&lt;br /&gt;
Axel&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Number of NICs</title><link href="https://sourceforge.net/p/wanem/bugs/19/" rel="alternate"/><published>2010-01-12T17:21:30Z</published><updated>2010-01-12T17:21:30Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netbb81d2286b9b7f80f4225a6a276df96dcd8345e0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When using more 5 NICs, the interface for configuring the IP addresses errors with segmentation fault. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>network configuration disappear</title><link href="https://sourceforge.net/p/wanem/bugs/18/" rel="alternate"/><published>2010-01-11T20:55:35Z</published><updated>2010-01-11T20:55:35Z</updated><author><name>Alex </name><uri>https://sourceforge.net/u/aglik/</uri></author><id>https://sourceforge.net779ac73c00004f8a44bc11fdaefb155464dd8b20</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sometimes the network is re-configured to 192.168.0.x address, and an error is printed at the console several times:&lt;br /&gt;
"HTB: quantum of class 100001 is big. Consider r2q change."&lt;br /&gt;
The setup includes a machine booted from WANem 2.2 ISO, bandwidth limitation to 256 Mbps or so. Single NIC is configured.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>network configuration disappear</title><link href="https://sourceforge.net/p/wanem/bugs/17/" rel="alternate"/><published>2010-01-11T19:33:35Z</published><updated>2010-01-11T19:33:35Z</updated><author><name>Alex </name><uri>https://sourceforge.net/u/aglik/</uri></author><id>https://sourceforge.net7065da050464d9695703b22fa4d7efdc4d9d11be</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sometimes the network is re-configured to 192.168.0.x address, and an error is printed at the console several times:&lt;br /&gt;
"HTB: quantum of class 100001 is big. Consider r2q change."&lt;br /&gt;
The setup includes a machine booted from WANem 2.2 ISO, bandwidth limitation to 256 Mbps or so. Single NIC is configured.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Cannot add more than 9 rulesets in the advanced mode</title><link href="https://sourceforge.net/p/wanem/bugs/16/" rel="alternate"/><published>2009-11-04T03:00:13Z</published><updated>2009-11-04T03:00:13Z</updated><author><name>M K Nambiar</name><uri>https://sourceforge.net/u/mknambiar/</uri></author><id>https://sourceforge.net3b1f4a98358636519a09b9bb5d96a2c4af1e1ff8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Adding more than 9 rulesets does not work in WANem advanced mode&lt;/p&gt;
&lt;p&gt;More details in the following link - &lt;a href="https://sourceforge.net/projects/wanem/forums/forum/725629/topic/3445060"&gt;https://sourceforge.net/projects/wanem/forums/forum/725629/topic/3445060&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>nat show command fails</title><link href="https://sourceforge.net/p/wanem/bugs/15/" rel="alternate"/><published>2009-06-22T11:28:55Z</published><updated>2009-06-22T11:28:55Z</updated><author><name>Sjaak</name><uri>https://sourceforge.net/u/sjaakvs/</uri></author><id>https://sourceforge.netfa628627e8a3a6b237aa63818b645e87cf055426</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'm using a physical computer with 2 ethernet ports and static network configuration.&lt;/p&gt;
&lt;p&gt;After adding both ethernet ports using ' nat add' , I get an error when doing ' nat show' &lt;br /&gt;
The nat show fails saying:&lt;br /&gt;
root/wanem.sh line 28: [: eth0: unarry operator expected&lt;br /&gt;
No NAT enabled interface in WANem&lt;/p&gt;
&lt;p&gt;After deleting one using 'nat del' the ' nat show'  reports correct again.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>nat command not in perc user</title><link href="https://sourceforge.net/p/wanem/bugs/14/" rel="alternate"/><published>2009-06-15T10:57:45Z</published><updated>2009-06-15T10:57:45Z</updated><author><name>Sjaak</name><uri>https://sourceforge.net/u/sjaakvs/</uri></author><id>https://sourceforge.net5ec238226c0f7a33ded46644693c8a08b0cae275</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The wanem command 'nat' is very useful for easy setup.&lt;br /&gt;
However this command is not available when login in via SSH as user perc.&lt;/p&gt;
&lt;p&gt;I use static IP adres configuration on 2 ethernet cards. &lt;br /&gt;
Otherwise boot/setup is giving me problems. This bug seems still to be open.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>.vmx file is missing catalog file</title><link href="https://sourceforge.net/p/wanem/bugs/13/" rel="alternate"/><published>2009-03-09T13:39:05Z</published><updated>2009-03-09T13:39:05Z</updated><author><name>Joshua Klein</name><uri>https://sourceforge.net/u/jk74/</uri></author><id>https://sourceforge.netc186439705ef6c0a087b37eca36780ca3e57b925</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When I try to use VMware converter to bring the VM into my ESX server, the process fails immediately after I specify the .VMX file to work from with an error stating that the .vmx file has a missing catalog file.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Wrong version info in wanem console</title><link href="https://sourceforge.net/p/wanem/bugs/12/" rel="alternate"/><published>2009-03-02T10:19:32Z</published><updated>2009-03-02T10:19:32Z</updated><author><name>Sjaak</name><uri>https://sourceforge.net/u/sjaakvs/</uri></author><id>https://sourceforge.net6ec3e685290eaf5d22de4a2807eec333bef35061</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Can't find the correct wanem version in the console.&lt;br /&gt;
after starting wanem 2.0 shell the reports v1.2&lt;/p&gt;
&lt;p&gt;So I can't find out what wanem version the sysadm started on the system.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>