I was working on some test machines and using ifstated which uses the
KQUEUE event to register changes in link state. I noticed that
ifstated did register any events having to do with the em interfaces.
Looking through the code, it doesn't appear to support the KQUEUE
events. Am I correct in say
Hi,
Here is my setup:
fxp0: no ip -> switch -> (computer with ip: 200.200.200.147, gateway
200.200.200.145)
^
|
bridged
|
\/
fxp1: 200.200.200.146, 148, 149, 150 -> ->
(internet)
^
ipf/ipnat
|
\/
fxp2: 192.168.1.1 -> switch -> lots of computers with 192.168.1.x addresses
(all use 1
Hello, First off, a great thanks to this list who pointed out my hardware
issue (rl series cards). I now have the bridge on two Intel Pro NICS and I
use the on-board sis card for console access, and my average ping time is a
2ms average to the router, passing about a solid 2MB/s.
My current sit
>
> Why dont you all do yourselves a favor and go out and buy one of those
> home dsl/cable modems that have 2 ports and provide load balancing
> instead.
>
[Mitch says:]
The only ones I've seen were rather expensive and aren't modem's - they are
routers... so you have to still have your ADSL mo
Mitch (Bitblock) said:
> Short answer is "Yes".
>
> For basic failover, I've used a script which monitors link status and
> function (by pinging or connecting to a remote host). Failover is
> accomplished by switching the default route.
>
> Using ipfw fwd statements, you can make both links functi
> NiY wrote:
>
> >Greetings! I have yet to find a definitive answer on this subject, so
> >I was hoping someone would let me know the official way to go about
> >this, or if it's even possible.
> >
> >We have two ADSL services coming into out building. We would like to
> >use them both on one netw
On Sun, 08 Aug 2004 13:01:00 -0400, Mike Tancsa <[EMAIL PROTECTED]> wrote:
> On Mon, 26 Jul 2004 21:14:33 -0700, in sentex.lists.freebsd.net you
> wrote:
>
> >Mike Tancsa wrote:
> >
> >>On Sat, 24 Jul 2004 20:42:01 -0700, in sentex.lists.freebsd.net you
> >>wrote:
> >>
> >>
> >Seriously thou
Hi,
Thanks for your reply. I noticed that this indeed was using
the Intel 82546EB chip after sending the e-mail to the list.
Anyway I can feel a bit more comfortable in getting this now!
thnks n rgds
-kc.
Christian Brueffer <[EMAIL PROTECTED]> wrote on 16-12-2004 09:46:02 PM:
> On Thu, Dec 1
On Thu, 16 Dec 2004, KC Somaratne wrote:
Hi,
Is there going to be any support for the above HP EtherNet
card in FreeBSD 5.3-RELEASE?
Most of the HP cards listed in the hardware notes for this
relase seem to be end-of-life by HP..!
Most of the hp ethernet cards are rebadged broadcoms
--
Sten Sp
On Thu, Dec 16, 2004 at 07:54:01PM +0800, KC Somaratne wrote:
> Hi,
>
> Is there going to be any support for the above HP EtherNet
> card in FreeBSD 5.3-RELEASE?
>
> Most of the HP cards listed in the hardware notes for this
> relase seem to be end-of-life by HP..!
>
According to the HP websit
On Thu, Dec 16, 2004 at 09:49:17AM +0500, ??? ? wrote:
?> I'm having this application (VPN daemon) which
?> uses divert sockets for sending stuff http://www.targeted.org/nest/
?> It worked fine under 5.3-RELEASE but broke after
?> recent upgrade to FreeBSD 5.3-STABLE.
?>
?> An attempt
Hello John,
You can use two ways:
1. Add 'unregistered_only yes' to your natd.conf
2. Run natd on xl2 with -reverse option
If I were you I would do the first one.
Thursday, December 16, 2004, 1:06:03 PM, John Angelmo wrote:
JA> Hello
JA> I have a network setup like this:
JA> xl0: External:213
Hi,
Is there going to be any support for the above HP EtherNet
card in FreeBSD 5.3-RELEASE?
Most of the HP cards listed in the hardware notes for this
relase seem to be end-of-life by HP..!
thnks in adv,
-kc.
___
[EMAIL PROTECTED] mailing list
htt
Hi,
I am evaluating ath driver with Senao AR5212 chip based miniPCI card.
Motherboard used is Geode based WRAP. While it works well in modes 11b and
11g, performance in 11a mode I need is suboptimal, as said in man page - even
worse. However, test with newer driver, albeit with linux system, wor
Hello
I have a network setup like this:
xl0: External:213.115.251.220
xl1: DMZ: 213.115.148.64/28
xl2: Internal: 192.168.20.0/24
Now my problem seems to be that I need to get external connection for my
Internal network but not nating the DMZ
To simplify it all /etc/natd.conf has this line:
interf
15 matches
Mail list logo