ipcop-devel Mailing List for IPCop Firewall

Bugs item #1764828, was opened at 2007-07-31 18:54
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1764828&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Greg Godkin (grgodkin)
Assigned to: Nobody/Anonymous (nobody)
Summary: 1.4.16 System logs are not generated

Initial Comment:
IPCop on 1Gb flash built from 1.4.16 iso. System logs do not get generated after the scheduled reboot. Group owners on log files are different then on older IPCop versions.
root@ipcop:/var/log # ll
total 122
-rw-r--r-- 1 root     root        0 2007-07-28 18:03 boot.log
drwxr-xr-x 2 squid    squid    1024 2007-07-28 18:17 cache
-rw-r--r-- 1 root     root     6139 2007-07-28 23:17 dmesg
drwxr-xr-x 2 nobody   nobody   1024 2007-07-29 07:21 dyndns
drwxr-xr-x 2 root     root     1024 2007-07-28 23:17 httpd
drwxr-xr-x 2 root     root     1024 2007-07-28 18:05 ip-acct
-rw-r----- 1 root     root      292 2007-07-31 11:43 lastlog
drwxr-xr-x 2 logwatch nobody   1024 2007-07-31 11:40 logwatch
-rw-r--r-- 1 root     root        0 2007-07-29 11:20 messages
-rw-r--r-- 1 root     root   103057 2007-07-29 11:20 messages.1.gz
-rw-rw---- 1 root     nobody    359 2007-07-31 13:49 ovpnserver.log
drwxr-xr-x 2 root     root     1024 2007-07-28 18:05 rrd
drwxr-xr-x 2 snort    snort    1024 2007-07-29 00:20 snort
drwxr-xr-x 2 squid    squid    1024 2007-07-28 17:12 squid
drwxr-xr-x 2 root     root     1024 2007-07-30 18:29 time
-rw-rw-r-- 1 root     utmp     1536 2007-07-31 11:43 wtmp
-rw-r--r-- 1 root     root      814 2007-07-29 00:20 wtmp.1.gz


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1764828&group_id=40604

Bugs item #1762763, was opened at 2007-07-28 17:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1762763&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Kernel
Group: 1.4.16
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Getz Dan (getzdan)
Assigned to: Nobody/Anonymous (nobody)
Summary: new e100 not working

Initial Comment:
i installed 1.4.16 update.
instead of recognizing the eth0,1,2 i have. the new e100 recognized only eth0. furthermore i had weird:
   5-order allocation failed 
and
   gfp=0x20/0
messages on dmesg.

i clawed my way back to a working system by reverting to an older kernel and then copying the older e100 for the newer kernel.

this was a bad experience.

but... you guys rock, and have a solid-rock feeling system otherwise....

thanks
dan


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1762763&group_id=40604

Hi

Are there any other ownership, or permissiom oddities, in /etc/snort
or /var/log/snort?

Eric

Hi Franck

This bug report was two years ago, is this not obsolete?

Bye
Michael

> -----Original Message-----
> From: ipc...@li... [mailto:ipcop-devel-
> bo...@li...] On Behalf Of Franck Bourdonnec
> Sent: Monday, July 23, 2007 7:23 PM
> To: ipc...@li...
> Subject: [IPCop-devel] translate
> 
> Hello,
> Can one of our Deutsch member translate this
> paragraph and put it in this 'bug report' so that
> we know...what to do with it!
> https://sourceforge.net/tracker/index.php?func=detail&aid=1162364&group
> _id=40604&atid=428516
> 
> Franck
> 
> Re: Eicon Diva Pro 2.0 funktioniert nicht
> Subject: 	Re: Eicon Diva Pro 2.0 funktioniert nicht
> 
> On Sun, Jun 12, 2005 at 05:19:49PM +0200, Bernd Volkmann wrote:
> > dagegen spricht, dass YAST die Karte als konfiguriert anzeigt.
> >
> 
> YaST zeigt alle Karten als konfigured an,sobald einmal ein
> Konfigurationsprogramm fuer die erkannt Kartenklasse gestartet
> wurde, unabhaengig ob die Karte unterstuetzt ist oder nicht.
> 
> Was sagt denn lspci -v  und lspci -vn ?
> Was steht in /etc/sysconfig/isdn/cfg-contr0 ?
> 
> Die DIVA Pro ist in jedem Fall keine Karte fuer die es Treiber
> gibt, da der DSP auf der Karte kompliziert anzusteuern ist und man mir
> vor
> Jahren davon abgeraten hat es zu versuchen, da der Aufwand zu hoch ist
> und
> die Karten nicht sehr verbreitet sind.
> Eicon soll wohl intern Treiber fuer Linux portiert haben, diese sind
> aber
> leider nicht so einfach erhaeltlich.
> 
> read from:
> http://osdir.com/ml/linux.suse.isdn/2005-06/msg00017.html
> 
> 
> -----------------------------------------------------------------------
> --
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> IPCop-devel mailing list
> IPC...@li...
> https://lists.sourceforge.net/lists/listinfo/ipcop-devel
> 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.10.14/912 - Release Date:
> 22.07.2007 19:02
> 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.14/912 - Release Date: 22.07.2007
19:02
 

