Its a Dell 1750, no chance to change nic. It was good some days before, changed with the snap from 07. I had to update because of the PPPOE-problem. Don't know if there was a change in the driver. I don't think so. Its a broadcom (bge) driver.

How can i see the nic stats?

Crashes seemed to be gone with some update but came again with last snapshot built on Tue Mar 9 08:46:18.

[pfSense Crash.txt](/public/imported_attachments/1/pfSense Crash.txt)

A fix has been committed for this issue.  The snapshot after the first one available after this post should probably have the fix.

Using  "pfSense-2.0-BETA1-1g-20100309-0142-nanobsd.img.gz" on a Firebox X700 and getting the same, no response from console after "Bootup complete" message

Dear risk:
      your question now ok or not?

At least, it did for a while.  RRD shows that the CPU util was recorded for a while.  Now top (and RRD, dashboard) shows 0% in all categories…

im downloading the 9th march 1GB nanobsd update, hope its there in it and if not can u provide the diff so i can manually do it till new snapshots

Thanks for the detailed report, rewt. Ticket opened.
http://redmine.pfsense.org/issues/show/409

thanks Jimp, i tried the file on the 4th March nanobsd but didnt seem to work so will try the latest snapshots once the traffic shaper issue is solved on them

We'll build in Internet connectivity troubleshooting documentation, but aside from that, there won't be any other documentation available locally. It will all be the help links that exist throughout, pointing to our site. That kind of thing tends to get done after the release is out, and updated numerous times afterwards as errata are found, real world experiences bring up things we should add, and the user error we see tells us where more details are needed, which things aren't clear, etc. We don't want out of date information out there, and documentation changes more than anything (once a release is near finished). We don't want to have to put out new releases to update documentation, hence there will almost certainly never be comprehensive documentation built in.

Does the snapshot you are using list b, g, ng, a, and na or does it only show g ht and a ht?  If it is the latter, try updating to a newer snapshot that shows the ng and na modes in the list.

found patch for file in known problems. sorry to bother you

I updated to today's build (actually just re-wrote my DOM) and all seems well.

Thanks,

Matt

Using   1.2.3-RELEASE   here

I use bittorent and was experiencing over a 1000 inetd running  :o  and I had to reboot every few days  :(.

I was using one Port forward NAT entry for TCP and another one for UDP
I have a Firewall rule for TCP and 1 for UDP on the WAN
the /tmp/rules.debug looked like

# NAT Inbound Redirects rdr on ng0 proto tcp from any to 12.34.56.78 port { 1723 } -> 172.28.15.15 # Reflection redirects rdr on $lan proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19000 rdr on $DMZ proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19001 rdr on $WiFi proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19002 rdr on ng0 proto udp from any to 12.34.56.78 port { 1723 } -> 172.28.15.15 # Reflection redirects rdr on $lan proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19003 rdr on $DMZ proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19004 rdr on $WiFi proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19005 # NAT Reflection rules pass in quick on $lan inet proto tcp from any to $loopback port 19000 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $DMZ inet proto tcp from any to $loopback port 19001 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $WiFi inet proto tcp from any to $loopback port 19002 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $lan inet proto udp from any to $loopback port 19003 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $DMZ inet proto udp from any to $loopback port 19004 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $WiFi inet proto udp from any to $loopback port 19005 keep state label "NAT REFLECT: Allow traffic to localhost"

today I changed for a single TCP/UDP Port forward NAT entry and rebooted
I still have a Firewall rule for TCP and 1 for UDP on the WAN
Now I have a steady 46 inetd running  after 3 hour uptime ;o)

# NAT Inbound Redirects rdr on ng0 proto { tcp udp } from any to 12.34.56.78 port { 1723 } -> 172.28.15.15 # Reflection redirects rdr on $lan proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19000 rdr on $lan proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19001 rdr on $DMZ proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19002 rdr on $DMZ proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19003 rdr on $WiFi proto tcp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19004 rdr on $WiFi proto udp from any to 12.34.56.78 port { 1723 } -> 127.0.0.1 port 19005 # NAT Reflection rules pass in quick on $lan inet proto tcp from any to $loopback port 19000 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $lan inet proto udp from any to $loopback port 19001 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $DMZ inet proto tcp from any to $loopback port 19002 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $DMZ inet proto udp from any to $loopback port 19003 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $WiFi inet proto tcp from any to $loopback port 19004 keep state label "NAT REFLECT: Allow traffic to localhost" pass in quick on $WiFi inet proto udp from any to $loopback port 19005 keep state label "NAT REFLECT: Allow traffic to localhost"

$WiFi is disabled in both case

Committed a fix

Every firewall rule is a traffic shaping rule. The keyword is 'queue'.

known issue.
http://redmine.pfsense.org/issues/show/396

It worked !  Tested with 02152010 Beta snapshot.  :)

before restart:

# df -i Filesystem  1K-blocks   Used   Avail Capacity iused  ifree %iused  Mounted on /dev/ad0s1a   3997382 316750 3360842     9%    8356 509786    2%   / devfs               1      1       0   100%       0      0  100%   /dev /dev/md0         3694     42    3358     1%      20    746    3%   /var/run devfs               1      1       0   100%       0      0  100%   /var/dhcpd/dev

after restart:

/dev/ad0s1a  3997382 316750 3360842    9%    8352 509790    2%  / devfs              1      1      0  100%      0      0  100%  /dev /dev/md0        3694    42    3358    1%      20    746    3%  /var/run devfs              1      1      0  100%      0      0  100%  /var/dhcpd/dev

Now I will try to get latest snapshot and see what happens….