On Jan 19, 7:58pm, [email protected] (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote: -- Subject: Re: [NetBSD-7] Panic in nfsd
| Hello, | | I have tried to delete all references to tap0 in /etc/altqd.conf My | /etc/altqd.conf file is now : | | interface wm1 bandwidth 10M priq | | class priq wm1 high_class NULL priority 1 | class priq wm1 low_class NULL priority 0 default | | filter wm1 high_class 0 1194 0 0 17 | filter wm1 high_class 0 0 0 1194 17 | | #interface tap0 bandwidth 2M priq | # | #class priq tap0 high_class_vpn NULL priority 1 | #class priq tap0 low_class_vpn NULL priority 0 default | # | #filter tap0 high_class_vpn 192.168.10.250 0 0 0 17 | #filter tap0 high_class_vpn 0 0 192.168.10.250 0 17 | | interface wm0 bandwidth 1000M priq | | class priq wm0 high_class_lan NULL priority 1 | class priq wm0 low_class_lan NULL priority 0 default | | filter wm0 high_class_lan 192.168.10.250 0 0 0 17 | filter wm0 high_class_lan 0 0 192.168.10.250 0 17 | | And my server panics again. Thus this panic is not related to tap0 but | to altqd itself. | | This server is far away (I cannot use kernel debugger as I don't have a | console access) and I haven't any information in /var/log/message (fsck | has failed and system has paniced twice, I have no kernel dump in | /var/crash). Ok, I can try this on my home lan. Can you please explain your topology? Which is the outside interface (wm1?), is wm0 192.168.10.250? christos