Hello,
Can one of our Deutsch member translate this
paragraph and put it in this 'bug report' so that
we know...what to do with it!
https://sourceforge.net/tracker/index.php?func=detail&aid=1162364&group_id=40604&atid=428516

Franck

Re: Eicon Diva Pro 2.0 funktioniert nicht
Subject: 	Re: Eicon Diva Pro 2.0 funktioniert nicht

On Sun, Jun 12, 2005 at 05:19:49PM +0200, Bernd Volkmann wrote:
> dagegen spricht, dass YAST die Karte als konfiguriert anzeigt.
> 

YaST zeigt alle Karten als konfigured an,sobald einmal ein
Konfigurationsprogramm fuer die erkannt Kartenklasse gestartet
wurde, unabhaengig ob die Karte unterstuetzt ist oder nicht.

Was sagt denn lspci -v  und lspci -vn ?
Was steht in /etc/sysconfig/isdn/cfg-contr0 ?

Die DIVA Pro ist in jedem Fall keine Karte fuer die es Treiber
gibt, da der DSP auf der Karte kompliziert anzusteuern ist und man mir vor
Jahren davon abgeraten hat es zu versuchen, da der Aufwand zu hoch ist und
die Karten nicht sehr verbreitet sind.
Eicon soll wohl intern Treiber fuer Linux portiert haben, diese sind aber
leider nicht so einfach erhaeltlich.

read from:
http://osdir.com/ml/linux.suse.isdn/2005-06/msg00017.html

