I have 3 machines running freebsd 4.5. I want to configure one of as a router.
One machine (A) has a IP of 131.123.36.65 (dc0). This needs to be connected to
another machine (B) 131.123.36.102 (ed1)through a machine (R) that has two
network cards 131.123.36.98(dc0) and 131.123.36.101(dc1). The ne
On Sun, Feb 01, 2004 at 05:20:43AM -0500, Sandeep kumar Davu wrote:
> I have 3 machines running freebsd 4.5. I want to configure one of as a router.
> One machine (A) has a IP of 131.123.36.65 (dc0). This needs to be connected to
> another machine (B) 131.123.36.102 (ed1)through a machine (R) that
On Fri, Jan 30, 2004 at 05:20:19PM -0600, Bob Van Valzah wrote:
> A port of the whole xorp world might be a better target than just the
> pim part. That wouldn't take much since it compiled easily. But it is
> a whopper--nearly 1 GB required to build.
XORP would be good as a separate port, but f
At Sat, 31 Jan 2004 15:27:03 +0100,
Dario Freni wrote:
>
> [1 ]
> Hi guys,
> I was wondering if the standard implementation of IPoFW is planning to
> be implemented. I'm not expert on device writing, I was also looking for
> some workarounds, like attach the fwe0:lower netgraph hook to a virtual
Hi,
I have once tried to implement IP over firewire with earlier ID. spec.
in the previous version of driver. The packetization, ARP and broadcast
is not difficult to implement.
However, I cannot believe the MCAP mechanism will not work properly,
since limited No. of acceptable stream channels is