From owner-freebsd-virtualization@FreeBSD.ORG Thu Dec 3 14:16:22 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07864106566C for ; Thu, 3 Dec 2009 14:16:22 +0000 (UTC) (envelope-from jmnwong@gmail.com) Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216]) by mx1.freebsd.org (Postfix) with ESMTP id 77C1C8FC22 for ; Thu, 3 Dec 2009 14:16:21 +0000 (UTC) Received: by ewy8 with SMTP id 8so1537119ewy.35 for ; Thu, 03 Dec 2009 06:16:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=okQA4ej8u4UZJNNQKDv61vMFMBgWFpN8+JaC/GXhh/o=; b=WHcBE5WdowBKGGORaDcKQPfGfI325tDIXBiJ+0Uay3Ub5azOeNVuJBq9yCJ6JjcKwZ KRf9e9/WasqffbP9mVHKRzeLO4nY/9B5X0gI2MtijHTdy7tRz81kQfWnoOTMK30Rwttc 4MJPz/RnkGg7wyyXvvvpsNjRrNPj89ACK1Bnc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JJGSsv1C4aTnldtrsYOWG9lAP8b2kuJnfj7EyRZjtEcXk0MQP0fzto08/JQ0/ZhG69 B9oHmXdymsGxLVZVtzSYN4aKLDLSUJ1hiRBYypB4knCrO1QoxtlFguJgyXTGZ0UAcYKS KC/jS4ZkYii6zyk/OKtdOHmv8dxllumBNKxKg= MIME-Version: 1.0 Received: by 10.213.57.19 with SMTP id a19mr3017524ebh.11.1259849779839; Thu, 03 Dec 2009 06:16:19 -0800 (PST) In-Reply-To: <20091202224841.O83957@maildrop.int.zabbadoz.net> References: <66313f8d0912020817x5839715ake916804d61dea730@mail.gmail.com> <20091202224841.O83957@maildrop.int.zabbadoz.net> Date: Thu, 3 Dec 2009 09:16:19 -0500 Message-ID: <66313f8d0912030616h691b149ay64dac79214336c45@mail.gmail.com> From: Justin Wong To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD virtualization mailing list Subject: Re: ppp in vimages? X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2009 14:16:22 -0000 > > I am having trouble getting ppp to work within vimages. Without vimages, >> my >> box is able to connect (via vr0 interface) and assign it to tun0. With >> > > > Which version of FreeBSD are you using? FreeBSD 8.0 RC3. I upgraded it after experiencing some kernel panics with 7.1 (Thanks for the tip Julian!). Seems to be working well so far. > vimages, I assign vr0 to it (continuing with the name vr0 instead of eth0) >> and ppp cannot detect it therefore I am unable to request for an IP. I am >> wondering whether this is a limitation on vimages/jails running ppp. >> >> Here is the error I am receiving: >> >> Dec 1 09:24:53 n2 ppp[1481]: tun0: Warning: deflink: PPPoE: unknown host >> Dec 1 09:24:53 n2 ppp[1481]: tun0: Warning: deflink: PPPoE: unknown host >> Dec 1 09:24:53 n2 ppp[1481]: tun0: Warning: deflink: Device (PPPoE:vr0) >> must bee >> gin with a '/', a '!' or contain at least one ':' >> > > This sounds more like if you had some special charater in the config > file somewhere? My ppp.conf has the line "set device PPPoE:vr0". So I do not believe I am putting in any extra characters. Adding the '/', '!', or ':' doesn't seem to work either. vr0 is just the name of my interface. > > Dec 1 09:24:53 n2 ppp[1481]: tun0: Phase: deflink: Enter pause (0) for >> redialinn >> g. >> > > >> Here is my ppp.conf: >> > > which I just started inside a vimage (with a different interface name) > and it started just fine in -foreground, even though I don't have a > single netgraph module loaded (in base system). Interesting. Perhaps there is a conflict with netgraph. > I also attempted to assign tun0 to a vimage, but it seems to lose its IP. >> > > What you would do if you have ppp running in base and want the data > inside a vimage is to use a bridge. If you move an interface between > network stacks basically all upper layer configuration is reset and > initialized as if the interface was just created. > Ah, I overlooked that. So the result in that case is correct. I've also attempted to use mpd with no luck. It seems mpd specifically calls command '/sbin/ifconfig' and checks for vr0 and it does not find it. This is likely because it is looking in the base image instead of within my vimage.