Bugs item #1758575, was opened at 2007-07-23 00:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1758575&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: 1.4.16
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: JunkYardDog (conradwy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Re-org on IP accounting data.db file

Initial Comment:
I have noticed that there is no re-org maintenance on the ip-accounting file: /var/log/ip-acct/data.db

This caused me some hassles the last few days so I wrote a simple maintenance routine in python.  (I am no python developer so the code is really simple).  I suggest you add a revised version of this possibly with some sanity checks etc. to your next release.  Maybe as a web page click-able item or scheduled like I did.  Your choice.

Here is the code:

import gdbm
db = gdbm.open("/var/log/ip-acct/data.db","w")
db.reorganize()
db.close()

I have scheduled this in cron to run once a week

Crontab entry
1 4 * * 0       /usr/bin/python /usr/local/sbin/reorg-ipacc-db > /dev/null 2>&1
 

You might want to argue that this is a feature request but lack of maintenance can be an operational show stopper so I logged it as a bug.

My system specs:
Pentium 60 with 24MB RAM 630MB Hard Drive 

Addons installed:
Traffic Control and Report --> I made some modifications to this
BOT (Block Outgoing Traffic)
L7 Filter --> Uninstalled but it seems to leave some traces on the system




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1758575&group_id=40604

On Thursday 19 July 2007, Phil Barnett wrote:
> After installing a fresh v1.4.16 on a test machine I'm using for a demo
> tonight, I attempted to set up the sourcefire rules for Snort.
>
> When viewing the latest ruleset installation log, I got the message
> that /etc/snort/rules was not writable.
>
> I changed the owner to snort with the command:
>
> chmod -R snort.snort /etc/snort/rules

As has been brought to my attention many times, chmod is NOT chown.

The proper command is:

chown -R snort.snort /etc/snort/rules

My bad.

-- 
Phil Barnett
AI4OF
SKCC #600

Hi , I use Ipcop on multiple server and it works fine !!

But I have a new problem, i have a new provider . So I don't konw if 
possible to use Ipcop for load balancing over 2 lines.

I search and I find this :

#!/bin/bash
#IPs of the def gateways
IP1=192.168.1.1
IP2=192.168.2.1
REDLOCAL=10.1.1.0/24
IPLOCAL=10.1.1.1
# NICs
IF1=eth0
IF2=eth1
ip rule add from $IP1 lookup T1
ip route add $REDLOCAL via $IPLOCAL table T1
ip route add 0/0 via $IP1 table T1
ip route add from $IP2 lookup T2
ip route add $REDLOCAL via $IPLOCAL table T2
ip route add 0/0 via $IP1 table T1
ip route default equalize nexthop via $IP1 dev $IF1 nexthop via $IP2 dev 
$IF2


(source : http://www.go2linux.org/node/26 )

 and another solution : 
http://lartc.org/howto/lartc.rpdb.multiple-links.html

I think the first solution is the most but I would like your opinion 
about this.

thanks leso

<html><div style='background-color:'><P>Hi, i've downloaded &amp; installed IPCOP v1.4.16 from scratch using ISO CD.<BR>Once configured and connected, went to update Snort rules via WebAdmin, i've setted the oink code for registered users, then save, then download new ruleset. Right after that, in the log i get this error:</P><PRE>Loading /var/ipcop/snort/oinkmaster.conf
/usr/local/bin/oinkmaster.pl: Error: the output directory "/etc/snort/rules" isn't writable by you.</PRE>
<P>I've do a chmod 777 to etc/snort/rules but it keeps don't working.&nbsp;Any ideas???</P>
<P>Thanks in advance...</P>
<P>PD: Sorry for my poor english...</P>
<P>Infinite Darkness (Ariel).</P></div><br clear=all><hr>Sé uno de los primeros a testar el Windows Live Messenger beta. <a href="http://g.msn.com/8HMAESAR/2731??PS=47575" target="_top">¡Haz click aquí! </a> </html>

After installing a fresh v1.4.16 on a test machine I'm using for a demo 
tonight, I attempted to set up the sourcefire rules for Snort.

When viewing the latest ruleset installation log, I got the message 
that /etc/snort/rules was not writable.

I changed the owner to snort with the command:

chmod -R snort.snort /etc/snort/rules

After that, the sourcefire rules applied perfectly.

-- 
Phil Barnett
AI4OF
SKCC #600

Feature Requests item #1756893, was opened at 2007-07-20 00:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1756893&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Next release
Status: Open
Priority: 5
Private: No
Submitted By: durango8 (durango8113)
Assigned to: Nobody/Anonymous (nobody)
Summary: sshd & httpd listening interface selection

Initial Comment:
1.4.15 
By default sshd & httpd listen on all interfaces.

For security reasons the install script could apply the servers to listen only on the green interface after green ip address is given.

The sshd gui interface would then have the option 
for listening on the $RED interface also.

A similar option to be given for the httpd listening ports and/or interfaces.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1756893&group_id=40604

On Wednesday 18 July 2007 14:17, SourceForge.net wrote:
> Bugs item #1756164, was opened at 2007-07-18 09:17

> Category: Installation
> Group: 1.4.16
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: roy (rhs001)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: permissions on /etc/snort/rules isn't correct
>
> Initial Comment:
> i downloaded the iso for version 1.4.16 and went into the intrusion
> detection and tried a refresh update list and a download new ruleset which
> worked.
>
> when i clicked on "Apply now" i got the following error:
>
> Loading /var/ipcop/snort/oinkmaster.conf
>
> /usr/local/bin/oinkmaster.pl:  Error:  the output directory
> "/etc/snort/rules" isn't writable by you.
>
> Oink  oink.  Exiting...
>
> i did a chown snort:snort on the /etc/snort/rules directory and all the
> files under it and it then worked fine.
>
> i believe that is why update 1.4.15 was released for the same problem i
> believe.
>
> thanks for a great product and i talk you guys up all the time.
>
> roy
>
Hi,
 This seems to be ISO problem alone as the test box got upgraded fro m 1.4.15 
and is fine. A quick test install on a spare box does Roy's trick .
 This may be as the GUI is being run by "admin" user not as  user root..

I had to leave it there as being pressed into doing other things:-{


geo.
-- 
TTFN
   Caparo

Bugs item #1756164, was opened at 2007-07-18 09:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1756164&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: 1.4.16
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: roy (rhs001)
Assigned to: Nobody/Anonymous (nobody)
Summary: permissions on /etc/snort/rules isn't correct

Initial Comment:
i downloaded the iso for version 1.4.16 and went into the intrusion detection and tried a refresh update list and a download new ruleset which worked.

when i clicked on "Apply now" i got the following error:

Loading /var/ipcop/snort/oinkmaster.conf

/usr/local/bin/oinkmaster.pl:  Error:  the output directory "/etc/snort/rules" isn't writable by you.

Oink  oink.  Exiting...

i did a chown snort:snort on the /etc/snort/rules directory and all the files under it and it then worked fine.

i believe that is why update 1.4.15 was released for the same problem i believe.

thanks for a great product and i talk you guys up all the time.

roy


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1756164&group_id=40604

Bugs item #1755634, was opened at 2007-07-17 14:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755634&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: cef1000 (cef1000)
Assigned to: Nobody/Anonymous (nobody)
Summary: upg from 1.4.15 > 1.4.16rc1 > 1.4.16 release

Initial Comment:
Upgrading from 1.4.15 to 1.4.16rc1 went fine, other than the things that are fixed in 1.4.16 (release).

Upgrade from 1.4.16.rc1 > 1.4.16 fails to upload using Web GUI interface.

Error encountered is package failed to install.  

It actually looks like it never uploads either.  Since it took a bit of time going from 1.4.15 > 1.4.16rc1 and the failure was almost instant going from 1.4.16rc1 > 1.4.16 (release)

Title ID is 16 for installed updates after the 1.4.16.rc1 is 1.4.16 is shown as installed, is it possible the header of the update for rc1 and final release indicate the same version and upgrade won't process because of it?

Any ideas, other than a reinstall to get around this ?


cef1000

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755634&group_id=40604

IPCop v1.4.16 is released.

This release fixes some bugs, update glibc , Net::DNS and capi for security
reasons. Upgraded packages are squid, snort, e100, r1000 and pulsar
glibc is a disputed issue CVE-2007-3508 concerning possibility to exploit
the
 bug.(glibc fix miss on our update information).

As usual, this version can be installed as an update from previous v1.4.x
versions or with a ready-to-go ISO or usb bootable images or pxe for a fresh
install.

Files are available on 'IPCop' package at
https://sourceforge.net/project/showfiles.php?group_id=40604

fcdls package is unchanged from 1.4.15
md5sums
for i386 machines
8802707d7663f32436de78d67bec9d63  ipcop-1.4.16-fcdsl.i386.tgz
c0d326c9e7502d46adfd438ecef6e3ce  ipcop-1.4.16-install-cd.i386.iso
eeb21587413d43f3b444b53c9dd1eac3  ipcop-1.4.16-install-pxe.i386.tgz
b503194f3f30f5fa26579a69354e6e7c  ipcop-1.4.16-install-usb-fdd.i386.img.gz
5f57ac7d80170555c229285ccf9e879e  ipcop-1.4.16-install-usb-hdd.i386.img.gz
116cb6f111a079e97ec50975b335f85b  ipcop-1.4.16-install-usb-zip.i386.img.gz
ed0d15d14dc0facab0a5a427b3a8f1fd  ipcop-1.4.16-update.i386.tgz.gpg

for alpha machines
438fc8c70e32c45d6622bc9b5c49a792  ipcop-1.4.16-update.alpha.tgz.gpg
7f5f8c41b436f89a6610d072ee99ed19  ipcop-1.4.16-install-cd.alpha.iso

sources
7d4e3699726c00686aa786bf0c94581d  ipcop-1.4.16-sources.tgz
c90ab4975d39aba3e10dab4f4a745019  ipcop-1.4.16-othersrc.tar.bz2
d157d1aa367383ea1325db1b33767a70  ipcop-1.4.16-othersrc.tar.bz2.md5

Three different usb images are available to boot from usb as some bios may
boot
 with one format and not others:
- fdd is an unpartionned usb key
- hdd is partionned like an hard disk
- zip is partionned like a zip (work with real usb zip device too)

- pxe is a package ready to use for pxe boot on install (instructions
inside)

To copy an usb image to an usb key (minimal size 64 MB), under linux, read
what letter the system give to that key ( cat /proc/partitions | grep sd )
and copy to that device with zcat (the-file) >/dev/sd(letter) without a
partition number. Don't forget the '>' or the output will go to the console.

To copy under Windows, you could uncompress the file and use winimage
(shareware).

- othersrc package contain all packages out of ipcop sources and is
interesting only for those who want to compile IPCop
You don't need to load directly that file on sourceforge as it is more
 convenient to do that from ipcop sources with './make.sh getothersrc'.
It will load, control file md5 and install packages include on cache
directory.

There has been small changes from 1.4.16rc1:
- bug with name resolution has been fixed,
- new sflogo is include in update,
- glibc is patched against a disputed issue CVE-2007-3508
- Net:DNS is upgraded to 0.60 CVE-2007-3377 CVE-2007-3409
- a few package URL download addresses have been updated for people building
- some unneeded wanpipe samples files are removed
If you install rc1 update or a fresh rc1 installation, you could simply take
all changes from final version with a few commands.
Princip is to revert version to 1.4.15 to be able to apply the 1.4.16 final
update without needing other changes
- revert the version to 1.4.15 on web interface
/bin/sed -i -e "s+= '1.4.*$+= '1.4.15';+" /var/ipcop/general-functions.pl
- copy the update .gpg file in /tmp
cd /tmp
gpg -o /tmp/patch.tar.gz --decrypt ipcop-1.4.*.tgz.gpg
tar zxf /tmp/patch.tar.gz
./setup
- remove the files in /tmp

Please report any problems in bug tracking system or on devel list.
You have to subscribe on all ipcop lists to be able send messages.
We were forced on this restriction because of the numerous spam attempts.


 Gilles

Bugs item #1755390, was opened at 2007-07-17 06:11
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755390&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: dbbcomputers (dbbcomputers)
Assigned to: Nobody/Anonymous (nobody)
Summary: Vonage VOIP Support

Initial Comment:
Vonage VOIP does not properly work with latest release of IPCop firewall.  Need Corrective action

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755390&group_id=40604

Feature Requests item #1755387, was opened at 2007-07-17 06:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1755387&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface Improvements (example)
Group: Next release
Status: Open
Priority: 5
Private: No
Submitted By: dbbcomputers (dbbcomputers)
Assigned to: Nobody/Anonymous (nobody)
Summary: Vonage VOIP Support

Initial Comment:
Have Vonage VOIP phone adaptor behind IPCop firewall need to have support / checkbox to enable ports to be opened to the Vonage VOIP machine

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1755387&group_id=40604

Bugs item #1755130, was opened at 2007-07-16 17:21
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755130&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: cef1000 (cef1000)
Assigned to: Nobody/Anonymous (nobody)
Summary: DNS is broken 1.4.15  > 1.4.16 ug

Initial Comment:
When upgrading, using the upgrade release, from 1.4.15 to 1.4.16 DNS dies on both GREEN and BLUE interfaces.

The upgrade was performed on a new 1.4.15 installation from ISO.  There are a couple of addins installed.

Hardware 1.8 Ghz P4
1 Gig Ram
80 Gig HDD

NICS
SIS 900 Onboard 10/100
3Com 10/100
Intel 100 Pro
Dlink 530 10/100

Initial base install: 

1.4.15

Add Ins Installed are:

Sys Info
HDD Temperature

Setting all workstations on Green and Blue to point to an external DNS server allows email and Web traffic to occur properly.

Testing when the issue was noticed consisted of pinging known outside ip address and getting a response, but pinging www.yahoo.com (etc) did not.

There is a thread at www.ipcops.com on this that may be of interest.

http://www.ipcops.com/index.php?name=PNphpBB2&file=viewtopic&p=54116#54116


I have also email Franck Bourdonnec in ipcops user listserv about this.

cef1000

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1755130&group_id=40604

Bugs item #1754197, was opened at 2007-07-15 04:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1754197&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: 1.4.15
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Wojtek (wojzie2022)
Assigned to: Nobody/Anonymous (nobody)
Summary: speed issue 1.4.16

Initial Comment:
Hi,
I have Pantech PX-500 with EVDO service from Sprint.
My IPCOP installation (1.4.16 rc1) works with this card, but speed is decreased about 10x compared to windows


thx
Wojtek 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428516&aid=1754197&group_id=40604

Feature Requests item #1754194, was opened at 2007-07-15 07:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1754194&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Noam Segal (nsegal)
Assigned to: Nobody/Anonymous (nobody)
Summary: Green networks

Initial Comment:
Hi there

Is there a plan to support multiple green networks in the future ?

Thanks,
Noam

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1754194&group_id=40604

On Saturday 14 July 2007 04:21:07 pm Seth Bardash wrote:
> > -----Original Message-----
> > From: ipc...@li...
> > [mailto:ipc...@li...] On Behalf
> > Of Franck Bourdonnec
> > Sent: Saturday, July 14, 2007 1:37 PM
> > To: ipc...@li...
> > Subject: Re: [IPCop-devel] How to install a new driver /
> > Installingthe 3ware 9500/9550 driver
> >
> > > I'm sure that the developers have the  "magic ingredients" at
>
> their
>
> > > fingertips, while I have just learned a few of the easier ones.
> > >
> > > It should not take long to write something on the order of:
> > >
> > > A) Here is the sequence to add a module
> > >
> > > B) Here is the sequence to add a module and have the build process
> > > compile it.
> > >
> > > C) Here is the sequence to add a driver and have the build process
> > > compile it.
> > >
> > > D) Once you succeed, here are the things we need to add it to the
> > > release.
> > >
> > > This type of how-to would further the cause and make it much
>
> easier
>
> > > for the developers and others to add features and functions while
> > > making sure that future releases stay compatible with a
> >
> > greater number
> >
> > > of add-ons. The above how-to processes are done by the
> >
> > developers on a
> >
> > > regular basis and therefore well known to them. Writing them down
> > > would open up the the add-on process to many more people and allow
> > > IPCop to grow at a faster rate for additional functions and
> >
> > additional
> >
> > > hardware support.
> > >
> > > Sincerely,
> > >
> > > Seth Bardash
> >
> > Hello,
> > about addon, it's very simple: very very limited support from
> > the system.
> > Only help is for 'languages' translations files. A little
> > support for OPenvpn
> > added in 1.4.16 and that all. For everything else, it is "elfen sie
> > selbst" ;-)
> >
> > drivers are more complicated. No straight solutions on how
> > install it into
> > a distro. Need 'readmes'
> >
> > Perhaps explaining subdirectory architecture, starting with a copy
>
> of
>
> > an lfs/script, registering files in ROOTFILES.i386 for the final iso
> > could help.
> >
> > The real job is what you did Seth, making the scsi driver compiled
> > correctly. The rest is classic for us. Just post a sourceforge
>
> request
>
> > so that it won't be lost (the lfs/script+particularities).
> >
> > Franck
>
> Its been added and the changes have been uploaded.
>
> email me if there are any questions.
>
> The version I made is working great so far.
>
> Thanks to all the people that have helped put this together.
>
> Seth Bardash
>
> Integrated Solutions and Systems
> 1510 Old North Gate Road
> Colorado Springs, CO 80921
>
> 719-495-5866
> 719-495-5870 Fax
> 719-337-4779 Cell
>
> http://www.integratedsolutions.org
>
> Failure can not cope with knowledge and perseverance!
>
>

