[pfSense Support] 192.0.2.112
Hi ! A friend of mine has a strange problem: everytime he reboots his pfsense his dyndns updates with 192.0.2.112 He had this problem with 1.2.2 and now updatet to 1.2.3 RC3 and it still exists... Anyone hast he same issues ? Any ideas ? Regards, Martin
Re: [pfSense Support] 192.0.2.112
I'm not sure how the dynamic dns daemon works on pf, however I could possibly understand this issue if the ISP was doing NAT with their cable/dsl modem and passing off a private IP range to your WAN interface. What IP is assigned to the WAN? Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Tue, Sep 29, 2009 at 5:52 AM, Fuchs, Martin martin.fu...@trendchiller.com wrote: Hi ! A friend of mine has a strange problem: everytime he reboots his pfsense his dyndns updates with 192.0.2.112 He had this problem with 1.2.2 and now updatet to 1.2.3 RC3 and it still exists… Anyone hast he same issues ? Any ideas ? Regards, Martin - 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] SNMP oid's for bandwidth
Hi, I'm trying to monitor in / out bandwidth in bits on wan interface but are having some problems finding the right SNMP oid. I found this one: http://cvstrac.pfsense.com/tktview?tn=257 but the OID i'm trying doesn't return anything. Does anyone have any better suggestions for bandwidth monitoring on pfsense from an nagios server? Regards Stale Johnsen
Re: [pfSense Support] SNMP oid's for bandwidth
to measure bandwidth used I use a script that checks the difference between bytes passed from poll A to poll B. I can point you to the plugin I use if you'd like. gives results like: vr0:UP (131.0KBps/8.0KBps) and I get alarms in my email when I pass too much traffic like you'd expect: * Nagios * Notification Type: PROBLEM Service: Interface Status - vr0 Host: pipboy Address: 192.168.2.1 State: WARNING Date/Time: Tue Sept 29 08:02:33 EDT 2009 Additional Info: vr0:UP (WARN 1490.2KBps/56.2KBps) The OID it uses is just off the IF-MIB if I remember right. and most devices regardless of OS tend to respond to polls on the .1.3.6.1.2.1 trees, especially .1.3.6.1.2.1.2.2 and .1.3.6.1.2.1.25 , the first of which is the one you're looking for for interface information. 2009/9/29 Ståle Johnsen stale.john...@smartit.no Hi, I'm trying to monitor in / out bandwidth in bits on wan interface but are having some problems finding the right SNMP oid. I found this one: http://cvstrac.pfsense.com/tktview?tn=257 but the OID i'm trying doesn't return anything. Does anyone have any better suggestions for bandwidth monitoring on pfsense from an nagios server? Regards Stale Johnsen
Re: [pfSense Support] SNMP oid's for bandwidth
I'm not sure about Nagios for graphing, however here is what my Cacti poller shows. Data Source: x.x.x.x/fxp0 (In) RRD: /var/www/data/graphs/networks/rra/X_in_1.rrd Action: 0, OID: .1.3.6.1.2.1.2.2.1.10.1 (Host: x.x.x.x, Community: **) Data Source: x.x.x.x/fxp0 (Out) RRD: /var/www/data/graphs/networks/rra/X_out_2.rrd Action: 0, OID: .1.3.6.1.2.1.2.2.1.10.1 (Host: x.x.x.x, Community: **) Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com 2009/9/29 Ståle Johnsen stale.john...@smartit.no: Hi, I'm trying to monitor in / out bandwidth in bits on wan interface but are having some problems finding the right SNMP oid. I found this one: http://cvstrac.pfsense.com/tktview?tn=257 but the OID i'm trying doesn't return anything. Does anyone have any better suggestions for bandwidth monitoring on pfsense from an nagios server? Regards Stale Johnsen - 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] SNMP oid's for bandwidth
Ståle Johnsen wrote: Hi, I'm trying to monitor in / out bandwidth in bits on wan interface but are having some problems finding the right SNMP oid. I found this one: http://cvstrac.pfsense.com/tktview?tn=257 but the OID i'm trying doesn't return anything. Does anyone have any better suggestions for bandwidth monitoring on pfsense from an nagios server? I use Cacti to monitor mine, and it polled the pfSense box when I setup the graphs and listed all the interfaces, and I just chose them from there. If you need to find the actual OID, you may have to do something like: snmpwalk -v 2c -c yourcommunity pfsense ip mib-2.interfaces And then use the resulting OIDs to see what you want (You can also use -On to find the numeric OIDs instead of their textual counterparts) IIRC, depending on the system, the wan interface will almost never be the same due to various ways the interfaces are detected by the system. You'll have to look in that snmpwalk output, find the interface name which corresponds to your WAN interface, and then use the traffic counters for that interface index number. For example, my WAN would show up like: IF-MIB::ifDescr.8 = STRING: vlan0 So then the various counters that end in .8 would be for that interface. (IF-MIB::ifInOctets.8, IF-MIB::ifOutOctets.8, etc) Jim - 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] SNMP oid's for bandwidth
Hi, This plugin looks perfect for what i'm looking for. Can you point me to it and paste which OID's you are using? Thank you in advance. Stale Johnsen - Original Message - Fra: iggd...@gmail.com Til: support@pfsense.com Sendt: 29. september 2009 16:10:51 Emne: Re: [pfSense Support] SNMP oid's for bandwidth to measure bandwidth used I use a script that checks the difference between bytes passed from poll A to poll B. I can point you to the plugin I use if you'd like. gives results like: vr0:UP (131.0KBps/8.0KBps) and I get alarms in my email when I pass too much traffic like you'd expect: * Nagios * Notification Type: PROBLEM Service: Interface Status - vr0 Host: pipboy Address: 192.168.2.1 State: WARNING Date/Time: Tue Sept 29 08:02:33 EDT 2009 Additional Info: vr0:UP (WARN 1490.2KBps/56.2KBps) The OID it uses is just off the IF-MIB if I remember right. and most devices regardless of OS tend to respond to polls on the .1.3.6.1.2.1 trees, especially .1.3.6.1.2.1.2.2 and .1.3.6.1.2.1.25 , the first of which is the one you're looking for for interface information. 2009/9/29 Ståle Johnsen stale.john...@smartit.no Hi, I'm trying to monitor in / out bandwidth in bits on wan interface but are having some problems finding the right SNMP oid. I found this one: http://cvstrac.pfsense.com/tktview?tn=257 but the OID i'm trying doesn't return anything. Does anyone have any better suggestions for bandwidth monitoring on pfsense from an nagios server? Regards Stale Johnsen
RE: [pfSense Support] 192.0.2.112
-Original Message- From: Curtis LaMasters [mailto:curtislamast...@gmail.com] Sent: Tuesday, September 29, 2009 5:50 AM To: support@pfsense.com Subject: Re: [pfSense Support] 192.0.2.112 I'm not sure how the dynamic dns daemon works on pf, however I could possibly understand this issue if the ISP was doing NAT with their cable/dsl modem and passing off a private IP range to your WAN interface. What IP is assigned to the WAN? Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com On Tue, Sep 29, 2009 at 5:52 AM, Fuchs, Martin martin.fu...@trendchiller.com wrote: Hi ! A friend of mine has a strange problem: everytime he reboots his pfsense his dyndns updates with 192.0.2.112 He had this problem with 1.2.2 and now updatet to 1.2.3 RC3 and it still exists. Anyone hast he same issues ? Any ideas ? Regards, Martin - Yep, I've had a few modems that do this... they start with the private subnet until assigned the IP from the ISP - then it switches. I'm guessing it's for diagnosing the line - but is just a pain in the hind One of our sites opted for the $5 static IP... the other just waited for it to update... not sure if there is another way around it. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: [pfSense Support] 192.0.2.112
On Tue, Sep 29, 2009 at 1:26 PM, Michel Servaes mic...@mcmc.be wrote: Is 192.0.2.112 not a public range ? 192.0.2.0/24 is reserved for documentation/example uses, RFC 3330. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org It's not a NATted adress on the WAN interface... It registers ths 192.x.x.x IP on dyndns and has a public IP... Even after a fresh install... I've only seen this on that system... Sorry, Martin - 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: AW: [pfSense Support] 192.0.2.112
Fuchs, Martin wrote: On Tue, Sep 29, 2009 at 1:26 PM, Michel Servaes mic...@mcmc.be wrote: Is 192.0.2.112 not a public range ? 192.0.2.0/24 is reserved for documentation/example uses, RFC 3330. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org It's not a NATted adress on the WAN interface... It registers ths 192.x.x.x IP on dyndns and has a public IP... Even after a fresh install... I've only seen this on that system... Sorry, Martin Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? Eugene - 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] vlan troubles
it could also be a bogus switch; it might not like you trying to run tagged and untagged frames on the same port. I'd advise changing to use vlan2, say, as your LAN and ensure all switch ports are marked untagged vlan2, (or in cisco speak, in access mode, access vlan 2, and nonegotiate). Everything works as it should now, thanks for all the patience. Fresh cabling across the board made it tick. No surprise, all the cables were recently re-routed in a new trough. jlc - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: AW: [pfSense Support] 192.0.2.112
-Ursprüngliche Nachricht- Von: Evgeny Yurchenko [mailto:evg.yu...@rogers.com] Gesendet: Dienstag, 29. September 2009 20:09 An: support@pfsense.com Betreff: Re: AW: [pfSense Support] 192.0.2.112 Fuchs, Martin wrote: On Tue, Sep 29, 2009 at 1:26 PM, Michel Servaes mic...@mcmc.be wrote: Is 192.0.2.112 not a public range ? 192.0.2.0/24 is reserved for documentation/example uses, RFC 3330. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org It's not a NATted adress on the WAN interface... It registers ths 192.x.x.x IP on dyndns and has a public IP... Even after a fresh install... I've only seen this on that system... Sorry, Martin Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? Eugene - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org No, it's not :-( that's what irritates me... - 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: AW: [pfSense Support] 192.0.2.112
Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? No, it's not :-( that's what irritates me... There is no other option, it had to be on the WAN interface at some point if the firewall registered it. It's impossible for it to just pick some arbitrary IP and register it. Check the system log, it will show what it's registering. If so, wouldn't the DynDNS option publish the correct IP once it changed again? Regards, -Jeppe - 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: AW: [pfSense Support] 192.0.2.112
On Tue, Sep 29, 2009 at 4:48 PM, Jeppe Øland jol...@gmail.com wrote: Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? No, it's not :-( that's what irritates me... There is no other option, it had to be on the WAN interface at some point if the firewall registered it. It's impossible for it to just pick some arbitrary IP and register it. Check the system log, it will show what it's registering. If so, wouldn't the DynDNS option publish the correct IP once it changed again? Yes, the new WAN IP script will re-register, but maybe that's failing for some reason if the IP changes very quickly. System logs will show. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: AW: [pfSense Support] 192.0.2.112
-Ursprüngliche Nachricht- Von: Chris Buechler [mailto:cbuech...@gmail.com] Gesendet: Dienstag, 29. September 2009 23:05 An: support@pfsense.com Betreff: Re: AW: [pfSense Support] 192.0.2.112 On Tue, Sep 29, 2009 at 4:48 PM, Jeppe Øland jol...@gmail.com wrote: Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? No, it's not :-( that's what irritates me... There is no other option, it had to be on the WAN interface at some point if the firewall registered it. It's impossible for it to just pick some arbitrary IP and register it. Check the system log, it will show what it's registering. If so, wouldn't the DynDNS option publish the correct IP once it changed again? Yes, the new WAN IP script will re-register, but maybe that's failing for some reason if the IP changes very quickly. System logs will show. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org I'll have a look again, but i also wonder why the script does not re-register the official-wan ip... - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
AW: AW: [pfSense Support] 192.0.2.112
-Ursprüngliche Nachricht- Von: Chris Buechler [mailto:cbuech...@gmail.com] Gesendet: Dienstag, 29. September 2009 23:05 An: support@pfsense.com Betreff: Re: AW: [pfSense Support] 192.0.2.112 On Tue, Sep 29, 2009 at 4:48 PM, Jeppe Øland jol...@gmail.com wrote: Do you have this 192.x.x.x for WAN at your Stauts-Interfaces page? No, it's not :-( that's what irritates me... There is no other option, it had to be on the WAN interface at some point if the firewall registered it. It's impossible for it to just pick some arbitrary IP and register it. Check the system log, it will show what it's registering. If so, wouldn't the DynDNS option publish the correct IP once it changed again? Yes, the new WAN IP script will re-register, but maybe that's failing for some reason if the IP changes very quickly. System logs will show. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org What also irritates me is that this IP is also used in the interfaces.inc... - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
