http://blog.gmane.org/gmane.os.freebsd.jail hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.os.freebsd.jail/2257 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/178302 jail jail(8): unknown parameter: ip6.addr when kernel compi o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -</pre> FreeBSD bugmaster 2013-05-20T11:06:48 http://comments.gmane.org/gmane.os.freebsd.jail/2251 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/178302 jail jail(8): unknown parameter: ip6.addr when kernel compi o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -</pre> FreeBSD bugmaster 2013-05-13T11:06:46 http://comments.gmane.org/gmane.os.freebsd.jail/2246 <pre>Thank you for your message. I am currently out of the office. I will answer to your request as soon as I'll be back on Monday the 13th of May 2013. For any urgent matter, please contact Zelda Lehmann zelda.lehmann-Wd1/L3XMp9xg9hUCZPvPmw&lt; at &gt;public.gmane.org </pre> Patricia Casal 2013-05-08T18:00:26 http://comments.gmane.org/gmane.os.freebsd.jail/2245 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/178302 jail jail(8): unknown parameter: ip6.addr when kernel compi o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -</pre> FreeBSD bugmaster 2013-05-06T11:06:47 http://comments.gmane.org/gmane.os.freebsd.jail/2229 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -alias and k o kern/159918 jail [jail] inter-jail communication failure o k</pre> FreeBSD bugmaster 2013-04-29T11:06:46 http://comments.gmane.org/gmane.os.freebsd.jail/2203 <pre>Hello I am having a very difficult time getting pf firewall to start in a vimage jail on 9.1-RELEASE. Is this at all possible? If this can be done, would you please share the details on how it's done? Thanks </pre> Joe 2013-04-24T17:13:56 http://comments.gmane.org/gmane.os.freebsd.jail/2197 <pre>Hello list I am using jail(8) trying to get a functional vimage environment on my 9.1-RELEASE system. My PC only has a single real NIC facing the public internet. My goal is to be able to have multiple vimage jails, each with their own epairXa epairXb and bridgeX where the "X" is the jails JID number all having their traffic passing through the single rl0 real interface. The vnet.start script shown below handles this nicely. The problem is after the first vimage jail is started the rl0 interface gets marked as busy when the second vimage jail is started. How do I get all vnet jails to pass through the real rl0 interface? Thanks for you help # /root &gt;cat /etc/jail.conf vimage33 { host.hostname = "vimage33"; path = "/usr/jails/vimage33"; mount.fstab = "/usr/local/etc/fstab/vimage33"; exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.consolelog = "/var/log/vimage33.console.log"; devfs_ruleset = </pre> Joe 2013-04-23T13:14:23 http://comments.gmane.org/gmane.os.freebsd.jail/2192 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -alias and k o kern/159918 jail [jail] inter-jail communication failure o k</pre> FreeBSD bugmaster 2013-04-22T11:06:46 http://comments.gmane.org/gmane.os.freebsd.jail/2191 <pre>Hello, This is something that imho could be done by GSoC student. It is possible to allow jailed root to mount various filesystems. But once all processes are dead, mounts done by jailed root that he didn't clean up are still hanging around. As time passes and more stuff gets jailable we should expect problems like this in different subsystems. So I propose that someone(tm) implements a solution which cleans this stuff during jail destruction. One idea how to do it: implement a list with clean up operations. Using mount example: you add a filesystem to be cleaned up after it is mounted, you delete it after it is unmounted. When the jail is going to die you just traverse the list backwareds and call cleaning functions, in this case unmounting filesystems. Maybe this is is a bad idea in the first place and it is better to take a look at mount tree and traverse that, I don't know, you should investigate. :) Note that the code has to be robust in case of errors (e.g. given fs may not be unmountable because </pre> Mateusz Guzik 2013-04-22T09:17:11 http://comments.gmane.org/gmane.os.freebsd.jail/2184 <pre>Hello, If a 9-STABLE amd64 host compiled with VIMAGE support contains a jail running i386 code with a vnet interface, how does one set the default route inside the jail? Ifconfig and the network work fine, but route returns: # route add default 192.168.0.1 route: writing to routing socket: Invalid argument add net default: gateway 192.168.0.1: Invalid argument The behavior appears the same whether the jail is running 8.3-i386 or 9.1-i386. Based on this: http://lists.freebsd.org/pipermail/freebsd-amd64/2011-October/014050.html It looks like this there was a host-side patch for this in the 8.2 timeframe, but I compared the patch to the 9-STABLE source for sys/net/rtsock.c and it's not there. As that's from two years ago, there's probably a reason it didn't make it in, so does anyone know what is the right way to manage routes in VIMAGE jails? Thanks for any advice! </pre> J David 2013-04-16T20:28:59 http://comments.gmane.org/gmane.os.freebsd.jail/2183 <pre>I am running 8.2 , I am hitting a panic after I create a vnet jail an try to remove it. jail -c name=j1 children.max=20 host.hostname=j1 jid=100 vnet persist allow.raw_sockets jail -r j1 calltrap() at calltrap+0x8 --- trap 0x9, rip = 0xffffffff80518f4d, rsp = 0xffffff805fa1d9e0, rbp = 0xffffff805fa1da30 --- raw_input() at raw_input+0x4d rts_input() at rts_input+0x70 netisr_process_workstream_proto() at netisr_process_workstream_proto+0x1ea swi_net() at swi_net+0xad intr_event_execute_handlers() at intr_event_execute_handlers+0x21c ithread_execute_handlers() at ithread_execute_handlers+0x73 ithread_loop() at ithread_loop+0x10f fork_exit() at fork_exit+0x180 fork_trampoline() at fork_trampoline+0xe The issue seems to be that in if_detach_internal(), if_down() is called which leads to netisr_queue() call in rt_dispatch() with an mbuf which has the interface being detached as rcvif, subsequently if_detach_internal() calls if_dead() on the interface. And, then at time of processing the work, this panic is seen</pre> suraj sandhu 2013-04-16T16:49:27 http://comments.gmane.org/gmane.os.freebsd.jail/2182 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -alias and k o kern/159918 jail [jail] inter-jail communication failure o k</pre> FreeBSD bugmaster 2013-04-15T11:06:45 http://comments.gmane.org/gmane.os.freebsd.jail/2173 <pre>Dear jail hackers, in my ongoing quest to understand the direction jail development is heading, I noticed that per-jail-fstabs are not (anymore?, yet?) supported by the new jail(8)-rc.d/jail2-combo. Are there official plans to drop the support? A nice new jail+zfs feature is the "zfs jail" command, allowing to attach a zfs to a jail. The way[tm] to properly use this feature is to first create a prison, attach the zfs file system(s) to the jid and only then run the exec.start command. So either jail(8) needs to be zfs aware and execute the zfs jail command(s) by itself, or a exec.postprestart command that is being passed the prison id of the new jail needs to be run in system context. (For shutting down and unjail-ing vice versa). The same goes with the vimage features. Most of the ways I can think of using vnet interfaces require some configuration in the host system after the vnet has been attached to the jid but before exec.start (and thus the jail's rc.d/netif) is executed. Since I speak C, posix and </pre> Dirk Engling 2013-04-11T18:48:07 http://comments.gmane.org/gmane.os.freebsd.jail/2170 <pre>Hi, I am using vnet on a jail, but when trying to acquire an IP via DHCP i get the following message: Can't find free bpf: No such file or directory any ideas of how to make the jail obtain an IP via DHCP when using vent ? regards. </pre> Nicolas de Bari Embriz Garcia Rojas 2013-04-09T00:45:07 http://comments.gmane.org/gmane.os.freebsd.jail/2169 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -alias and k o kern/159918 jail [jail] inter-jail communication failure o k</pre> FreeBSD bugmaster 2013-04-08T11:06:47 http://comments.gmane.org/gmane.os.freebsd.jail/2167 <pre> Hi. Since I setuped Jail for www stuff in server there are network problems. Router has 3 NIC's in bridge with aliases. cloned_interfaces="bridge0" ifconfig_bridge0="addm rl1 addm rl2 addm rl3 up" ifconfig_rl1="up -wol" ifconfig_rl2="up -wol" ifconfig_rl3="up -wol" ifconfig_bridge0_alias0="inet 10.11.1.1 netmask 255.255.255.0" ifconfig_bridge0_alias1="inet 10.12.1.1 netmask 255.255.255.0" ifconfig_bridge0_alias2="inet 10.13.1.1 netmask 255.255.255.0" ifconfig_bridge0_alias3="inet 10.14.1.1 netmask 255.255.255.192" ifconfig_bridge0_alias4="inet 10.15.1.1 netmask 255.255.255.0" Also I use PF for filtering traffic. There are a lot of rules. In two words: it is unable to reach any host in LAN and also any IP addresses on router, allowed access to Internet only. In other words Jail in original DMZ zone with IP 10.15.1.1. In random time (about one incident per-(2|3)days) the strange situations is occur: I am unable to ping/ftp/http from jail or from LAN any host in Internet. From/to router - it's ok. Restart</pre> wishmaster 2013-04-06T20:34:33 http://comments.gmane.org/gmane.os.freebsd.jail/2164 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/167911 jail new jail(8) problem with removal, ifconfg -alias and k o kern/159918 jail [jail] inter-jail communication failure o k</pre> FreeBSD bugmaster 2013-04-01T11:06:45 http://comments.gmane.org/gmane.os.freebsd.jail/2142 <pre>Dear jail hackers, if I follow the development correctly, the jail(8) command was augmented to make the rc.d/jail script obsolete. However when I want to use the rc system to start my jails, I am stuck with convincing rc.d/jail to not fail for missing _hostname or _rootdir. How am I supposed to have my jails started at boot time? And while we're at it, is there a rcorder-style way to introduce dependencies into jail.conf to control the order my jails are started in? Which brings me to another point, there does not seem to be a way to convince rc.d/jail to set a jailname for old style jails, making it hard to integrate with tools that use libjail to translate what were _hostname parameters to jid before. On a related note, in order to finally include all the nextgen jail features in my ezjail project, I wonder if there's an automated tool to read/write/modify jail.conf(s) on the radar. Currently I am considering keeping my own set of configs and generating a jail.conf per jail on the fly, which I do not t</pre> Dirk Engling 2013-03-30T17:33:44 http://comments.gmane.org/gmane.os.freebsd.jail/2141 <pre> You sent an email to the Exchange list with an attachment. We have disabled this option as recently a virus was attached. Please resend your posting without it? Thanks! </pre> Lyris ListManager 2013-03-29T10:45:09 http://comments.gmane.org/gmane.os.freebsd.jail/2136 <pre>Hi all, what tool can help me to (emulate) PF or a firewall behavior within a jail that it is using VIMAGE ? regards </pre> Nicolas de Bari Embriz Garcia Rojas 2013-03-28T15:05:23 http://comments.gmane.org/gmane.os.freebsd.jail/2130 <pre>Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/177325 jail [jail] Jail umounts fstab in the wrong order o kern/176482 jail [jail] Jails not unmounting devfs on exit o kern/176112 jail [jail] [panic] kernel panic when starting jails o kern/176092 jail [jail] [panic] Starting a jail on my releng/9.1 kernel o kern/174902 jail [jail] jail should provide validator for jail names o kern/174436 jail [jail] Jails with numbers as names don't work o bin/173469 jail [jail] regression: security.jail.sysvipc_allowed=1 no o kern/169751 jail [jail] reading routing information does not work in ja o bin/16791</pre> FreeBSD bugmaster 2013-03-25T11:06:45 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.freebsd.jail