Just an lfs script like the e100 and e1000 drivers which are also from 
external sources than the kernel and an addition to the make.sh script to 
build it at the right time is all that is needed. This would even download 
the driver tarball for you if the lfs script is made in the usual manner. 
This is also how many other non native kernel drivers are added to IPCop. No 
need to even change the rootfiles since the scsi part of the driver tree is 
all included when it builds the installer. Changing and re-tarballing the 
kernel seems a bit too kludgy and you'll have to do this every time there is 
a kernel update since the 2.4 kernel is being actively maintained and I'm 
sure 2.4.34 won't be the last.


Dave


 

> -----Original Message-----
> From: ipc...@li... 
> [mailto:ipc...@li...] On Behalf 
> Of Franck Bourdonnec
> Sent: Saturday, July 14, 2007 1:37 PM
> To: ipc...@li...
> Subject: Re: [IPCop-devel] How to install a new driver / 
> Installingthe 3ware 9500/9550 driver
> 
> >
> > I'm sure that the developers have the  "magic ingredients" at
their
> > fingertips, while I have just learned a few of the easier ones.
> >
> > It should not take long to write something on the order of:
> >
> > A) Here is the sequence to add a module
> >
> > B) Here is the sequence to add a module and have the build process
> > compile it.
> >
> > C) Here is the sequence to add a driver and have the build process
> > compile it.
> >
> > D) Once you succeed, here are the things we need to add it to the
> > release.
> >
> > This type of how-to would further the cause and make it much
easier
> > for the developers and others to add features and functions while
> > making sure that future releases stay compatible with a 
> greater number
> > of add-ons. The above how-to processes are done by the 
> developers on a
> > regular basis and therefore well known to them. Writing them down
> > would open up the the add-on process to many more people and allow
> > IPCop to grow at a faster rate for additional functions and 
> additional
> > hardware support.
> >
> > Sincerely,
> >
> > Seth Bardash
> >
> 
> 
> Hello,
> about addon, it's very simple: very very limited support from 
> the system.
> Only help is for 'languages' translations files. A little 
> support for OPenvpn
> added in 1.4.16 and that all. For everything else, it is "elfen sie 
> selbst" ;-)
> 
> drivers are more complicated. No straight solutions on how 
> install it into
> a distro. Need 'readmes'
> 
> Perhaps explaining subdirectory architecture, starting with a copy
of 
> an lfs/script, registering files in ROOTFILES.i386 for the final iso
> could help.
> 
> The real job is what you did Seth, making the scsi driver compiled
> correctly. The rest is classic for us. Just post a sourceforge
request
> so that it won't be lost (the lfs/script+particularities).
> 
> Franck

