ipcop-devel Mailing List for IPCop Firewall

I noticed that there is a newer version of the out of kernel solos-pci 
drivers on SF as of last July which is now 1.0.4. The in kernel version 
looks to be still at version 0.07. Of course you need the out of kernel 
tarball to get the utilities anyway. 

Olaf, did you ever get to test one of the Geos units from Traverse? To 
anyone else reading, the Traverse Geos platform has the solos-pci built into 
the motherboard and can be had in single or dual adsl config but not the 
quad port like the pci mammoth I have to play with. Traverse has been better 
about updated firmware lately for their cards they spun off to Rocksolid.
--
Dave Studeman
http://www.raqcop.com 

David W Studeman wrote:

>   IPCop contains both the deprecated prism54 and the newer p54 drivers.
> The newer driver supports both SoftMac and the older FullMac hardware
> whereas prism54 only supports the FullMac hardware. When this hardware
> is used, both versions end up being loaded. I can't think of any reason
> other than firmware hell to keep the prism54 in the IPCop kernel.

All that is need is changing this: CONFIG_PRISM54=m
To this: # CONFIG_PRISM54 is not set
On line 1761 of the existing kernel.config.i486. There is no need to do a 
make menuconfig in this case in the kernel tree.

It would appear that the Sparc and Power PC configs also have the conflict. 
The Alpha config does not appear to have the same options.
-- 
Dave Studeman
http://www.raqcop.com 

  IPCop contains both the deprecated prism54 and the newer p54 drivers. 
The newer driver supports both SoftMac and the older FullMac hardware 
whereas prism54 only supports the FullMac hardware. When this hardware 
is used, both versions end up being loaded. I can't think of any reason 
other than firmware hell to keep the prism54 in the IPCop kernel.
-- 
Dave Studeman
http://www.raqcop.com

On Sat, 2013-12-14 at 15:07 +0100, Olaf wrote:

> On 2013-12-11 08:45, Ersan YILDIRIM wrote:
> 
> > During the installation of IPCop2.1.1-rc1 Turkish characters instead of
> > "?" mark appears.
> >
> > It Be Fixed?
> 
> probably not, same problem in 2.0.3 and very likely in older versions.
> 
> Olaf


I like the subject line.  "Corrupt Turkish characters" sounds like the
brief back page blurb for a pulp fiction novel.

David

>>> I looked at the firmware in a 2.1.1rc1 installation and a 2.0.6
>>> installation and noticed that some firmware in the 3.4 kernel is
>>> different than that of 2.6.32. Any reason not to include it in the
>>> update?

thanks Dave, fixed in #7186

Olaf

On 2013-12-11 08:45, Ersan YILDIRIM wrote:

> During the installation of IPCop2.1.1-rc1 Turkish characters instead of
> "?" mark appears.
>
> It Be Fixed?

probably not, same problem in 2.0.3 and very likely in older versions.

Olaf

On 12/11/2013 08:13 PM, Eric Shubert wrote:
> Will there be a 2.1.1 iso? I'm wondering how/where the virtio devices
> patch (submitted to this list 4/26/2013) fits in to the scheme of things.
>
> Thanks.
>

Let me follow up. I see there's now a 2.1.1 iso, and it performs much 
better cpu-wise as a VM. I'm disappointed to see though that the virtio 
devices patch submitted last April does not appear to be in the release. 
Gilles indicated back then that he would integrate it.

Here is the patch again, for your convenience. Is there any possibility 
of getting this included with this release? It would be very appropriate.

Thanks for all your great work, and your consideration.


-- 
-Eric 'shubes'

Will there be a 2.1.1 iso? I'm wondering how/where the virtio devices 
patch (submitted to this list 4/26/2013) fits in to the scheme of things.

Thanks.

-- 
-Eric 'shubes'

