ISA cards are often fussy.

If you know the resources you want it to use and the name of the module, you
can configure it manually (as on of the options)

for example, an ne2000's card module name is 'ne'. If its io = 0x300 and irq
= 10 you would set it up on the manual configuration line as follows:

ne io=0x300 irq=10

If you don't know what resources your ISA card is set to, you can probably
download a tool to take it off of PnP and set it to jumperless, and pick the
io/irq combination you want it to use (irq=10, io=0x300 is usually a pretty
safe bet). In the end grabbing another (different make and model) PCI
network card may be the easiest solution though.

As for running a fax server. I don't know your exact requirements but in
principal I'd recommend a separate box. Every service you run on a firewall
is a possible liability/point of weakness. The more stuff running, the more
potential weaknesses, the more work required to maintain it (security wise).
Your call.

Hope that helps.

Marcel

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 06, 2003 12:17 PM
> To: [EMAIL PROTECTED]
> Subject: (clug-talk) IPCop 1.3
> 
> 
> : 
> 
>  
> Hello 
>  
> I've some problem with IPCop. first, it doesnt detect one of 
> my network card. 
> maybe its because its an ISA card ? I remember that poeple 
> talked about this 
> problem on may's meeting... but I'm not able to use both card 
> at a time. i can 
> use my PCI card as eth0 or eth1, but not both interface at 
> the same time. 
>  
> thanks. 
>  
> as a second question, if anyone have ever made a fax server 
> with IPCop, I 
> would really like to have any informations about that. 
>  
> thanks  
>  
> Mathieu 
>  
>  
> 

----------------------------------------------------------------------------
This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take action
relying on it. Any communication received in error, or subsequent reply,
should be deleted or destroyed.

Reply via email to