[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Missing local interface inside jails with FreeBSD 9.0 after upgrade from FreeBSD 8.2



Hi Dirk,

First of all to big, fat "Thank You" for this terrific piece of
software, which has been rendering my life much easier ever since I
deployed it. I seem to have a little problem since I upgraded from
FreeBSD 8.2 to FreeBSD 9.0: While the alias loopback interface lo1 (in
my case) was recognised and visible from within each and every jail
under FreeBSD 8.2, this does not seem t work any more with FreeBSD 9.0.
In short, Postfix compilation, for instance,  bails out with an error,
as there is no external interface. Strange!!! Have you received any
other, similar reports from FreeBSD 9.0 upgraders/users? Yes, I have
been using the "inet" class designation ever since, even with FreeBSD 8.2.

Here are some snippets:
ifconfig issued from within a jail running under FreeBSD 8.2:

[root@dnsvlan ~]# ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
	ether 00:24:21:ef:33:d1
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet 127.0.1.101 netmask 0xffffffff
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33152

With exactly the same configuration, I get this after an upgrade to
FreeBSD 9.0, done on the host (non-jail) system via freebsd-upgrade,
recompilation of ports used there, then ezjail-admin update -bp,
followed by re-compilation of all ports within the jails, including
reboots as indicated by the FreeBSD 9.0 upgrade release notes:

[root@dnsvlan ~]# ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
	ether 00:e0:4c:0f:98:a6
ifconfig: socket(AF_INET6, SOCK_DGRAM): Protocol not supported
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
ifconfig: socket(AF_INET6, SOCK_DGRAM): Protocol not supported
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
ifconfig: socket(AF_INET6, SOCK_DGRAM): Protocol not supported
lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
ifconfig: socket(AF_INET6, SOCK_DGRAM): Protocol not supported
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33152
ifconfig: socket(AF_INET6, SOCK_DGRAM): Protocol not supported

If you compare the lo1 entries before and after the upgrade, you can
clearly see an assigned I.P. number (127.0.1.101) prior to the upgrade,
but none thereafter. This happens, although the /etc/rc.conf settings in
the host system have not changed a single bit.

Any thoughts? Thanks a lot for your help.
Best regards -

Chris

-- 
Dr. Christoph H. Larsen
synaLinQ (Vietnam)			synaLinQ (Kenya)
P.O. Box 55, Bưu điện NT, 01 Pasteur	P.O. Box 1607, Village Market
Nha Trang, Khánh Hòa			Nairobi 00621
Vietnam					Kenya
Mobile:	+84-98-9607357			Mobile: +254-753-632481
	+49-176-96456254 (Germany)
Fax:    +49-231-292734790
Email:  christoph.larsen AT synalinq DOT com