On 30/03/15(Mon) 17:21, Holger Glaess wrote: > Am 29.03.2015 um 13:54 schrieb Martin Pieuchot: > >On 29/03/15(Sun) 12:56, Holger Glaess wrote: > >>Am 24.03.2015 um 05:41 schrieb Holger Glaess: > >>>hi > >>> > >>>i play a little bit with rdomain > >>> > >>>if add my pppoe device to rdomain 1 > >>> > >>># cat /etc/hostname.pppoe0 > >>>rdomain 1 > >>>rtlabel netcologne > >>>inet6 autoconf > >>>inet 0.0.0.0 255.255.255.255 NONE \ > >>>pppoedev msk0 authproto pap \ > >>>authname 'foo@bar' authkey 'xyz' up > >>>dest 0.0.0.1 > >>>!/sbin/route -T 1 add default -ifp pppoe0 0.0.0.1 > >>>!/sbin/route -T 1 add -inet6 default -ifp pppoe0 ::0.0.0.1 > >>> > >>> > >>> > >>>the pf lines > >>> > >>>pass in on $lan_if from any to $myserver rtable 1 > >>>pass in on rdomain 1 proto tcp from <allow_ssh> to ($nc_pppoe:0) port 22 > >>>rdr-to 192.168.131.250 port 22 rtable 0 > >>>match out on $nc_pppoe nat-to ($nc_pppoe:0) > >>> > >>> > >>> > >>>so , all works fine but if i connect to the system by ssh and do , for > >>>example , an tcpdump -n- r /var/log/pflog > >>>the whole machine crash to an kernel panik. > >>> > >>>this is reproducable and , looks like , just when you have an inbound > >>>connection ( rdr ) . > >>[...] > >>some news for me ? > >We can't give you any news because the panic information you sent are > >useless. Generally when a panic happen you see the message below: > > > >RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! > > > >If you include this information we might be able to give you some news ;) > > > >Martin > > > hi > > i try to do what you wrote . > > but if i enter show painc the ddb at console say "no panic" > > i made some pictures i hope this helps. > > > http://www.glaessixs.de/~glaess/debugging.tgz
Are you using a USB Ethernet device? Could you try -current and let me know if you still have the same panic, a fix regarding uhci(4) has been committed.
