Re: [pfSense] Ipsec issue

[Eero Volotinen]

Well, that sounds like lifetime setting is not correct on another endpoint?

Eero

3.8.2016 3.07 ap. "Francois Roussy"  kirjoitti:

> Hi,
>
> I have a ipsec tunnel between a pfsense 2.3.2 and a fortigate 200d
>
> Every ~24h, there is a small disruption because it seem the tunnel drop
> and come back..
>
> any idea why ?
>
> On the 200d, there is 10 more fortigate 50b connected to it, and i dont
> see that issue.
>
> thanks
>
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Ipsec issue

[Francois Roussy]

Hi,

I have a ipsec tunnel between a pfsense 2.3.2 and a fortigate 200d

Every ~24h, there is a small disruption because it seem the tunnel drop and 
come back..

any idea why ?

On the 200d, there is 10 more fortigate 50b connected to it, and i dont see 
that issue.

thanks


___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Alias duplicate - can't delete any of them

[Ryan Coleman]

Two choices that I’m aware of:

1) delete the main rule and recreate
2) Download backup config, remove from the file, upload new config and watch it 
wipe.


> On Aug 2, 2016, at 6:58 PM, Ugo Bellavance  wrote:
> 
> Hi,
> 
> First problem: some time ago a duplicate of an alias got created, I don't 
> know why or how.
> 
> Second problem: when I try to delete one of the duplicate, I get the standard 
> warning saying that all elements that still use this alias will become 
> invalid.  I click OK and both are still here.  I get an errer message saying 
> "Cannot delete alias. Currently in use by /rule name/.
> 
> How should I proceed?  Remove it temporarily from the rule, then delete one 
> of them, then add it back to the rule?
> 
> Thanks,
> 
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Alias duplicate - can't delete any of them

[Ugo Bellavance]

Hi,

First problem: some time ago a duplicate of an alias got created, I 
don't know why or how.


Second problem: when I try to delete one of the duplicate, I get the 
standard warning saying that all elements that still use this alias will 
become invalid.  I click OK and both are still here.  I get an errer 
message saying "Cannot delete alias. Currently in use by /rule name/.


How should I proceed?  Remove it temporarily from the rule, then delete 
one of them, then add it back to the rule?


Thanks,

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Unable to Retrieve Page Information

[Ron Lemon]

Thanks Mark.  Hit the nail on the head.  I am now at 2.3.2 and I can again
see all my installed and available packages.

I guess that means I am off to show more people this bright shiny new
interface as I now have all the functionality (and more) that I require.

Thanks for the great product and support.  You really can't beat this for
the price.

On Tue, Aug 2, 2016 at 4:43 PM, Mark Wiater 
wrote:

>
>
> On 8/2/2016 2:58 PM, Ron Lemon wrote:
>
>> I am on Community Edition 2.3.1-RELEASE (amd64)
>>
>> This weekend I added the new replacement for VNSTAT2 (Traffice Totals I
>> think it is now called).
>>
>
> Any suggestions on how to fix this?
>>
>
> Yes, I had the same problem. The day after 2.3.2 was releaseed, and I was
> on 2.3.1, I installed a package - don't recall which.
>
> After that installation, it would not display any packages, including
> installed, and it would not tell me my update status.
>
> The solution for me was to upgrade to 2.3.2 from the command line. For me
>
> from the console
>>
>> pkg clean
>> pkg update
>> pkg upgrade
>> reboot
>>
>
> worked
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Unable to Retrieve Page Information

[Mark Wiater]

On 8/2/2016 2:58 PM, Ron Lemon wrote:

I am on Community Edition 2.3.1-RELEASE (amd64)

This weekend I added the new replacement for VNSTAT2 (Traffice Totals I
think it is now called).



Any suggestions on how to fix this?


Yes, I had the same problem. The day after 2.3.2 was releaseed, and I 
was on 2.3.1, I installed a package - don't recall which.


After that installation, it would not display any packages, including 
installed, and it would not tell me my update status.


The solution for me was to upgrade to 2.3.2 from the command line. For me


from the console

pkg clean
pkg update
pkg upgrade
reboot


worked
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Unable to Retrieve Page Information

[Ron Lemon]

I am on Community Edition 2.3.1-RELEASE (amd64)

This weekend I added the new replacement for VNSTAT2 (Traffice Totals I
think it is now called).

After adding this (which seemed to go with no errors) I no longer seem to
be able to get the list of packages that I have installed or the list of
all packages.

Is this something anyone else has experienced?  I have rebooted but that
did not seem to change anything.

Is there a log I should look in?  I don't see anything in the logs
presented by the GUI.

Any suggestions on how to fix this?


PS   I love the new interface but not having this one package was
preventing me from updating because I use the results from it regularly.
Now that I have it I would love to move all my systems up.

Thanks.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Mini-USB console on new pfSense certified hardware

[Karl Fife]

On 8/1/2016 4:20 PM, Moshe Katz wrote:

You could also use a set of USB over twisted pair adapters, but those
aren't necessarily the most dependable pieces of hardware over long
distances.


Indeed.  When something goes wrong, cognitive loads are high, and you 
don't want to be dickign around with uncertainty about your diagnostic 
tools and methods.  It's especially problematic at the precise moment 
when your wings are clipped because you don't have access to various 
online resources.  It's one of those "correlated risks" that makes this 
a bad place to introduce new variables, even if their absolute risk is 
low.   Just my 64¢.


___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Mini-USB console on new pfSense certified hardware

[WebDawg]

On Mon, Aug 1, 2016 at 7:03 PM, Jeremy Porter  wrote:

> There is an on-board UART to USB converter on the
> RCC-VE/DFFv2/4860/8880/2440/2220.   This is wired directly to the
> chipset uart on the Rangely, at system voltage levels, not at RS232
> levels.  (The USB convert chip is cost comparable to a RS-232 voltage
> driver chip in cost, and has a smaller board footprint.)  Additionally
> the connect takes up less back-panel space.
>
> There are no test points brought out, if there were you would need a
> level shifter, and an isolator to protect the SOC.
>
> Most modern systems have USB Host ports, which is all that is required
> for the USB serial interface to work.  Any small system, can manage
> quite a few hosts with a powered usb hub.  (We actually use Beaglebone
> black as terminal servers).  We actually switched all our remaining
> terminal server systems over to these types, by getting a rack-mount 32
> port USB to RS-232 converter.
>
>
Can you explain to me the last statement?  You now use a Beaglebone as the
server, and manage the rest of your RS-232 terminal types with the
Beaglebone too.  With the 32 port USB to RS-232 converter?
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold