Tips for MPD PPtP Re: still troubles with MPD and WinXP
- Original Message - From: "Sergey Matveychuk" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: still troubles with MPD and WinXP > I still a troubles with MPD (now 3.12) and WinXP. > Slow and bad connection :( Bill Moran wrote up these tips based on some testing he did when I was having problems last month, perhaps they will help you ? The main thing I found was to turn off Multilink on the Windows side. Do a search on google groups for: "PPtP Client to MPD to boxes behind NATD are very slow?? (solved?)" Regards, John. __ Get your FREE personalized e-mail at http://www.canada.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: still troubles with MPD and WinXP
> In your /etc/ppp/ppp.conf you should set > set timeout 0 > in the appropriate section that refers to your PPTP connection. That > might fix this problem if this is indeed a timeout issue as you said. Thank you. It's seams to be better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Tips for MPD PPtP Re: still troubles with MPD and WinXP
> Bill Moran wrote up these tips based on some testing he did when I was > having problems last month, perhaps they will help you ? The main thing > I found was to turn off Multilink on the Windows side. > Do a search on google groups for: > "PPtP Client to MPD to boxes behind NATD are very slow?? (solved?)" I'v tried all tips I found. Nothing help. I'v varied MTU size, set multilink on and off and so on. All tips I'v found in FreeBSD mail lists and google. Thinks was going better or worse but not good. All troubles I got when I moved from Win2k to WinXP. Here if my mpd.conf: default: load ciam-pptp ciam-pptp: new -i ng0 ciam-pptp ciam set iface disable on-demand set iface idle 1800 set iface enable proxy-arp set iface mtu 1400 set iface up-script /usr/local/etc/mpd/mpd-up.sh set iface down-script /usr/local/etc/mpd/mpd-down.sh set ipcp ranges 192.168.1.1/32 192.168.1.100/32 set ipcp dns 192.168.1.1 set bundle disable multilink # set link mtu 1460 set link disable pap set link enable chap #set link enable no-orig-auth set link keep-alive 10 60 # # enable Microsoft encryption # set bundle enable encryption #set bundle enable crypt-reqd set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless All mpd.conf I'v seen was a similar but without up/down scripts. This scripts set ipfw rules only but may be something goes wrong with mpd when it run the scripts? I'v thought it's my WinXP fault but it works fine with poptop. But I don't satisfy of poptop stability though. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Tips for MPD PPtP Re: still troubles with MPD and WinXP
> Bill Moran wrote up these tips based on some testing he did when I was > having problems last month, perhaps they will help you ? The main thing > I found was to turn off Multilink on the Windows side. > Do a search on google groups for: > "PPtP Client to MPD to boxes behind NATD are very slow?? (solved?)" I'v tried all tips I found. Nothing help. I'v varied MTU size, set multilink on and off and so on. All tips I'v found in FreeBSD mail lists and google. Thinks was going better or worse but not good. All troubles I got when I moved from Win2k to WinXP. Here if my mpd.conf: default: load ciam-pptp ciam-pptp: new -i ng0 ciam-pptp ciam set iface disable on-demand set iface idle 1800 set iface enable proxy-arp set iface mtu 1400 set iface up-script /usr/local/etc/mpd/mpd-up.sh set iface down-script /usr/local/etc/mpd/mpd-down.sh set ipcp ranges 192.168.1.1/32 192.168.1.100/32 set ipcp dns 192.168.1.1 set bundle disable multilink # set link mtu 1460 set link disable pap set link enable chap #set link enable no-orig-auth set link keep-alive 10 60 # # enable Microsoft encryption # set bundle enable encryption #set bundle enable crypt-reqd set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless All mpd.conf I'v seen was a similar but without up/down scripts. This scripts set ipfw rules only but may be something goes wrong with mpd when it run the scripts? I'v thought it's my WinXP fault but it works fine with poptop. But I don't satisfy of poptop stability though. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
mpd bridging
Hi, I've seen Julian and Archie suggest bridging with mpd several times on this list, as a solution to forwarding packets like UDP broadcasts. Now that I again encountered such an issue, I'd like to know exactly how to bridge an ethernet interface, lets say fxp0, and a few mpd-supplied ng0-3 interfaces. I found a sample script that is supposed to establish netgraph bridging between the specified interfaces, however, that fails to work. Regards, Anthony Volodkin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: 5.0-REL alias problem
On 2003-02-10 14:59, Matthew Jonkman <[EMAIL PROTECTED]> wrote: > I can't add more than one alias to an interface on a new install of > 5.0-rel. > > I have tried specifying every possible detail of the alias but no > change, just get this: > > ifconfig: ioctl (SIOCAIFADDR): File exists > > The first alias works fine, can't add more. Notable details: The aliases > are in the same subnet but trying aliases in other subnets has the same > effect. Hmmm, are you sure you're using the correct ifconfig params? # ifconfig lo0 127.0.0.2 netmask 255.255.255.255 alias # ifconfig lo0 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 inet 127.0.0.2 netmask 0x # ifconfig lo0 127.0.0.2 netmask 255.255.255.255 -alias # ifconfig lo0 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
RE: 5.0-REL alias problem
As far as I know, but please detail what they should be. I've made more than my share of dumb mistakes in my lifetime. Here's an example of adding a new one. No aliasas will set now, I've tried to do them in rc.conf. # ifconfig rl0: flags=8843 mtu 1500 inet XXX.XXX.44.91 netmask 0xfff8 broadcast XXX.XXX.44.95 ether 00:05:5d:32:c6:9c media: Ethernet autoselect (10baseT/UTP) status: active rl1: flags=8843 mtu 1500 inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 ether 00:50:70:d1:17:02 media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 ng0: flags=8890 mtu 1500 # ifconfig rl0 alias XXX.XXX.44.92 netmask 255.255.255.248 ifconfig: ioctl (SIOCAIFADDR): File exists IP's altered to protect innocent firewalls. Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Giorgos Keramidas Sent: Saturday, February 15, 2003 11:07 PM To: Matthew Jonkman Cc: [EMAIL PROTECTED] Subject: Re: 5.0-REL alias problem On 2003-02-10 14:59, Matthew Jonkman <[EMAIL PROTECTED]> wrote: > I can't add more than one alias to an interface on a new install of > 5.0-rel. > > I have tried specifying every possible detail of the alias but no > change, just get this: > > ifconfig: ioctl (SIOCAIFADDR): File exists > > The first alias works fine, can't add more. Notable details: The aliases > are in the same subnet but trying aliases in other subnets has the same > effect. Hmmm, are you sure you're using the correct ifconfig params? # ifconfig lo0 127.0.0.2 netmask 255.255.255.255 alias # ifconfig lo0 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 inet 127.0.0.2 netmask 0x # ifconfig lo0 127.0.0.2 netmask 255.255.255.255 -alias # ifconfig lo0 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: pim6sd crash
> On Fri, 14 Feb 2003 17:43:57 + (GMT), > Abdul Basit <[EMAIL PROTECTED]> said: > on freebsd 5.0-Release, pim6sd crashes if i execute > ifconfig gifX destroy if it is running in background, > i need to restart it manually. > pim6sd display 'check_vif_state' Device not configured > and exits. any workaround ? A workaround is not to destroy an interface when pim6sd is running on the interface. Note that this kind of trouble is not specific to pim6sd. Dynamic interface creation/deletion is a big architectural change to the traditional BSD kernel, and I bet there are many other applications affected by such an operation. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
