Hello rip,
Are you sure that you want only one subnet? In your case two different
subnets on two interfaces IMHO look much better. If you are sure about
one-subnet setup than you should try to set up a bridge(4) between
them two NICs. Bridge in FreeBSD is supporting ipfw filtering, so
you can stil
I know about the broken IPSEC problem so I have compiled kernel with
FAST_IPSEC. The man pages say:
"In general, the Fast IPsec implementation is intended to be compatible
with the KAME IPsec implementation."
Then, when reading 14.10 VPN over IPsec docs...
http://www.freebsd.org/doc/en_US.ISO8
> The second problem you are having is that you can't have two NIC on the
> same subnet.
Well it is possible to do but it is kind of useless to put 2 nic interfaces on
the same subnet, unless you can have 1 gbit incomming and 2 100 nic
downstreaming it over the subnet but this will need a load
On Sep 2, 2004, at 2:17 PM, rip wrote:
I am trying to make a configuration to isolate the WiFi APs on a
single segment. DHCP hands out 'good' addresses (10.0.0.x) to MACs it
recognizes and 'bad' (10.99.0.x) when the MAC does not match and is
taken from the common pool.
I then will use ipfw to bl
Hello All;
Here is the puzzle
Config : 5.1-Release
3 xl interfaces xl0, xl1, xl2
I am trying to make a configuration to isolate the WiFi APs on a single
segment. DHCP hands out 'good' addresses (10.0.0.x) to MACs it
recognizes and 'bad' (10.99.0.x) when the MAC does not match and is
taken fro
I forgot to mention, that it's FreeBSD 5.2.1. On FreeBSD 4.10 this problem
doesn't occur.
--
// WWW: apm.cifrid.net // PGP: finger [EMAIL PROTECTED] //
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscri
Pound (http://www.apsis.ch/pound) is a http reverse proxy and
load balancer. While I was playing with it, I ran into a weird thing.
After pound forwards a connection to a backend, something like this occurs
(truss output):
connect(0x3,{ AF_INET 182.5.5.8:49087 },16) ERR#36 'Operation now in
