Re: [pfSense] Change WAN interface

[Luc Paulin]

I think that I just figure it out... Yeah it was at that page I was looking
at but didn't understand the difference beetween interface and network
port,  I found this a bit confusing.

--
 !
   ( o o )
 --oOO(_)OOo--
   Luc Paulin
   email: paulinster(at)gmail.com
   Skype: paulinster


2016-10-14 14:18 GMT-04:00 Steve Yates :

> Interfaces/(assign) page should have drop downs to pick the interface.
>
> --
>
> Steve Yates
> ITS, Inc.
>
> -Original Message-
> From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Luc Paulin
> Sent: Friday, October 14, 2016 1:16 PM
> To: pfSense Support and Discussion Mailing List 
> Subject: [pfSense] Change WAN interface
>
> How can I assign the wan interface to another interface ...
> Let say I initally assign WAN to bge0, but then I need to move WAN to
> bge3  How can this be done Look like we can't delete the assign WAN
> interface.
> ___
> 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] Change WAN interface

[Luc Paulin]

How can I assign the wan interface to another interface ...
Let say I initally assign WAN to bge0, but then I need to move WAN to bge3
 How can this be done Look like we can't delete the assign WAN interface.

Am I missing something  ?

  -Luc

--
 !
   ( o o )
 --oOO(_)OOo--
   Luc Paulin
   email: paulinster(at)gmail.com
   Skype: paulinster
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Change WAN interface

[Steve Yates]

Interfaces/(assign) page should have drop downs to pick the interface.

--

Steve Yates
ITS, Inc.

-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Luc Paulin
Sent: Friday, October 14, 2016 1:16 PM
To: pfSense Support and Discussion Mailing List 
Subject: [pfSense] Change WAN interface

How can I assign the wan interface to another interface ...
Let say I initally assign WAN to bge0, but then I need to move WAN to bge3  How 
can this be done Look like we can't delete the assign WAN interface.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] Change WAN interface

[Luc Paulin]

How can I assign the wan interface to another interface ...
Let say I initally assign WAN to bge0, but then I need to move WAN to bge3
 How can this be done Look like we can't delete the assign WAN interface.

Am I missing something  ?

  -Luc

--
 !
   ( o o )
 --oOO(_)OOo--
   Luc Paulin
   email: paulinster(at)gmail.com
   Skype: paulinster
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Lightning strike

[Espen Johansen]

Map interfaces based on mac and give them a name. Then adress the
interfaces based on that name. When it comes to reorganization of
interfaces the answer is; don't do it. Let the user remap interfaces
manually only. If the user wants to drop their DMZ to get wan back online
then it should be a manual process.
In order to accomplish this you need a interface database and a simple
interface setup process with a foreach loop. This code was done in 2007 but
it was never comitted.

Ifconfig allows naming of interfaces. So once they are named and mac->name
binding is done, then the binding is remebered "forever" in a config file.
If a new interface is added and not found in the mac->name "DB" it is just
placed in a unassigned state untill the user assigns it manually.

-lsf

On Fri, Oct 14, 2016, 18:00 Vick Khera  wrote:

> On Thu, Oct 13, 2016 at 6:25 PM, Walter Parker  wrote:
> > Problem is that all of the current OS do this sort of renumbering (I'd
> have
> > to check, but I think it could be a hardware/driver issue). IIRC Linux
> > systems have had this sort of problem in even greater measure than the
> > BSDs. The plug and play nature of USB has caused issues for most systems
>
> Current versions of CentOS/RedHat hard-wire ethernet names. You have
> to go dig in and find some file that has the mappings and delete them
> if you do something like replace a motherboard with embedded NICs,
> otherwise it makes all new ethernet device names for you. The mapping
> is base on MAC address.
> ___
> 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] Lightning strike

[Vick Khera]

On Thu, Oct 13, 2016 at 6:25 PM, Walter Parker  wrote:
> Problem is that all of the current OS do this sort of renumbering (I'd have
> to check, but I think it could be a hardware/driver issue). IIRC Linux
> systems have had this sort of problem in even greater measure than the
> BSDs. The plug and play nature of USB has caused issues for most systems

Current versions of CentOS/RedHat hard-wire ethernet names. You have
to go dig in and find some file that has the mappings and delete them
if you do something like replace a motherboard with embedded NICs,
otherwise it makes all new ethernet device names for you. The mapping
is base on MAC address.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.3.2-p1 RELEASE Now Available

[Ryan Coleman]

It’s been around since 2.3.0 was released, I believe.




> On Oct 13, 2016, at 8:23 PM, Volker Kuhlmann  wrote:
> 
> On Fri 14 Oct 2016 11:21:10 NZDT +1300, Jim Pingle wrote:
> 
>> There are no installers for 2.3.2-p1. You have to install 2.3.2 and
>> update to patch 1 once it's installed.
> 
> Ah, I see, that's why pre-2.3.2 doesn't offer it as an update either.
> I haven't noticed this situation having existed before, would it be
> useful to mention it inthe release note?
> 
> Thanks Jim,
> 
> Volker
> 
> -- 
> Volker Kuhlmann   is list0570 with the domain in header.
> http://volker.top.geek.nz/Please do not CC list postings to me.
> ___
> 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