Re: [pfSense] Limiter via Floating Rules?
Hi Ermal, On 01/07/2014 07:16 PM Ermal Luçi wrote: You should use pass action for the first rule and the second which specified the limiters should stay as is. This is because match rules do not apply action only remember the decision to be applied on a later action matching rule like pass/block. thanks for your response. Well, both rules are having limiters configured which I thought were optional parameters to be applied using the match option since I don't want the pass/block state of that particular traffic to be changed by any floating rule. Second, having the quick option set on both rules using the pass action on the first wouldn't that stop interface specific rules from being processed? I do have a bunch of rules set up for the interface where the traffic of the MyOffice alias is originated from. /J signature.asc Description: OpenPGP digital signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Limiter via Floating Rules?
On Tue, Jan 7, 2014 at 2:08 PM, Jan j...@agetty.de wrote: Hi Ermal, On 01/07/2014 07:16 PM Ermal Luçi wrote: You should use pass action for the first rule and the second which specified the limiters should stay as is. This is because match rules do not apply action only remember the decision to be applied on a later action matching rule like pass/block. thanks for your response. Well, both rules are having limiters configured which I thought were optional parameters to be applied using the match option since I don't want the pass/block state of that particular traffic to be changed by any floating rule. Second, having the quick option set on both rules using the pass action on the first wouldn't that stop interface specific rules from being processed? I do have a bunch of rules set up for the interface where the traffic of the MyOffice alias is originated from. Well short answer. Try with only the second rule stating !from your alias. That should give you a working config. /J ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Lan Card Support
Hi Adam/Maik Thanks for your response, I would hope Adam is right as the server i'll recieve for pfSense installation has onboard lan card that i described. Looking for a successful installation :) On Tue, Jan 7, 2014 at 5:04 AM, Maik Heinelt m...@vegasystems.com wrote: On 2014/01/07 2:48, Adam Thompson wrote: It should, as that card will either use standard Intel or Broadcom Ethernet chips. There is always a small possibility that any given card may be incompatible, but in your case I would expect that be almost negligible. If the card is a brand-new model or revision, you are more likely to have problems. -Adam On Jan 6, 2014 11:42 AM, rajan agarwal rajanagarwa...@gmail.com rajanagarwa...@gmail.com wrote: Hi All, I am about to put pfSense in a production box. I will be using IBM Quad Port Gigabit PCIe Ethernet Card P/N.: 39Y6136. Will pfSense version 2.0.1 support this particular LAN card? I can't find the name of this LAN card on the freeBSD 8.1 hardware support page. Regards ___ List mailing listList@lists.pfsense.orghttp://lists.pfsense.org/mailman/listinfo/list sorry, I disagree. I bought two quad port cards and all are with Intel chipset. The card was found by pfsense (found it in dmesg output), but it never was usable as NIC in pfsense. I ended up with buying a dual port card what is working fine. Not working: - Silicom PEG4IL - Intel EXPI9404PT Intel Pro/1000 PT QUAD PORT Working: - Intel EXPI9402PT Pro/1000 PT DELL X3959 Dual Port PCI-E x4 Maik ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list Regards Rajan Agarwal ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] is it possible to rename gateways in 2.1 release AMD64?
Am 07.01.2014 20:52, schrieb Joe Landman: Hi folks: I am trying to match a spec we've been given as precisely as possible. I can't rename the gateways from the web interface. Is it possible to rename them from hand editing the config.xml file? or some other method? Thanks! Joe Not sure i follow. What is not working with: Click on the System -- Routing -- Gateways on the e button next to the gateway you want to change the name of. Set the name you want in the Name field. Regards Matthias May ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] is it possible to rename gateways in 2.1 release AMD64?
Once you create a gateway, you can not rename it from the GUI. I had to delete and re-create my gateway in order to rename it. On Tue, Jan 7, 2014 at 12:02 PM, Matthias May matth...@may.nu wrote: Am 07.01.2014 20:52, schrieb Joe Landman: Hi folks: I am trying to match a spec we've been given as precisely as possible. I can't rename the gateways from the web interface. Is it possible to rename them from hand editing the config.xml file? or some other method? Thanks! Joe Not sure i follow. What is not working with: Click on the System -- Routing -- Gateways on the e button next to the gateway you want to change the name of. Set the name you want in the Name field. Regards Matthias May ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] is it possible to rename gateways in 2.1 release AMD64?
On 01/07/2014 03:09 PM, Walter Parker wrote: Once you create a gateway, you can not rename it from the GUI. I had to delete and re-create my gateway in order to rename it. Got it. Thanks! -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com twtr : @scalableinfo phone: +1 734 786 8423 x121 cell : +1 734 612 4615 ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] is it possible to rename gateways in 2.1 release AMD64?
On 01/07/2014 03:02 PM, Matthias May wrote: Am 07.01.2014 20:52, schrieb Joe Landman: Hi folks: I am trying to match a spec we've been given as precisely as possible. I can't rename the gateways from the web interface. Is it possible to rename them from hand editing the config.xml file? or some other method? Thanks! Joe Not sure i follow. What is not working with: Click on the System -- Routing -- Gateways on the e button next to the gateway you want to change the name of. Set the name you want in the Name field. It doesn't allow you to change names of gateways once they are set. I am not sure precisely why, but it simply does not work. Regards Matthias May ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com twtr : @scalableinfo phone: +1 734 786 8423 x121 cell : +1 734 612 4615 ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] Limiter via Floating Rules?
Hi Ermal, On 01/08/2014 12:04 AM Ermal Luçi wrote: Well short answer. Try with only the second rule stating !from your alias. That should give you a working config. but how about multiple departments then? Each of them with a separate set of limiters as well. I'm just trying to understand why the match action doesn't seem to work with limiters like it does with any other optional parameters like queues for example. Assigning limiters to all interface based rules would be a real pain depending on the size of the rule set and the complexity of the configuration. E.g. lets say you've got 14 interfaces on a box each one supposed to have its own set of limiters. I'd expect multiple floating rules, each one defining a separate set of limiters per department to work while pushing unmatched traffic into a default set of limiters using a catch-all rule at the very end of the chain. I mean, this is the intended use of the floating tab, right? So if there's anything wrong with my assumption someone be so kind and kickstart my brain. It would be nice to have a clear explanation to this but also for anyone else who might come up with the same question bumping into this thread. Thanks a lot :) signature.asc Description: OpenPGP digital signature ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
Re: [pfSense] is it possible to rename gateways in 2.1 release AMD64?
On Tuesday, January 07, 2014 10:11:35 PM Joe Landman wrote: It doesn't allow you to change names of gateways once they are set. I am not sure precisely why, but it simply does not work. It would be nice to lift this limitation while in-flight. I've hit situations where it would have been useful to do so, and it's twice the effort if you have to delete it and re-enter it as something else you actually want. Mark. signature.asc Description: This is a digitally signed message part. ___ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
