Re: [pfSense] 2.2.5 console problem

[Nick Upson]

I've managed to gain access via the lan, checked the box to enable the
serial Terminal, but it still doesn't respond

Nick Upson, Telensa Ltd, Senior Operations Network Engineer
direct +44 (0) 1799 533252, support hotline +44 (0) 1799 399200

On 24 November 2015 at 15:34, Nick Upson  wrote:

> Hi
>
> I've done a factory reset and upgrade to 2.2.5 and having used the console
> to access the resulting machine I rebooted, I can't talk to the console any
> more, the network is not yet setup correctly (but moved off default) so I
> can't get into it at all.
>
> If I reboot there is initial output on the console (putty) showing the
> initial menu, options 1 to 6
> but nothing after that
>
> How can I undo whatever I've done? or just factory reset
>
> Nick Upson, Telensa Ltd, Senior Operations Network Engineer
> direct +44 (0) 1799 533252, support hotline +44 (0) 1799 399200
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Multiple SSIDs

[Steve Yates]

Steve Yates wrote on Tue, Nov 24 2015 at 9:28 am:
>   We haven't used wireless with pfSense yet.  The manuals for the
> hardware models don't seem to mention how to set up the optional
> wireless. The doc site suggests not using wireless in pfSense?
> (https://doc.pfsense.org/index.php/Should_I_use_pfSense_as_my_access_poi
> nt)  It also says that some cards can handle multiple SSIDs
> (https://doc.pfsense.org/index.php/Wireless_Interfaces).  Does anyone
> know if pfSense's hardware models support multiple SSIDs?
> 
>   The scenario is a client would use pfSense for routing but has a "demo
> room" they would like to keep isolated.  Can we set up a second SSID that
> would connect to that room's network?  Or should we just get an access point
> for that room?
>

Or, for other/future reference, a "guest" SSID that would be isolated 
from the rest.  I'd expect that to be possible as long as it supports multiple 
SSIDs, and just be a matter of the routing setup...

--

Steve Yates
ITS, Inc.



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

[pfSense] 2.2.5 console problem

[Nick Upson]

Hi

I've done a factory reset and upgrade to 2.2.5 and having used the console
to access the resulting machine I rebooted, I can't talk to the console any
more, the network is not yet setup correctly (but moved off default) so I
can't get into it at all.

If I reboot there is initial output on the console (putty) showing the
initial menu, options 1 to 6
but nothing after that

How can I undo whatever I've done? or just factory reset

Nick Upson, Telensa Ltd, Senior Operations Network Engineer
direct +44 (0) 1799 533252, support hotline +44 (0) 1799 399200
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Multiple SSIDs

[Steve Yates]

We haven't used wireless with pfSense yet.  The manuals for the 
hardware models don't seem to mention how to set up the optional wireless.  The 
doc site suggests not using wireless in pfSense? 
(https://doc.pfsense.org/index.php/Should_I_use_pfSense_as_my_access_point)  It 
also says that some cards can handle multiple SSIDs 
(https://doc.pfsense.org/index.php/Wireless_Interfaces).  Does anyone know if 
pfSense's hardware models support multiple SSIDs?

The scenario is a client would use pfSense for routing but has a "demo 
room" they would like to keep isolated.  Can we set up a second SSID that would 
connect to that room's network?  Or should we just get an access point for that 
room?

--

Steve Yates
ITS, Inc.


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

Re: [pfSense] Enable bypass for LAN interface IP not working? ver 2.2.5

[Nicolas Fabris]

Thks Chris!


Lic. Nicolas A. Fabris
Seguridad Informática
Gcia. De Procesos y Sistemas
O.S.P.R.E.R.A.
OO4312-2500 Int. 3119
nicolas.fab...@osprera.org.ar

-Mensaje original-
De: List [mailto:list-boun...@lists.pfsense.org] En nombre de Chris Buechler
Enviado el: lunes, 23 de noviembre de 2015 11:53 p.m.
Para: pfSense Support and Discussion Mailing List
Asunto: Re: [pfSense] Enable bypass for LAN interface IP not working? ver 2.2.5

It's there and it works (from the LAN subnet to the LAN subnet is skipped). 
Check the first config entry in /var/etc/ipsec/ipsec.conf.

On Mon, Nov 23, 2015 at 11:08 AM, Nicolas Fabris 
 wrote:
> Hi folks! How are you?
>
> Nobody?
>
> Thksss!!!
>
> Lic. Nicolas A. Fabris
> Seguridad Informática
> Gcia. De Procesos y Sistemas
> O.S.P.R.E.R.A.
> OO4312-2500 Int. 3119
> nicolas.fab...@osprera.org.ar
>
>
> -Mensaje original-
> De: List [mailto:list-boun...@lists.pfsense.org] En nombre de Nicolas 
> Fabris Enviado el: jueves, 19 de noviembre de 2015 12:49 p.m.
> Para: list@lists.pfsense.org
> Asunto: [pfSense] Enable bypass for LAN interface IP not working? ver 
> 2.2.5
>
> Hi folks! How are you today?
>
> Having problems after upgrading to 2.2.5 with Enable bypass for LAN 
> interface IP option (VPN, IPSEC, Advanced.)
>
> When IPsec tunnel is established I lost ping to LAN IP of pfsense.
> When tunnel is not established, automatically ping come again.
>
> Can somebody give me a hand?
>
> Thks!
>
>
> Lic. Nicolas A. Fabris
> Seguridad Informática
> Gcia. De Procesos y Sistemas
> O.S.P.R.E.R.A.
> * 4312-2500 Int. 3119
> nicolas.fab...@osprera.org.ar
>
> ___
> 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 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] Enable bypass for LAN interface IP not working? ver 2.2.5

[Chris Buechler]

It's there and it works (from the LAN subnet to the LAN subnet is
skipped). Check the first config entry in /var/etc/ipsec/ipsec.conf.

On Mon, Nov 23, 2015 at 11:08 AM, Nicolas Fabris
 wrote:
> Hi folks! How are you?
>
> Nobody?
>
> Thksss!!!
>
> Lic. Nicolas A. Fabris
> Seguridad Informática
> Gcia. De Procesos y Sistemas
> O.S.P.R.E.R.A.
> OO4312-2500 Int. 3119
> nicolas.fab...@osprera.org.ar
>
>
> -Mensaje original-
> De: List [mailto:list-boun...@lists.pfsense.org] En nombre de Nicolas Fabris
> Enviado el: jueves, 19 de noviembre de 2015 12:49 p.m.
> Para: list@lists.pfsense.org
> Asunto: [pfSense] Enable bypass for LAN interface IP not working? ver 2.2.5
>
> Hi folks! How are you today?
>
> Having problems after upgrading to 2.2.5 with Enable bypass for LAN interface 
> IP option (VPN, IPSEC, Advanced.)
>
> When IPsec tunnel is established I lost ping to LAN IP of pfsense.
> When tunnel is not established, automatically ping come again.
>
> Can somebody give me a hand?
>
> Thks!
>
>
> Lic. Nicolas A. Fabris
> Seguridad Informática
> Gcia. De Procesos y Sistemas
> O.S.P.R.E.R.A.
> * 4312-2500 Int. 3119
> nicolas.fab...@osprera.org.ar
>
> ___
> 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 mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Disable DHCP domain-name request

[Dave Warren]

On 2015-11-22 22:51, Nicola Ferrari (#554252) wrote:

Hi, marco?
Did you remove old dhcp leases on pfsense?

If you renew dhcp request on an already present client (in dhcp 
leases), the client will use the old lease (and all its options), so 
you'll not see your new configurations reflected.


Delete all leases from Status -> DHCP leases, restart dhcp service and 
retry ...


That's not necessary and would be incorrect behaviour if it were 
happening. I just confirmed here with my pfSense installation, new 
options are applied without removing the old lease in all expected 
cases, including the Domain Name field.


I tested via a Domain Name change against an automatic renewal and 
manual renewal, as well as a "release/renew" cycle; in all cases the 
client was aware of the new settings immediately after the DHCP 
operation completed.


Now admittedly some broken clients won't reflect all changes 
immediately; some of our VoIP phones will update DNS servers as soon as 
they renew, but won't update timezone information until the next reboot, 
but this is a client deficiency and nothing you do in pfSense (including 
removing the old lease) will make a difference, and it only causes 
issues on specific hardware, but if you capture and analyze the packets, 
you'll see correct data was sent by the DHCP server.


--
Dave Warren
http://www.hireahit.com/
http://ca.linkedin.com/in/davejwarren


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