Its been added and the changes have been uploaded.

email me if there are any questions.

The version I made is working great so far.

Thanks to all the people that have helped put this together.

Seth Bardash

Integrated Solutions and Systems
1510 Old North Gate Road
Colorado Springs, CO 80921

719-495-5866
719-495-5870 Fax
719-337-4779 Cell

http://www.integratedsolutions.org

Failure can not cope with knowledge and perseverance! 
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.6/900 - Release Date:
7/14/2007 3:36 PM
 

Feature Requests item #1754148, was opened at 2007-07-14 17:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1754148&group_id=40604

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Seth Bardash (sbardash)
Assigned to: Nobody/Anonymous (nobody)
Summary: Adding a driver to the kernel

Initial Comment:
I needed to install the 3ware 3w-9xxx.o driver to support the 95XX Series of controller on our firewall.


1) I used a dual opteron 290 machine with 3.5 GB of enhanced latency memory and a 4 disk raid 0 array with dual monitors running Centos 3.8 with updates.

(I also changed the linux lfs build file from make -j 3 to make -j 6 -
this helped!!)

2) Install the IPCop source and then have the system download the "getothersrc" -> ./make.sh getothersrc just like it says in the build howto.

3) Read the build how to - this helps but is missing the magic ingredients to actually add new stuff

