Date: Tue, 22 Apr 2003 01:03:36 +0200 From: Christian Brueffer <chris@unixpages.org> To: Darcy Buskermolen <darcy@wavefire.com> Cc: freebsd-net@freebsd.org Subject: Re: Netgraph one2many Message-ID: <20030421230336.GC17943@unixpages.org> In-Reply-To: <200304211149.54495.darcy@wavefire.com> References: <200304210931.27836.darcy@wavefire.com> <20030421173558.GB17943@unixpages.org> <200304211149.54495.darcy@wavefire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--+xNpyl7Qekk2NvDX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Apr 21, 2003 at 11:49:54AM -0700, Darcy Buskermolen wrote:
> On Monday 21 April 2003 10:35, Christian Brueffer wrote:
> > On Mon, Apr 21, 2003 at 09:31:27AM -0700, Darcy Buskermolen wrote:
> > > I'm trying to implement a one2many setup however I'm getting the
> > > following errorm msg:
> > >
> > > bash-2.0$ ngctl mkpeer xl1: one2many upper one
> > > ngctl: send msg: No such file or directory
> > > bash-2.0$
> >
> > Have you loaded the ng_ether and ng_one2many modules?
> >
> > - Christian
>=20
> Thanks, I was missing the ng_ether. In playing around with this I came u=
p=20
> with an idea that might be a viable way to solve a customers problem that=
=20
> they are having with their VPN. Their ADSL provider, in an effort to=20
> discurage using their non business accounts for server type purposes have=
=20
> imposed a per connection bandwith limit of 128Kbit. This makes the VPN=20
> somewhat slow for his purposes. I've used netgraph and ksock to create=
=20
> tunnels for routing of IPX information etc. this has made me wonder if it=
's=20
> possible to bind a bunch of these ksocks together to create a one2many ov=
er 7=20
> tunnels, to allow the VPN to use the full bandwith? How probabel does th=
is=20
> sound for implementing in the following mannor?
>=20
> #create interface for connection 1
> ngctl mkpeer tee dummy left2right
> ngctl name dummy tee1
> ngctl mkpeer tee1: ksocket left inet/dgram/udp
> ngctl name tee1:left ksock1
>=20
> #create interface for connection 2
> ngctl mkpeer tee dummy left2right
> ngctl name dummy tee2
> ngctl mkpeer tee2: ksocket left inet/dgram/udp
> ngctl name tee2:left ksock2
>=20
> # bind connection1
> ngctl msg ksock1: bind inet/${LOCAL_IP}:4096
> ngctl msg ksock1: connect inet/${REMOTE_IP}:4096
>=20
> #bind connection2
> ngctl msg ksock2: bind inet/${LOCAL_IP}:4097
> ngctl msg ksock2: connect inet/${REMOTE_IP}:4097
>=20
> #bind to the existing VPN on gif0
> ngctl mkpeer gif0: one2many upper one
> ngctl connect tee1: gif0:upper lower many1
> ngctl connect tee2: gif0:upper lower many2
> ngctl msg gif0:upper setconfig "{xmitAlg=3D1 failAlg=3D1 enabledLinks =
=3D[ 1 1 ]=20
> }"
>=20
Sorry, can't answer that one. I have never used one2many in production
environments.
- Christian
--=20
Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org
GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D
--+xNpyl7Qekk2NvDX
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+pHjIbHYXjKDtmC0RAp4zAKDIS5wnksSUQVzgCjhnwycUQYw7IwCeLJ+D
60B61W/uYklg5mdv4D2wy2g=
=Bigu
-----END PGP SIGNATURE-----
--+xNpyl7Qekk2NvDX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030421230336.GC17943>