Date: Mon, 02 Jun 2008 22:32:26 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Reinhold <freebsd@violetlan.net> Cc: Odhiambo Washington <odhiambo@gmail.com>, freebsd-questions@freebsd.org Subject: Re: mpd5 stoped working after subnet change Message-ID: <48444ACA.8040308@FreeBSD.org> In-Reply-To: <1212434598.00078576.1212423606@10.7.7.3> References: <1212067397.00076529.1212056411@10.7.7.3> <1212405782.00078336.1212393602@10.7.7.3> <1212412984.00078364.1212401401@10.7.7.3> <1212420183.00078428.1212406801@10.7.7.3> <1212420230.00078485.1212409802@10.7.7.3> <1212423783.00078487.1212411001@10.7.7.3> <1212427398.00078528.1212417001@10.7.7.3> <1212430983.00078536.1212417602@10.7.7.3> <1212434588.00078564.1212422402@10.7.7.3> <1212434598.00078576.1212423606@10.7.7.3>
next in thread | previous in thread | raw e-mail | index | archive | help
Reinhold wrote: >> So, upon connection, there was a bandwidth of 64000bps, but upon >> closing that session, the b/w is 9600bps. >> > I see the same things since I started logging the connection. > At the start I see this > mpd5: [B-3] Bundle: Status update: up 1 link, total bandwidth 64000 bps > and at the end its > mpd5: [B-3] Bundle: Status update: up 0 links, total bandwidth 9600 bps Those speeds mean nothing to you actually. They are used _only_ for multilink load balancing. 64000 is the default that can be changed manually by configuration, but as I have said it is meaningless whan multilink is not used. PPTP protocol has capabilities to make PAC inform PNS side about connection speed, but it is only informational and in no way interfere with real transfer speeds. > This is a bit OT because my original problem got fixed thanks to you, I > still have no idea what fixed it though, hehehe Logging (probably increased to 'log +phys2 +phys3') and tcpdump on a physical interface should help you if problem will get back again. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48444ACA.8040308>