4) run ./make.sh build the first time through to set up the kernel directory under build/usr/src

5) It now helps if you copy and install the same base kernel from the cache directory to another directory so that you can test and modify any files needed by the new driver(s).

6) This is where it gets a little tricky.
	
You need to modify the build/usr/src/linux/drivers/xxx files. I modified the scsi directory to add the 3w-9xxx driver. I added a line to the Makefile and I added a line to the Config.in file for the 3w-9xxx driver. 	Then I added a line to the defconfig file in build/usr/src/linux/arch/i386/for the 3w-9xxx driver

Then I changed the 3 files in pcop-1.4.15/config/kernel that are used to build the 3 different kernel .config files so that they build the 3w-9xxx.o driver module during the kernel build process.

7) You now need to make these modifcations to a bare untar'ed kernel tree and re-tar.gz the kernel,  run md5sum on the kernel and take that value and insert it into the file ipcop-1.4.15/lfs/linux

8) Copy the new linux-x.x.x.tar.gz file to the ipcop-1.4.15/cache directory.

9) run ./make.sh clean then ./make.sh build and your new driver should
be there in the install.

I now have an IPCop iso that supports all the 3ware PCI based cards.

Hope this helps......

;-)

Seth Bardash


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=428519&aid=1754148&group_id=40604

