[pfSense Support] About DHCPDISCOVER logs on Syslogs
Hi, I created IP and MAC list on DHCP server service and I checked *Deny unknown clients I have errors* systemlogs below I dont know 08:00:27:76:84:08 and 00:12:79:5d:df:ec How can I learn what does it mean this log and Who is this Macs dhcpd: DHCPDISCOVER from 08:00:27:76:84:08 via vge1: network 10.0.1/24: no free leases dhcpd: DHCPDISCOVER from 00:12:79:5d:df:ec via vge1: network 10.0.1/24: no free leases dhcpd: DHCPDISCOVER from 08:00:27:76:84:08 via vge1: network 10.0.1/24: no free leases dhcpd: DHCPDISCOVER from 00:12:79:5d:df:ec via vge1: network 10.0.1/24: no free leases dhcpd: DHCPDISCOVER from 08:00:27:76:84:08 via vge1: network 10.0.1/24: no free leases dhcpd: DHCPDISCOVER from 00:12:79:5d:df:ec via vge1: network 10.0.1/24: no free leases NOT I use *1.2.3-RC3 * built on Mon Oct 5 22:57:46 UTC 2009 FreeBSD 7.2-RELEASE-p4 i386
Re: [pfSense Support] routed / RIP -- No buffer space available?
- Tim Nelson tnel...@rockbochs.com wrote: - Tim Nelson tnel...@rockbochs.com wrote: Greetings all- I've got a system running 1.2-RELEASE embedded in my home lab (haven't upgraded to 1.2.3 because I don't have a larger CF available yet...). It's been working fine for quite some time but recently I enabled RIP on it. The route updates seem to be sent/received properly for awhile, then my logs start going nuts with errors like this: routed[1242]: Send mcast sendto(re5, 224.0.0.9.520): No buffer space available The Status - System page shows memory usage at 22% (256MB total) and disk usage at 57% (256MB CF). So, where else would buffer space be required that it's not available? Thanks for any pointers you can lend! Something else I didn't notice before... my MBUF Usage: 5337 /5505 Does that make a difference? While my MBUF usage isn't 100%, is it possible that it's high enough to prevent routed/RIP from working properly? Is the fix to simply add more RAM to the system in question? Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] routed / RIP -- No buffer space available?
Tim Nelson wrote: - Tim Nelson tnel...@rockbochs.com wrote: - Tim Nelson tnel...@rockbochs.com wrote: Greetings all- I've got a system running 1.2-RELEASE embedded in my home lab (haven't upgraded to 1.2.3 because I don't have a larger CF available yet...). It's been working fine for quite some time but recently I enabled RIP on it. The route updates seem to be sent/received properly for awhile, then my logs start going nuts with errors like this: routed[1242]: Send mcast sendto(re5, 224.0.0.9.520): No buffer space available The Status - System page shows memory usage at 22% (256MB total) and disk usage at 57% (256MB CF). So, where else would buffer space be required that it's not available? Thanks for any pointers you can lend! Something else I didn't notice before... my MBUF Usage: 5337 /5505 Does that make a difference? While my MBUF usage isn't 100%, is it possible that it's high enough to prevent routed/RIP from working properly? Is the fix to simply add more RAM to the system in question? Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 When you restart pfSense does RIP work? What MBUF usage shows? Does it continuously grow? Evgeny. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] routed / RIP -- No buffer space available?
- Gerald A geraldabli...@gmail.com wrote: Hey Tim, On Tue, Dec 22, 2009 at 7:04 PM, Tim Nelson tnel...@rockbochs.com wrote: Something else I didn't notice before... my MBUF Usage: 5337 /5505 Does that make a difference? While my MBUF usage isn't 100%, is it possible that it's high enough to prevent routed/RIP from working properly? Is the fix to simply add more RAM to the system in question? I noticed no one answered you. I'm not an expert, so take this with a grain of salt: Adding RAM won't increase MBUFs, if I remember correctly. It is a kernel param, and can be tweaked by recompiling the kernel. (It may nowadays be possible to massage it by sysctl, or as a boot time param, but I'm not sure). So, you can tweak it without adding RAM. As for your error: routed[1242]: Send mcast sendto(re5, 224.0.0.9.520): No buffer space available I've seen this when an ipfw rule prevented sending, like for a ping. Could it be a fw rule that is causing this? (Just grasping at straws). Good luck, Gerald - Right now, it's just functioning as a 'core' router with NAT turned off. All interfaces have Allow any protocol from anywhere to anywhere rules on them. There are no other services enabled, not even dns forwarder or DHCP. Just pure routing and RIP. Looking at my edge firewall, I see MBUF usage like this: 738 /1845 which is very odd since that box also has 256MB RAM. The only difference is that my edge box has 2x128MB DIMMs and my core (problematic box) has a single 256MB DIMM. Are the MBUF values calculated randomly? Where do they come from? Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105
Re: [pfSense Support] routed / RIP -- No buffer space available?
- Evgeny Yurchenko evg.yu...@rogers.com wrote: When you restart pfSense does RIP work? What MBUF usage shows? Does it continuously grow? Evgeny. RIP works for a little while upon reboot, then after about 30 minutes or so, stops. The logs say nothing of consequence other than what I've posted already. However, upon first boot, MBUF usage is this: 426 /645 and RIP works fine. Then, later, MBUF usage jumps up and RIP stops working. VERY odd. And, I know there is no traffic through this box since the other 5 NICs are not connected to anything. Only one is connected to my management network... I've been using RIPv2 but for 'gits and shiggles' I'll try RIPv1 and see if that makes any difference. I'm rather stumped on this one... Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] routed / RIP -- No buffer space available?
Tim Nelson wrote: - Evgeny Yurchenko evg.yu...@rogers.com wrote: When you restart pfSense does RIP work? What MBUF usage shows? Does it continuously grow? Evgeny. RIP works for a little while upon reboot, then after about 30 minutes or so, stops. The logs say nothing of consequence other than what I've posted already. However, upon first boot, MBUF usage is this: 426 /645 and RIP works fine. Then, later, MBUF usage jumps up and RIP stops working. VERY odd. And, I know there is no traffic through this box since the other 5 NICs are not connected to anything. Only one is connected to my management network... I've been using RIPv2 but for 'gits and shiggles' I'll try RIPv1 and see if that makes any difference. I'm rather stumped on this one... Tim Nelson Systems/Network Support Rockbochs Inc. (218)727-4332 x105 Try ping 224.0.0.9 from pfSense when there is a problem and right after you reboot. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] sshlockout in 2.0
Hello, # uname -a FreeBSD 2.0-alpha-alpha 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Wed Aug 5 16:55:16 UTC 2009 sullr...@releng_2_0__freebsd_7_2-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7 i386 as soon as I connect to pfsense with the second ssh session I get blocked: # pfctl -t sshlockout -T show 192.168.7.113 Could somebody please explain this pfSense' behavior? If it is done intentionally by developers then why? Thanks, Evgeny. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] sshlockout in 2.0
On Wed, Dec 23, 2009 at 12:00 AM, Evgeny Yurchenko evg.yu...@rogers.com wrote: Hello, # uname -a FreeBSD 2.0-alpha-alpha 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #0: Wed Aug 5 16:55:16 UTC 2009 sullr...@releng_2_0__freebsd_7_2-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7 i386 as soon as I connect to pfsense with the second ssh session I get blocked: # pfctl -t sshlockout -T show 192.168.7.113 Could somebody please explain this pfSense' behavior? If it is done intentionally by developers then why? Sounds like you're using a snapshot that was creating in the middle of the sshlockout changes that went in. At one point it was locking out IPs after 1 failed login attempt. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] What I can do with my appliance
I have an Alix appliance with 256 MB memory. Added an 8 GB cf card and upgraded the firmware. I just wanted to take stock of how far I have come with this little power sipper and pfSense in a short few days since the book came out. I have: a. setup DNS forwarding and my LAN machines are now happy b. setup OpenDNS connectivity c. prioritized my Vonage VOIP connection d. implemented egress filtering - did not know such a thing existed and have subsequently found a screaming mac on my network (UDP port 137 NetBIOS) e. implemented OpenVPN - the setup was not a breeze but a heck of a lot easier than winging it off the net I just have to sit back, take a deep breath and thank the folks who brought us this functionality and put the book together. I've read most of it three times over and can say that I am impressed. I have had the Alix box sitting on a shelf for over a year and thought I'd never actually put it to use. Until the book came out. It is written clearly and covers the stuff I need. For example, I was thinking of getting a wifi card for the small box and reading the book clearly veered me in the direction of staying with an external wifi box to make the setup more robust and debug-able. I have actually invested many hours learning the pfsense environment - I can see using it in an enterprise environment on a real server. The more I work with it , the more I like it and have to say -- this is a beautiful thing. Mehma
[pfSense Support] Wan interface Error
Hi I use dashboard Have a error WAN Interfaces Statistics. I analysed system log but I dont view anything What is the problem Where can I learn What is Problem Where can I look ? Thank you for everything attachment: Error.png- To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] Wan interface Error
Op 23-12-2009 8:19, Koray AGAYA schreef: I use dashboard Have a error WAN Interfaces Statistics. I analysed system log but I dont view anything What is the problem Where can I learn What is Problem Where can I look ? This refers to physical interface errors. Collisions on a duplex mismatch, crc errors, buffer over runs. You'll have to debug switch ports etc. Regards, Seth - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
