Date: Fri, 13 Jan 2006 15:20:08 +0000 From: Tom Jobbins <tomjobbins@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Two PPP connections to the same ISP with same remote gateway Message-ID: <a3d37d280601130720i1d4b8830q@mail.gmail.com> In-Reply-To: <200601131309.24446.doconnor@gsoft.com.au> References: <a3d37d280601121337y64ec3965r@mail.gmail.com> <200601131309.24446.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for replying, Daniel This is really odd, because I don't see this on my machines (as per our > discussion on IRC which you mention below), I did.. > > midget# cat /dev/tun & > [1] 21524 > midget# cat /dev/tun & > [2] 21525 I've isolated the difference. If I repeat exactly what you do - including the two cat /dev/tun commands - then it works for me too. So long as the tun0 and tun1 interfaces are created with a cat /dev/tun &, I am able to give them matching remote gateway addresses. However this is not the case when the interfaces are created any other way, i.e. via ppp. Ditto ng0/ng1 created by mpd. Also, if I then kill the cat /dev/tun commands, leaving tun0 and tun1 existing, but unopened, I am then no longer able to set the matching gateway. And if I don't kill the cat commands, ppp can't use those tun devices because another process has them open. So it would appear this was just a dead end. I don't know whats different about an interface created with the cat command - perhaps as it's not connected to a real network utility, the normal route checking does not apply? If you - or anyone else - has any more ideas as to what I can try to make this work, I would be most grateful. It's incredibly frustrating to be limited in this way, given that I'm almost certain that ipfilters source-based routing will get around any routing issues if I could only bring the interfaces up. Thanks Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a3d37d280601130720i1d4b8830q>