On 12/09/2013 12:31 PM, Olaf wrote:
> For those feeling courageous and lucky, 2.1.1-rc1 installation and
> update files are available on SourceForge.
> The 2.1.0-rc1 and 2.1.1-rc1 update requires a 2.0.6 installation and
> manual update via GUI!
>
>
> ***
> 2.1.1-rc1 is for testing purposes and cannot be updated to 2.1.1.
> ***
>
> When testing the installation and or update, make sure to have uptodate
> and working backups to be able to return to 2.0.6.
> The USB installation files may not work and will be fixed by the time
> 2.1.1 is released.
>
>
> Download location: http://sourceforge.net/projects/ipcop/files/IPCop
> Test Versions/
>
> Updates
> 5e4e52584240ce9473b4b2aade7116a8  ipcop-2.1.0-rc1-update.i486.tgz.gpg
> a9db2a3bf897495bb04ad4e05da03cbd  ipcop-2.1.1-rc1-update.i486.tgz.gpg
>
> Installation
> e85d2d427be119ddbb06beb51c04853b  ipcop-2.1.1-rc1-install-cd.i486.iso
> e01f15d336ba97530650fe398be7e341  ipcop-2.1.1-rc1-install-netboot.i486.tgz
> c9928e8af81eecf2db4999f8957eb6ae
> ipcop-2.1.1-rc1-install-usb-fdd.i486.img.gz
> 4eaff3178af96fe982c0592f07e3b0d6
> ipcop-2.1.1-rc1-install-usb-hdd.i486.img.gz
> 239fa77998a056d33ba4ee863cc37373
> ipcop-2.1.1-rc1-install-usb-zip.i486.img.gz
>
>
> Olaf
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>

Achim Weber wrote:

> Hi Dave
> 
>> I looked at the firmware in a 2.1.1rc1 installation and a 2.0.6
>> installation and noticed that some firmware in the 3.4 kernel is
>> different than that of 2.6.32. Any reason not to include it in the
>> update?
> 
> Probably they are just missing in the update rootfiles. Which files are
> different, can you send the names/path?
> 
> Achim

Yes I can.

IPCop 2.0.6:
/lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-mips-09-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-rv2p-06-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-rv2p-09-5.0.0.j3.fw
/lib/firmware/bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw
/lib/firmware/cxgb3/t3fw-7.4.0.bin
/lib/firmware/bnx2x-e1-5.0.21.0.fw
/lib/firmware/bnx2x-e1h-5.0.21.0.fw

IPCop 2.1.1:
/lib/firmware/bnx2/bnx2-mips-06-6.2.1.fw
/lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw
/lib/firmware/bnx2/bnx2-rv2p-06-6.0.15.fw
/lib/firmware/bnx2/bnx2-rv2p-09-6.0.17.fw
/lib/firmware/bnx2/bnx2-rv2p-09ax-6.0.17.fw
/lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
/lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
/lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
/lib/firmware/cis/PE520.cis
-- 
Dave Studeman
http://www.raqcop.com 

Hi Dave

> I looked at the firmware in a 2.1.1rc1 installation and a 2.0.6 installation 
> and noticed that some firmware in the 3.4 kernel is different than that of 
> 2.6.32. Any reason not to include it in the update?

Probably they are just missing in the update rootfiles. Which files are
different, can you send the names/path?

Achim

I looked at the firmware in a 2.1.1rc1 installation and a 2.0.6 installation 
and noticed that some firmware in the 3.4 kernel is different than that of 
2.6.32. Any reason not to include it in the update?
-- 
Dave Studeman
http://www.raqcop.com 

For those feeling courageous and lucky, 2.1.1-rc1 installation and 
update files are available on SourceForge.
The 2.1.0-rc1 and 2.1.1-rc1 update requires a 2.0.6 installation and 
manual update via GUI!


***
2.1.1-rc1 is for testing purposes and cannot be updated to 2.1.1.
***

When testing the installation and or update, make sure to have uptodate 
and working backups to be able to return to 2.0.6.
The USB installation files may not work and will be fixed by the time 
2.1.1 is released.


Download location: http://sourceforge.net/projects/ipcop/files/IPCop 
Test Versions/

Updates
5e4e52584240ce9473b4b2aade7116a8  ipcop-2.1.0-rc1-update.i486.tgz.gpg
a9db2a3bf897495bb04ad4e05da03cbd  ipcop-2.1.1-rc1-update.i486.tgz.gpg

Installation
e85d2d427be119ddbb06beb51c04853b  ipcop-2.1.1-rc1-install-cd.i486.iso
e01f15d336ba97530650fe398be7e341  ipcop-2.1.1-rc1-install-netboot.i486.tgz
c9928e8af81eecf2db4999f8957eb6ae 
ipcop-2.1.1-rc1-install-usb-fdd.i486.img.gz
4eaff3178af96fe982c0592f07e3b0d6 
ipcop-2.1.1-rc1-install-usb-hdd.i486.img.gz
239fa77998a056d33ba4ee863cc37373 
ipcop-2.1.1-rc1-install-usb-zip.i486.img.gz


Olaf