Hi Archie, I've another, probably unrelated problem that has surfaced with mpd-netgraph in the last couple of months. The work-around is simple, which is why it's taken me so long to get around to raising the issue.
I start mpd-netgraph at boot time, to create a VPN link to my office, with a script /usr/local/etc/rc.d/mpd. That used to work fine, and I haven't changed my mpd configuration at all in the mean time. For the last couple of months, though, this has resulted in no ng0 node, and a log that looks like: Feb 5 21:41:46 gurney mpd: mpd: pid 240, version 3.6 ([EMAIL PROTECTED] 18:28 19-Jan-2002) Feb 5 21:41:46 gurney mpd: [vpn] can't create socket node: Exec format error Feb 5 21:41:46 gurney mpd: mpd: local IP address for PPTP is xxx.xxx.xxx.xxx Feb 5 21:41:46 gurney mpd: [vpn] using interface Feb 5 21:41:46 gurney mpd: [vpn] IFACE: Open event Feb 5 21:41:46 gurney mpd: [vpn] IPCP: Open event Feb 5 21:41:46 gurney mpd: [vpn] IPCP: state change Initial --> Starting Feb 5 21:41:46 gurney mpd: [vpn] IPCP: LayerStart Feb 5 21:41:46 gurney mpd: [vpn] bundle: OPEN event in state CLOSED Feb 5 21:41:46 gurney mpd: [vpn] opening link "vpn"... Feb 5 21:41:46 gurney mpd: [vpn] link: OPEN event Feb 5 21:41:46 gurney mpd: [vpn] LCP: Open event Feb 5 21:41:46 gurney mpd: [vpn] LCP: state change Initial --> Starting Feb 5 21:41:46 gurney mpd: [vpn] LCP: LayerStart Feb 5 21:41:46 gurney mpd: [vpn] device: OPEN event in state DOWN Feb 5 21:41:46 gurney mpd: pptp0: connecting to yyy.yyy.yyy.yyy:1723 Feb 5 21:41:46 gurney mpd: [vpn] device is now in state OPENING Feb 5 21:41:46 gurney mpd: pptp0: connected to yyy.yyy.yyy.yyy:1723 Feb 5 21:41:46 gurney mpd: pptp0: attached to connection with yyy.yyy.yyy.yyy:1723 Feb 5 21:41:46 gurney mpd: pptp0-0: outgoing call connected at 14808325 bps Feb 5 21:41:46 gurney mpd: [vpn] PPTP call successful Feb 5 21:41:46 gurney mpd: [vpn] can't attach pptpgre node: Bad file descriptor Feb 5 21:41:46 gurney mpd: pptp0-0: clearing call Feb 5 21:41:46 gurney mpd: [vpn] can't shutdown "bypass.link0": Bad file descriptor Feb 5 21:41:46 gurney mpd: [vpn] device: DOWN event in state OPENING Feb 5 21:41:46 gurney mpd: [vpn] device is now in state DOWN Feb 5 21:41:46 gurney mpd: [vpn] link: DOWN event Feb 5 21:41:46 gurney mpd: [vpn] LCP: Down event Feb 5 21:41:46 gurney mpd: [vpn] device: OPEN event in state DOWN Feb 5 21:41:46 gurney mpd: [vpn] pausing 9 seconds before open Feb 5 21:41:46 gurney mpd: [vpn] device is now in state DOWN Feb 5 21:41:46 gurney mpd: pptp0-0: peer call disconnected res=zero? err=none Feb 5 21:41:46 gurney mpd: pptp0-0: killing channel Feb 5 21:41:46 gurney mpd: pptp0: closing connection with yyy.yyy.yyy.yyy:1723 Feb 5 21:41:46 gurney mpd: pptp0: killing connection with yyy.yyy.yyy.yyy:1723 With the section from "device: OPEN event in state DOWN" repeating until I stop mpd. It seems to be a race or dependancy problem, because the "fix" is to just wait for a couple of seconds after stopping mpd, then start it again, and then it works fine. After doing the manual stop/start sequence, the kernel mutters something like: Jan 30 09:29:03 gurney /kernel: bpf: ng0 attached Hints? Suggestions? -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
