At 02:48 19-2-2002 -0600, Nick Rogness wrote:
>On Sun, 17 Feb 2002, Zviratko wrote:
>
> >
>[SNIP]
> >
> > I will try that, but I guess default route has precedence over ipfw.
>
> Not in the case of ipfw fwd. The routing decision seems to be
> made before ipfw fwd changes the packe
On Mon, Feb 18, 2002 at 01:44:05PM -0800, Sean Chittenden wrote:
> > The only real "cisco only" protocol is the PAgP (Port Aggregation
> > Protocol) which is essentially just a FEC auto-negiotation protocol they
> > made up. AFAIK noone other then Cisco actually implements this though.
>
> Don'
On Sun, 17 Feb 2002, Zviratko wrote:
>
[SNIP]
>
> I will try that, but I guess default route has precedence over ipfw.
Not in the case of ipfw fwd. The routing decision seems to be
made before ipfw fwd changes the packet.
Nick Rogness <[EMAIL PROTECTED]>
- Don't mind me...I
>> The only real "cisco only" protocol is the PAgP (Port Aggregation
>> Protocol) which is essentially just a FEC auto-negiotation protocol they
>> made up. AFAIK noone other then Cisco actually implements this though.
> Don't forget to add EIGRP and CDP to the list. -sc
actually, the one with
> The only real "cisco only" protocol is the PAgP (Port Aggregation
> Protocol) which is essentially just a FEC auto-negiotation protocol they
> made up. AFAIK noone other then Cisco actually implements this though.
Don't forget to add EIGRP and CDP to the list. -sc
--
Sean Chittenden
To Un
> > ng_fec needs a cisco at the other end (or possibly another freebsd
> > machine with ng_fec but I don't know that).
Fast EtherChannel doesn't actually require a Cisco device on the other
side, it is really just a "non-standardized standard" for the hashing
that decides which physical interfa
I just got it to work by using ng_one2many:
ifconfig ed1 up lladdr 00:88:e8:83:63:c0
ifconfig ed2 up lladdr 00:88:e8:83:63:c0
kldload /modules/ng_ether.ko
ngctl mkpeer ed1: one2many upper one
ngctl connect ed1: ed1:upper lower many0
ngctl connect ed2: ed1:upper lower many1
ngctl msg ed2: setpromi
>
> > Hi,
> > is there a preferred way to do ethernet load balancing? My situation
is - 2
> > cable modems connected to two ethernet cards on with a machine
functioning
> > as a NAT gateway for LAN. I tried netgraph (ng_ether with round robin
and
> > ng_fec). With ng_ether, I achieved packets bei
On Sun, 17 Feb 2002, Zviratko wrote:
> Hi,
> is there a preferred way to do ethernet load balancing? My situation is - 2
> cable modems connected to two ethernet cards on with a machine functioning
> as a NAT gateway for LAN. I tried netgraph (ng_ether with round robin and
> ng_fec). With ng_et