On Sunday 08 July 2007 10:20:15 pm Olaf Westrik wrote:
> Hello David,
>
>
> good catch!
>
> > Now I got it working. I renamed rc.netaddress.up and rc.updatered eith a
> > .new extension just in case I wanted to go back and dropped the
> > rc.netaddress.up and rc.updatered files from 1.4.15 in place and it works
> > fine now. Since we are not going to use the changes, shouldn't we just
> > revert back to the previous versions of these two files?
> >
> > Ok. Now I'll sit back and see what happens.
>
> For starters rc.updatered is broken, since it no longer (after rev
> 1.11.2.22) starts dnsmasq with remote DNS server IP addresses.
>
> Could you change lines 85-87 in rc.updatered from:
> if [ -e "CONFIG_ROOT/red/dial-on-demand" -a "$DIALONDEMANDDNS" == "on"
> -a ! -e "CONFIG_ROOT/red/active" ]; then
>     OPT_DNSMASQ="-r CONFIG_ROOT/ppp/fake-resolv.conf $OPT_DNSMASQ"
> fi
>
> into:
> if [ -e "CONFIG_ROOT/red/dial-on-demand" -a "$DIALONDEMANDDNS" == "on"
> -a ! -e "CONFIG_ROOT/red/active" ]; then
>     OPT_DNSMASQ="-r CONFIG_ROOT/ppp/fake-resolv.conf $OPT_DNSMASQ"
> else
>     OPT_DNSMASQ="-r CONFIG_ROOT/red/resolv.conf $OPT_DNSMASQ"
> fi
>
> cheers Olaf

