Hi all,
Recently I upgraded to 8.2-STABLE and reconfigured natd + jailed box, but
all packets could not over nat box. I've researched and found
/etc/rc.firewall does not recieve argument of firewall_type. So ipfw does
not divert and natd could not be performed. The reason is /etc/rc.d/ipfw
incorrec
At Wed, 4 May 2011 03:47:02 +1000 (EST),
Ian Smith wrote:
>
> On Wed, 4 May 2011, KIRIYAMA Kazuhiko wrote:
> > Hi all,
> > Recently I upgraded to 8.2-STABLE and reconfigured natd + jailed box, but
> > all packets could not over nat box. I've researched and found
&
At Wed, 04 May 2011 10:40:12 +0900,
My wrote:
>
> At Wed, 4 May 2011 03:47:02 +1000 (EST),
> Ian Smith wrote:
> >
> > > +++ /etc/rc.d/ipfw 2011-05-03 22:08:14.0 +0900
> > > @@ -35,15 +35,11 @@
> > >
> > > ipfw_start()
> > > {
> > > -local _firewall_type
> > > -
Dear stable list,
I've created private network by Vimage Jail using ezjail referenced [1] as
follows:
em0 X.X.X.X bridge0 192.168.1.254 --+-- epair0a --+-- epair0b 192.168.1.1(ns)
|
+-- epair1a --+-- epair1b 192.168.1.2(ns1)
Hi,
At Sat, 4 May 2013 15:07:11 +0300,
Mikolaj Golub wrote:
>
> On Sat, May 04, 2013 at 02:52:23PM +0900, KIRIYAMA Kazuhiko wrote:
>
> > May 4 11:19:46 xx kernel: Fatal trap 12: page fault while in kernel
> > mode
> > May 4 11:19:46 xx kernel: cpuid = 2; ap
Hi stable list,
Now ipfw_nat's rules must be write directly in firewall_nat_flags. This is
messy to describe many rules. firewall_nat_rules will be treat smartly.
To enable firewall_nat_rules,apply following patch to /etc/rc.firewall
--- /etc/rc.firewall.org2013-05-11 08:23:13.0 +
, it's spec does not changed so far. Is
there any command to display revision number except uname ?
Best regards.
---
KIRIYAMA Kazuhiko
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
On Tue, 20 Aug 2019 13:47:55 +0900,
Trond Endrestøl wrote:
>
> On Tue, 20 Aug 2019 11:00+0900, KIRIYAMA Kazuhiko wrote:
>
> > I've rebuild up to r351108 but `uname -a' can't display it's
> > revision number.
>
> Add this to /etc/src.conf:
>
On Tue, 20 Aug 2019 20:20:30 +0900,
Larry Rosenman wrote:
>
> On 08/20/2019 6:18 am, KIRIYAMA Kazuhiko wrote:
> > On Tue, 20 Aug 2019 13:47:55 +0900,
> > Trond Endrestøl wrote:
> >>
> >> On Tue, 20 Aug 2019 11:00+0900, KIRIYAMA Kazuhiko wrote:
> >>
On Tue, 20 Aug 2019 20:58:26 +0900,
Trond Endrestøl wrote:
>
> [1 ]
> On Tue, 20 Aug 2019 20:18+0900, KIRIYAMA Kazuhiko wrote:
>
> > On Tue, 20 Aug 2019 13:47:55 +0900,
> > Trond Endrestøl wrote:
> > >
> > > On Tue, 20 Aug 2019 11:00+0900, KIRIYAMA K
nfs rw 0 0
vm.tfc:/ds/src/stable/12/r351318/usr/srcnfs ro,nolockd
0 0
vm.tfc:/ds/obj/stable/12/r351318/usr/objnfs rw 0 0
admin@tbedfs:~ %
Thanks for your help!
---
KIRIYAMA
nment - chop wood, draw water.
>
> Marko Cupać
> https://www.mimar.rs/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stab
root@tbedfs:/usr/home/admin # cd /usr/src/
root@tbedfs:/usr/src # make buildworld
To make buildworld in chrooted environment, what should I do ?
Best regards
(*1) Acctually used vm-bhyve port(sysutils/vm-bhyve).
[1] http://ds.truefc.org/~kiri/freebsd/stable/dake.log
[2] ht
13 matches
Mail list logo