Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Nov 2011 23:27:13 +0100
From:      =?ISO-8859-1?Q?Erik_N=F8rgaard?= <norgaard@locolomo.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: No network in mixed FBSD81/90 chroot environment
Message-ID:  <4ED55C41.8010907@locolomo.org>
In-Reply-To: <4ED4F30C.3080302@my.gd>
References:  <4ED4D533.6020103@locolomo.org> <4ED4D6DA.9020604@locolomo.org> <4ED4F30C.3080302@my.gd>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 29/11/2011 15:58, Damien Fleuriot wrote:

> On 11/29/11 1:58 PM, Erik Nørgaard wrote:
>>> Today I finished make build/install world/kernel in /mnt, and now I no
>>> longer have network access, interfaces are visible with ifconfig but
>>> no ip is set and can't be set from within the chroot environment.
>>>
>>> Is this to be expected? How do I get my network access back?
>> Should add: Network on the host FBSD81 system works fine.
>
> When you chroot to your /mnt/ folder you're still using the 8.x kernel
> and thus the 8.x NIC drivers, with a 9.x userland.
>
> This might be your problem.

That seems strange though, first, drivers are loaded into the kernel so 
there is no mismatch there, 8.1 drivers in 8.1 kernel. And then, this is 
the output from ifconfig, first the chroot environment, then the host 
environment:

FreeBSD chroot # ifconfig
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
mtu 1500 
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
	ether e0:69:95:77:f1:20
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33200
FreeBSD chroot # exit

alpha# ifconfig
re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
mtu 1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
	ether e0:69:95:77:f1:20
	inet 192.168.0.1 netmask 0xfffffe00 broadcast 192.168.1.255
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
	inet6 ::1 prefixlen 128
	inet 127.0.0.1 netmask 0xff000000
	nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33200

So, the devices are there, just no network connectivity.

> What are you trying to achieve with this, a smooth 8.x ->  9.x transition ?

Well, I don't know what happened on the host system, but the kernel 
fails building, even kernel 8.2, at if_vlan. Since I decided to migrate 
to the other disk and upgrade to 9.0 I created a chrooted environment on 
the new disk and build sources there.

Now, the tricky part is that this is a headless system and I need it to 
be up or at least be sure that I can roll back if something fails.

> You may want to, instead, install your 9.0 on a different machine
> (possibly a VM), then use dump on the filesystems to inject them
> properly on your new disk on the original machine.
>
> You should then be able to reboot on the new disk just fine.

Thanks, for the suggestion, but sounds risky, the disks are not 
identical size.

It seems I have a workaround that will get my new disk ready: Using 
fetch-recursive I've downloaded the sources of the ports I need 
installed, so I can build in the chroot without network access.

BR, Erik

-- 
M: +34 666 334 818
T: +34 915 211 157



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4ED55C41.8010907>