hi thanks I think the problem is Ethernet card of pfsense(real tek) and the router port. Today i added another router. and from internal pc i can get 34 M/b speed!! so it guess there is problem between duplexing …..

Thanks for the reply! Here is some samples from the report management is used to seeing: Listed by source hosts: Accepted 45 packets on interface eth1   From XXX.XXX.XXX.XXX - 1 packet to udp(123)   From XXX.XXX.XXX.XXX - 70 packets to udp(53,123) tcp(22)   From XXX.XXX.XXX.XXX - 168 packets to udp(123)   From XXX.XXX.XXX.XXX - 25 packets to udp(123) Listed by source hosts: Dropped 105 packets on interface eth0   From X.X.X.X - 1 packet to udp(5060)   From X.X.X.X - 1 packet to udp(5060)   From  X.X.X.X- 16 packets to tcp(18490)   From X.X.X.X - 2 packets to tcp(445)   From X.X.X.X - 1 packet to udp(1434)   From X.X.X.X - 1 packet to udp(1434)   FromX.X.X.X - 1 packet to tcp(3306) Listed by source hosts: Logged 1181 packets on interface eth1   From XXX.XXX.XXX.XXX - 98 packets to tcp(80)   From XXX.XXX.XXX.XXX - 255 packets to tcp(80)   From XXX.XXX.XXX.XXX - 21 packets to tcp(80)   From XXX.XXX.XXX.XXX - 34 packets to tcp(80)   From XXX.XXX.XXX.XXX - 36 packets to tcp(80)   From XXX.XXX.XXX.XXX - 30 packets to tcp(80) Listed by source hosts: Rejected 12 packets on interface eth0   From XXX.XXX.XXX.XXX - 1 packet to udp(123)   From XXX.XXX.XXX.XXX - 1 packet to tcp(22)   From XXX.XXX.XXX.XXX - 1 packet to udp(43361)   From XXX.XXX.XXX.XXX - 1 packet to tcp(2967)   From XXX.XXX.XXX.XXX - 1 packet to tcp(22)   From XXX.XXX.XXX.XXX - 3 packets to tcp(30978) Listed by source hosts: Rejected 855 packets on interface eth1   From XXX.XXX.XXX.6 - 15 packets to tcp(443)   From XXX.XXX.XXX.58 - 3 packets to icmp(8)   From XXX.XXX.XXX.59 - 15 packets to tcp(443)   From XXX.XXX.XXX.61 - 120 packets to tcp(443)   From XXX.XXX.XXX.67 - 15 packets to tcp(443)   From XXX.XXX.XXX.70 - 50 packets to tcp(443,1935)   From XXX.XXX.XXX.71 - 60 packets to tcp(443,1935) Hope this helps. Any idea when we will see 2.0? I have been loving 1.2.3 and love the new stuff in 2.0 especialy the key managment for openvpn. Thanks again!! Rich

Do you have "Block private networks" or "Block bogon networks" set on your WAN interface?

There is no documentation for this.  Read the builder scripts source code and if this is not an option consider purchasing a reseller agreement from https://portal.pfsense.org/index.php/reseller-subscription

pfSense 1.2.3 only supports PPPoE on WAN. The 2.0 beta can do as many PPPoE interfaces as you like. If you must use 1.2.3, you can put some kind of small NAT device in between pfSense and the modem, or if you have a modem/router, see if it can handle the PPPoE login portion (often called a half-bridge).

You can use tcpdump on the physical interface which will grab the information you need.  If you want, you can easily capture this data in binary format and then feed it to an instance of Wireshark running on a separate machine for extra prettiness.

Old (overblown) news, there is already at least one other thread on the matter.

Thanks for your help. I will try this tomorrow and will post the result.

You can check the inode usage from the shell with "df -i" You might also want to have a look at this thread I started for a similar issue: http://forum.pfsense.org/index.php/topic,26626.0.html

IIRC others have solve similar problems with a cronjob "/sbin/dhclient vr1"

From the physical console, reset the password.

Really simple introductory would be the Head First Networking (an O'Reilley) Then maybe CBT Nuggets Jeremy Ciaora CCNA ICND1 (video lectures, very good and entertaining, not dry!)

I (and quite a few other people) have had real problems with those Realtek NICs. Nasty st-st-stuu-uu-uuttering action if you get my meaning. AS someone else said  "They give new meaning to the term 'low end' " Everyone recommends the Intel 1000's and so do I.

well that is weird.  it sure sounds like the dhcp server is not running.  what does DHCP look like on the Status page?  If you try and fail to get an IP and set one manually, try looking at the firewall system logs to see if any error messages shed light.