Date: Thu, 2 Oct 2014 22:44:30 +0800 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Warren Block <wblock@wonkity.com> Cc: freebsd-jail@freebsd.org, freebsd-stable@freebsd.org Subject: Re: no network connection from inside a jail Message-ID: <20141002224430.7a4cb3f3@X220.alogt.com> In-Reply-To: <alpine.BSF.2.11.1410020809320.50835@wonkity.com> References: <20141002180506.4965760b@X220.alogt.com> <alpine.BSF.2.11.1410020809320.50835@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
On Thu, 2 Oct 2014 08:10:16 -0600 (MDT)
Warren Block <wblock@wonkity.com> wrote:
> On Thu, 2 Oct 2014, Erich Dollansky wrote:
>
> > Hi,
> >
> > I recently upgraded to 10.1 BETA3 via sources. All seemed to be fine
> > until I started jails which connect to the Internet. It simply does
> > not work anymore. When the browser from the jail connects to
> > another jail on the same machine via HTTP, it all works. Accesses
> > to the ouside of the machine fails.
> >
> > Even a ping to a local device does not work.
> >
> > ping 192.168.yyy.xxx
> > ping: socket: Operation not permitted
> >
> > despite having
> >
> > security.jail.allow_raw_sockets: 1
> >
> > Just to make sure, I upgraded also the world in all jails without
> > any difference.
> >
> > UPDATING did not mention any changes since BETA1.
> >
> > I feel a bit lost now.
> >
> > What could have caused the problems?
>
> Does the jail have more than one Ethernet interface?
not really. Lagg is used to switch between wireless and wire:
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether f0:de:f1:cd:10:3a media: Ethernet autoselect
status: no carrier
iwn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
2290 ether f0:de:f1:cd:10:3a
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
status: associated
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500 ether f0:de:f1:cd:10:3a
inet 192.168.0.18 netmask 0xffffffff broadcast 192.168.0.18
media: Ethernet autoselect
status: active
laggproto failover lagghash l2,l3,l4
laggport: wlan0 flags=4<ACTIVE>
laggport: em0 flags=1<MASTER>
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500 ether f0:de:f1:cd:10:3a
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid xxxxxx channel 1 (2412 MHz 11g ht/40+) bssid
90:61:0c:13:36:fe country US authmode WPA2/802.11i privacy ON deftxkey
UNDEF AES-CCM 2:128-bit txpower 14 bmiss 10 scanvalid 60 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64
protmode CTS ampdulimit 32k ampdudensity 16 -amsdutx amsdurx shortgi wme
roaming MANUAL
The address 192.168.0.18 is also not reachable from outside.
Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141002224430.7a4cb3f3>