After entering the command "ifconfig stf create" - we panic
# kldstat -v | grep stf
On the internal interface are given two networks ipv6 - /64 and /48.
Service works rtadvd.
Wanted to create a service 6to4.
How-To-Repeat: ifconfig stf create
By then it is better to freebsd-net
Over to maintainer(s).
On Friday, January 21, 2011 7:24:08 pm Vladislav V. Prodan wrote:
> >Number: 154214
> >Category: amd64
> >Synopsis: Panic when creating stf interface
> >Confidential: no
> >Severity: serious
> >Priority: high
> >Responsible: freebsd-amd64
> >State: open
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Sat Jan 22 00:30:08 UTC 2011
> >Originator: Vladislav V. Prodan
> >Release: 9.0-CURRENT amd64
> FreeBSD mary-teresa.ZZZ 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sun Aug 29
19:00:25 EEST 2010 vlad11@mary-teresa.ZZZ:/usr/obj/usr/src/sys/mary-
> After entering the command "ifconfig stf create" - we panic
> # kldstat -v | grep stf
> 226 if_stf
> On the internal interface are given two networks ipv6 - /64 and /48.
> Service works rtadvd.
> Wanted to create a service 6to4.
The picture shows a double fault (likely due to infinite recursion on the
stack or some code putting too large of an object onto the stack). Can you
get a backtrace via 'tr' at the db> prompt and reply with the output?
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped
This is likely the same problem as #218895.
As a workaround either don't load pf, or don't create interfaces with names that are also group names (the easiest way to ensure this is to always append a number to the interface names, so stf0 iso. stf).
*** This bug has been marked as a duplicate of bug 218895 ***