It looks like Gilles has fixed the two files, one reverted, one just cleaned 
up. I would guess that rc2 is coming now?


Dave

>
> I'm sure that the developers have the  "magic ingredients" at their
> fingertips, while I have just learned a few of the easier ones.
>
> It should not take long to write something on the order of:
>
> A) Here is the sequence to add a module
>
> B) Here is the sequence to add a module and have the build process
> compile it.
>
> C) Here is the sequence to add a driver and have the build process
> compile it.
>
> D) Once you succeed, here are the things we need to add it to the
> release.
>
> This type of how-to would further the cause and make it much easier
> for the developers and others to add features and functions while
> making sure that future releases stay compatible with a greater number
> of add-ons. The above how-to processes are done by the developers on a
> regular basis and therefore well known to them. Writing them down
> would open up the the add-on process to many more people and allow
> IPCop to grow at a faster rate for additional functions and additional
> hardware support.
>
> Sincerely,
>
> Seth Bardash
>


Hello,
about addon, it's very simple: very very limited support from the system.
Only help is for 'languages' translations files. A little support for OPenvpn
added in 1.4.16 and that all. For everything else, it is "elfen sie 
selbst" ;-)

drivers are more complicated. No straight solutions on how install it into
a distro. Need 'readmes'

Perhaps explaining subdirectory architecture, starting with a copy of 
an lfs/script, registering files in ROOTFILES.i386 for the final iso
could help.

The real job is what you did Seth, making the scsi driver compiled
correctly. The rest is classic for us. Just post a sourceforge request
so that it won't be lost (the lfs/script+particularities).

Franck