[Bug 195859] Reproduceble panic with VIMAGE + if_bridge

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859

Craig Rodrigues  changed:

   What|Removed |Added

   Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
 CC||h...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 195859] Reproduceble panic with VIMAGE + if_bridge

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859

--- Comment #6 from Craig Rodrigues  ---
Herbert found by creating VNET jails and then stopping them, he could reproduce
the problem.  Here are the steps he used to reproduce the problem:

/etc/rc.conf:

hostname="beastie.home.lan"
ifconfig_em0="inet 192.168.1.25 netmask 0x"
defaultrouter="192.168.1.255"
cloned_interfaces="bridge0"
ifconfig_bridge0="inet 10.0.0.1 netmask 0xff00"
sshd_enable="YES"
fsck_y_enable="YES"
background_fsck="NO"
syslogd_flags="-ss"
gateway_enable="YES"
pf_enable="NO"
pflog_enable="NO"
jail_enable="NO"
jail_list="jail01 jail02 jail03 jail04"
devfs_load_rulesets="YES"

/etc/jail.conf:

jail01 {
 name = "jail01";
 path = /usr/local/jails/jail01;
 mount.devfs;
 host.hostname = jail01.home.lan;
 vnet = "new";
 vnet.interface = "epair0b";
 persist;
 exec.prestart = "ifconfig epair0 create";
 exec.prestart += "ifconfig bridge0 addm epair0a";
 exec.prestart += "ifconfig epair0a up";

 exec.start = "";
 #exec.start = "/bin/sh /etc/rc";

 exec.poststart ="jexec $name ifconfig epair0b 10.0.0.10 netmask
255.0.0.0 up";
 exec.poststart +=   "jexec $name route add default 10.0.0.1";
 exec.poststart +=   "jexec $name sh /etc/rc";

 exec.stop = "/bin/sh /etc/rc.shutdown";

 exec.poststop = "ifconfig bridge0 deletem epair0a";
 exec.poststop +="ifconfig epair0a destroy";
}

/etc/rc.conf in jail01:

hostname="jail01.home.lan"
sshd_enable="YES"
sendmail_enable="NONE"

Starting jail with "/etc/rc.d/jail onestart jail01" or "jail -c jail01".
Stopping jail with "/etc/rc.d/jail onestop jail01" or "jail -r jail01".

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 195859] Reproduceble panic with VIMAGE + if_bridge

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859

--- Comment #7 from Craig Rodrigues  ---
Created attachment 151803
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151803&action=edit
dump2.txt

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 195859] Reproduceble panic with VIMAGE + if_bridge

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859

--- Comment #8 from Craig Rodrigues  ---
Herbert provided a traceback from his kernel panic.  This looks like the source
of the problem:

panic: mtx_lock() of destroyed mutex @
/usr/src/sys/modules/if_bridge/../../net/if_bridge.c:1814

It looks like after destroying a jail, a mutex is destroyed, but this
destroyed mutex is used later on in another jail.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 194515] Fatal Trap 12 Kernel with vimage

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515

--- Comment #18 from dar...@dons.net.au ---
Is this going to be MFCd?
The 3 commits apply cleanly to stable/10 and seem to work (but I have only
tested it lightly so far)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Kickstarter Invitation

[Emma Turing]

Hi, I'd like to invite you to back our Kickstarter project - The World's
First Personal Robot
.  

 We're already 210% funded and the #1 Robot Project on Kickstarter now.

 PERSONAL ROBOT IS THE WHOLE PACKAGE: 

   - The world's first personal assistant robot that can see, hear, smell,
move, and feel
  - The smartest home automation system (supports both Z-Wave and Zigbee)
  -  A photographer, storyteller, companion, security guard, and more
  - Powered by Artificial Intelligence algorithms
  - Open APIs
 
  We're been featured by TechCrunch, Mashable, and VentureBeat.

 Thanks,
 Emma

  

 


 
 
 *If you're not interested, please simply reply "don't email" and we'll
stop emailing you immediately.*
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: dragonflybsd's ipfw

[Sato Kentney]

Hi,
I get below from another email this morning, the ipfw can add dynamic rules
according to below email.

*You can manually insert a state as below and the state will be maintain by
ipfw itself.*
*ipfw state add rulenum 100 udp 192.168.1.1:0
 8.8.8.8:53  expiry +600*
*so you dont need to implement the logic to maintain the IP addresses or
configure any crontab to remove..*
*different state can have different expiry or "life time"*

ありがとう
佐藤柯德

2014-11-17 17:07 GMT+08:00 Ian Smith :

> On Mon, 17 Nov 2014 15:48:13 +0800, Sato Kentney wrote:
>
>  > I saw a email in dragonflybsd email list, someone is doing this!
>  > http://www.dragonflybsd.org/docs/ipfw2/
>
> We've had 'ipfw2' for a very long while.  I couldn't help wondering why
> DF wouldn't just import our many years of development and experience
> rather than using bycn82's 'rewrite'? .. but DF already has ipfw2:
>
> http://leaf.dragonflybsd.org/cgi/web-man?command=ipfw§ion=ANY
>
> man page dated October 2008.  Before tables, in-kernel NAT, later
> dummynet updates and no doubt more.  So why not start from there?
>
> cheers, Ian
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"