> Can you be a bit more specific about the setup details? Are you trying
to describe a setup like this
eth0 - 10 (or 100) Mbps NIC connecting to the Internet
eth1 - 10 (or 100) Mbps NIC connecting to LAN A (eth1, 192.168.1.0
network)
eth2 - 10 (or 100) Mbps NIC connecting
>You did not tell us what is your Internet side. Do you happen to be on
a pppoe connection? If so - did you setup CLAMPMSS=YES in Shorewall
config? That will really slow things down if you didn't.
Victor thanks for the reply.
CLAMPMSS=No.
Not using PPPOE.
- Bob Coffman
Forgot to add details of FTP server and test client:
FTP server is W2003/IIS. Test client is WinXP.
I did reload the original Bering 1.2 config (which used 2 3c509 NICs in a
straight 2 interface configuration) and got 2 Megabytes/sec using the FTP
test. Hardware appears to be fine after all.
-
Robert K Coffman Jr - Info From Data Corporation wrote:
Can you be a bit more specific about the setup details?
This is a bit of a long shot. But in your detailed report, I noticed this:
/proc/interrupts
CPU0
0: 159264 XT-PIC timer
1: 2 XT-PIC keyboa
Ray,
I disabled the serial ports. If there was a winmodem in this box, I would
remove it (or as my brother says, "gank it outta there") since it is a
router. I'll disable everything I can when I set one up. I happened to
choose IRQ 3 for this card because I could set that by jumper, and therefo
This is the problem:
[1] As desired, tcp 3389 is forwarded (DNAT) from the
Bering-uClibc/shorewall box to a server on the local LAN, when using
the the firewall's external interface.
[2] When using a DMZ address, tcp 3389 is also forwarded to that server
on the local LAN, and NOT the
Is this a drop-in replacement for existing implementations?
If not, howto find what requires change?
Thank you.
* "K.-P. Kirchdörfer" <[EMAIL PROTECTED]> [2005:04:27:18:54:31+0200] scribed:
> Am Dienstag, 26. April 2005 12:41 schrieb Pascal OFFREDO:
> > OpenVpn 2.0 final has been released
> >
>
