The /etc/rc.d/jail script contains the on-the-fly conversion from the
legacy rc.conf method statements to jail.conf file formate.
The jail.conf was added in freebsd 9.0 and its now time to remove the
deprecated support for the old definition method.
I think you are all barking up the wrong tree
The default OS comes with only ONE fib.
You need to re-compile the kernel with "option ROUTETABLES=2"
or use the net.fibs=2 option in /boot/loader.config file.
0= default host routing table
1= first additional routing table
2= second additional
Ronald Klop wrote:
Hi,
After stopping a jail I get a crashdump.
core.txt:
https://www.klop.ws/core_2eef39c581f90f2f0c4921e43f1998c1/core.txt.0
Jail.conf:
--
exec.stop = "/bin/sh /etc/rc.shutdown";
exec.clean;
exec.prestart = "ifconfig bridge0 > /dev/null 2> /dev/null || ( ifconfig
Know if_bridge is being worked on to make its performance faster.
Has this new if_bridge been merged into 13.0 current head or stable 12.2?
If so I would like to give it a test ride by installing last weeks
snapshot.
___
freebsd-current@freebsd.org
Gary Jennejohn wrote:
On Thu, 9 Jul 2020 10:27:02 +0800
Marcelo Araujo wrote:
Em qui., 9 de jul. de 2020 __s 07:34, Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> escreveu:
In /etc/defaults/rc.conf I see this
ipv6_ipfilter_rules="/etc/ipf6.rules"
# rules definition file for ipfilter,
#
Gary Jennejohn wrote:
On Thu, 9 Jul 2020 10:27:02 +0800
Marcelo Araujo wrote:
Em qui., 9 de jul. de 2020 __s 07:34, Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> escreveu:
In /etc/defaults/rc.conf I see this
ipv6_ipfilter_rules="/etc/ipf6.rules"
# rules definition file for ipfilter,
#
In /etc/defaults/rc.conf I see this
ipv6_ipfilter_rules="/etc/ipf6.rules"
# rules definition file for ipfilter,
# see /usr/src/contrib/ipfilter/rules for examples
man 8 ipf says
ipf -6 ipv4 and ipv6 rules are stored in a single table and can be read
from a single file. This option is no
BulkMailForRudy wrote:
I love using jails. For many years, I used a tool to help out: ezjail,
now I am just raw-dogging it by using the config file in /etc/jail.conf
Here is my config:
# /etc/jail.conf
# VNET is used to send an epair to each jail.
# The epair is renamed jail0 with
Have gateway host, (ie; host that is connected directly to the public
internet.) running a vnet jail that has pf firewall running inside of
it. When I start the vnet jail I see a few dhclient tasks auto start for
vge0 which is the interface added as member to the bridge. I take this
to mean
ftp.freebsd.org/pub/FreeBSD/releases/amd/amd/12.0-BETA3/base.txz
/usr/local empty
/var/log empty
This is really making testing imposable!
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Issuing the kldstat -v command no longer shows the vimage name. Has it
be renamed to something different?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Hello lists:
With 12.0, vimage is now included with the system base kernel and the
pfctl program has been worked on so it will function in a vnet jail.
While 12.0 is still in the beta releases i am trying to test this new
environment. All ready found bug dealing with ipfilter running on host
Running pf on host and in vnet jail. In the vnet jail rc.conf have
normal parameters to start pf and the log. On vnet jail start up the
vnet jail log specified in the jail(8) jail.conf file gets this error
message.
Startling pflog.
Enabling pfpfctl: /dev/pf: No such file or directory
pfctl:
Bjoern A. Zeeb wrote:
On 28 Oct 2018, at 15:31, Ernie Luzar wrote:
Tested with host running ipfilter and vnet running pf. Tried loading
pf from host console or from vnet console using kldload pf.ko command
and get this error message;
linker_load_file: /boot/kernel/pf.ko-unsupported file
Tested with host running ipfilter and vnet running pf. Tried loading pf
from host console or from vnet console using kldload pf.ko command and
get this error message;
linker_load_file: /boot/kernel/pf.ko-unsupported file type.
Looks like the 12.0 version of pf which is suppose to work in vnet
blanktime, screensaver has no effect on vt console.
splash screen has no effect on vt console.
no messages of any kind issued.
They all work on sc console.
___
freebsd-current@freebsd.org mailing list
Wanting to get a head start on using 12.0 and vnet jails with in jail
firewall.
1. Will Vimage be compiled as a module in the 12.0 kernel and be
included in the base system release?
1.a. Has the boot time console log message about vimage being "highly
experimental" been removed?
2. Has
YongHyeon PYUN wrote:
On Thu, Nov 02, 2017 at 10:13:15AM -0400, Ernie Luzar wrote:
Posted this 10/31/2017 got no reply.
Been getting these error messages since about release 10.0 I think.
Have changed to new hardware box and new cable modem and still having
the same error messages. Also
Posted this 10/31/2017 got no reply.
Been getting these error messages since about release 10.0 I think.
Have changed to new hardware box and new cable modem and still having
the same error messages. Also occurs when I use em0 interface to connect
to the public internet instead of vge0.
Chuck Swiger wrote:
On Apr 14, 2017, at 6:47 AM, Ernie Luzar <luzar...@gmail.com> wrote:
To aid in debugging the script I'm writing, I place "echo" commands throughout so I can
kind of have a trace of the logic as different conditions are processed. Normally I just del
To aid in debugging the script I'm writing, I place "echo" commands
throughout so I can kind of have a trace of the logic as different
conditions are processed. Normally I just delete these "echo" commands
after I get the script working.
But this time I want to try something different. I want
peter.b...@bsd4all.org wrote:
Well, in my case it panic’ed on 11-stable. I’m only using pf on the
host, not in the jail. I’m using Devin Teske’s jng to create a netgraph
bridge. It is my intention to use the netgrpah bridge with bhyve as well.
I also tested using Devin Teske’s jng to
scall+0xfb
The panic is so far not reproducible.
On 10 Apr 2017, at 15:50, Ernie Luzar <luzar...@gmail.com
<mailto:luzar...@gmail.com>> wrote:
peter.b...@bsd4all.org <mailto:peter.b...@bsd4all.org> wrote:
There have been issues with pf if I recall correctly. I currently
have issues wi
To the VNET (VIMAGE) update project team members
Release 11.0 has some out standing VNET (VIMAGE) PR's that need addressing.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212013
peter.b...@bsd4all.org wrote:
There have been issues with pf if I recall correctly. I currently have issues
with stable, pf and vnet. There is an issue with pf table entries when an
interface is moved to a different vnet.
Does anyone no if there is a specific fix for this that hasn’t been
Cy Schubert wrote:
In message <58e50379.6090...@gmail.com>, Ernie Luzar writes:
I have been a ipfilter user since Freebsd 3.0 without any complaints.
Now I'm trying to get ippool to function. I have been able to add a
pool, but now I want to refresh it's contents. From what I read in &
I have been a ipfilter user since Freebsd 3.0 without any complaints.
Now I'm trying to get ippool to function. I have been able to add a
pool, but now I want to refresh it's contents. From what I read in "man
8 ippool", I have to remove the pool from core and then re-add it with
the complete
Is anyone working the these outstanding vt(4) bug reports?
Bug 210431 - vt(4) copy/paste mode does not work in hw.vga.textmode=1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210431
Bug 210432 - vt(4) does not support boot time splash screen
You can add these things to the vt to-do list
Change the default font to look like sc.
Add copy/paste function like sc has.
Add splash screen support like sc has.
Adrian Chadd wrote:
hi,
no, the vt_vga backend doesn't yet do VESA.
I keep meaning to sit down and fix this, but life and wifi
Alan Somers wrote:
I've seen three separate machines where FreeBSD11's vt(4) driver chops
off the leftmost three columns of the screen. Rendering simply starts
at the beginning of the fourth column. In all cases, setting
"kern.vty=sc" corrects the problem. The three different systems are:
1)
O. Hartmann wrote:
Hello list.
I struggle with setting up jails on most recent CURRENT.
The machine containing the jails has two NICs (bce0 and bce1). the host itself
is supposed to own NIC bce0 exclusively - means, the services running on that
NIC - syslogd, named and others - are bound to
Hartmann, O. wrote:
I ran into a very nasty and time consuming problem. Creating a NanoBSD
image with a modified script framework creating GPT partitions, I put
the imaes via "dd(1)" on USB flash or SD flash. Because the images are
usually much smaller than the overall capacity of the USB or SD,
Glen Barber wrote:
On Mon, Jul 11, 2016 at 03:32:34PM -0600, Alan Somers wrote:
On Mon, Jul 11, 2016 at 2:01 PM, Ronald Klop wrote:
Hi,
Just downloaded the amd64 BETA1 ISO (873MB) and tried to burn a CD on
Windows 10. It complained that the ISO is too big for my 700 MB
Kurt Jaeger wrote:
Hi!
If you want textmode like in the old days, add this line to
/boot/loader.conf:
hw.vga.textmode="1"
If I do this on a laptop 10.3p5, sending the laptop to sleep with
zzz causes a crash (!), which is reproducable.
submit a PR
John Baldwin wrote:
On Monday, June 20, 2016 04:54:11 PM Ernie Luzar wrote:
Ed Maste wrote:
On 20 June 2016 at 14:29, Ernie Luzar <luzar...@gmail.com> wrote:
I found the cause of this boot time message
"vicontrol: setting cursor type: Inappropriate ioctl for device"
In
Ed Maste wrote:
On 20 June 2016 at 14:29, Ernie Luzar <luzar...@gmail.com> wrote:
I found the cause of this boot time message
"vicontrol: setting cursor type: Inappropriate ioctl for device"
In my rc.conf I had this statement
vidcontrol -c blink -h 250
From testing it se
Trond Endrestøl wrote:
On Mon, 20 Jun 2016 11:36-0400, Ernie Luzar wrote:
I have installed 11.0-ALPHA4-i386-20160617-r301975.
The console looks very different from all previous releases.
I find it to be harder to read. This manifests it self with the boot log
messages and the normal behavior
Hello list;
I have installed 11.0-ALPHA4-i386-20160617-r301975 to test VIMAGE.
I have read previous list posts saying vimage was going to be part of
the base system in 11.0. When I configure a jail with vnet I get a
error typical of vimage not being compiled into the kernel.
To me it looks
I have installed 11.0-ALPHA4-i386-20160617-r301975.
The console looks very different from all previous releases.
I find it to be harder to read. This manifests it self with the boot log
messages and the normal behavior of the virtual consoles.
But the real problem is in the notable hesitation
As long as packaged base is not mandatory, it is fine by me.
+1 on that
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
wrote:
On 04/18/16 10:00, Ernie Luzar wrote:
11.0 will have pkg base, thats ok, but what does than mean for the
base.txz file?
It it going to stay as part of FBSD install?
I have many scripts for creating jails which depend on the base.txz file.
It's even easier now:
# mkdir -p /usr/jails/new
11.0 will have pkg base, thats ok, but what does than mean for the
base.txz file?
It it going to stay as part of FBSD install?
I have many scripts for creating jails which depend on the base.txz file.
___
freebsd-current@freebsd.org mailing list
Glen Barber wrote:
As many are aware, one of the major user-facing changes to FreeBSD in
11.0-RELEASE is packaging the base system with pkg(8). Originally, the
11.0-RELEASE code slush was scheduled to start on April 22, 2016, which
is only a week away at this point.
With the packaged base
Bjoern A. Zeeb wrote:
On 24 Aug 2015, at 19:08 , Mark Felder wrote:
What is preventing RCTL from being enabled right now? Any known/serious
blockers?
It’s enabled in GENERIC.
And the same for VIMAGE? I know there were issues with some firewalls,
but I'm not sure where
44 matches
Mail list logo