Am 21.11.2010 03:01, schrieb Chris Buechler:
A broadcast domain is the layer 2 segregation of the network. If
you're not using VLANs, and have one switch, you have one broadcast
domain. The broadcast address is different, but those broadcasts all
go to every device. In the case of buggy phone
hi,
just my simple idea, not sure if it fits perfectly.
setup the interface on the firewall to
192.168.0.0/23 p.e.
if-address 192.168.0.1
add a second virtual IP (carp) to the Lan IF
192.168.1.1 ( as gateway address for the second /24 )
add certain rules for it if neccessary.
TROUBLESHOOTING:
Le Fri, 19 Nov 2010 15:58:35 -0800 (PST), Gé Weijers g...@weijers.org a écrit
:
We'd like to separate IPs of bacbone antennas from client ones, for
example 192.168.1.0/24 for antennas and 192.168.2.0/24 for
people. How this could be done ? [...]
I hope you realize that your customers
On 11/20/2010 09:04 PM, Frédéric Boiteux wrote:
I'm not sure to understand well : in the case I gave, 192.168.1.0/24 and
192.168.2.0/24, the two nets don't share the same broadcast domain
(192.168.1.255 and 192.168.2.255), isn't it ?
Fred.
I'm also in doubt.
Because your example is
On 10-11-20 08:25 PM, Karsten Becker wrote:
On 11/20/2010 09:04 PM, Frédéric Boiteux wrote:
I'm not sure to understand well : in the case I gave, 192.168.1.0/24 and
192.168.2.0/24, the two nets don't share the same broadcast domain
(192.168.1.255 and 192.168.2.255), isn't it ?
Fred.
2010/11/20 Karsten Becker karsten.bec...@ecologic.eu:
On 11/20/2010 09:04 PM, Frédéric Boiteux wrote:
I'm not sure to understand well : in the case I gave, 192.168.1.0/24 and
192.168.2.0/24, the two nets don't share the same broadcast domain
(192.168.1.255 and 192.168.2.255), isn't it ?
I'm
I use Engenius equipment quite often. They support a management interface and
up to 4 SSIDs all controlled with VLAN tagging.
--Original Message--
From: Fred Boiteux
To: support@pfsense.com
ReplyTo: support@pfsense.com
Subject: Re: [pfSense Support] how to manage 2 subnets for LAN
I do this all the time and using a separate nic is simpler and easier to
manage than an alias. Unless I am missing something, a vlan for this case is
overkill.
--
Richard
On Thu, Nov 18, 2010 at 4:13 PM, David Burgess apt@gmail.com wrote:
On Thu, Nov 18, 2010 at 3:51 PM,
On 2010-11-19 9:56 AM, Richard Amerman fi...@7technw.com wrote:
I do this all the time and using a separate nic is simpler and easier to
manage than an alias. Unless I am missing something, a vlan for this case
is
overkill.
I discussed this with the m0n0wall list back in '07 where cmb and
When there is a good use-case I completely agree with you, and it is
probably my fault for not remembering that his traffic probably needed to be
kept more separate.
In many cases it is completely a non issue. In most of the cases I use this
method it is all within a single internal organization
Hi,
Le Thu, 18 Nov 2010 15:16:24 -0700,
David Burgess apt@gmail.com a écrit :
In that case you can add an alias to the LAN interface. IIRC, you just
run ifconfig appending 'alias' to the end. Don't quote me on it
though.
Get that working, then use shellcmd to make it stick
On Fri, Nov 19, 2010 at 4:27 PM, Fred Boiteux fblis...@free.fr wrote:
I saw the
http://doc.pfsense.org/multiple-subnets-one-interface-pfsense.pdf
but I was doubtful about how well it's supported in PfSense :-/
Works fine. Generally bad network design to have multiple IP subnets
on the same
On Thu, 18 Nov 2010, Fred Boiteux wrote:
We'd like to separate IPs of bacbone antennas from client ones, for
example 192.168.1.0/24 for antennas and 192.168.2.0/24 for
people. How this could be done ? [...]
I hope you realize that your customers can manually switch subnets on
their end
Hello PfSense masters,
I'm using successfully PfSense to manage the access of a wifi network
providing Internet to my village. At now, we have a simple setup on
the LAN side where all backbone network (antennas) and connected
people shares the same subnet, for ex : 192.168.1.0/24 :
Hi,
As we use an Alix 2d3 board with 3 ethernet interfaces, there is one
free at now : could we use this OPT interface to manage backbone
network, with an address in its subnet 192.168.1.0/24, and put an
address from 192.168.2.0/24 subnet on the LAN interface to serve
clients, provided these
Le Thu, 18 Nov 2010 14:10:18 +0100,
Seth Mos seth@dds.nl a écrit :
Hi,
As we use an Alix 2d3 board with 3 ethernet interfaces, there is
one free at now : could we use this OPT interface to manage backbone
network, with an address in its subnet 192.168.1.0/24, and put an
address
On Thu, Nov 18, 2010 at 12:39 PM, Fred Boiteux fblis...@free.fr wrote:
The different LAN subnets' trafic aren't VLAN tagged, and all traffic
comes from one Ethernet port (from the nearest antenna), so I don't
understand how VLAN could be used there ?
Most carrier-grade radios support tagging
subnets
concurrently on the same VLAN until I can get rid of all the old
addresses.)
-Adam
-Original Message-
From: David Burgess [mailto:apt@gmail.com]
Sent: Thursday, November 18, 2010 13:56
To: support@pfsense.com
Subject: Re: [pfSense Support] how to manage 2 subnets
On Thu, Nov 18, 2010 at 3:11 PM, Adam Thompson athom...@athompso.net wrote:
I think the OP was referring to running two subnets concurrently on the
same wire, something I often have to do for various reasons, sometimes to
solve co-existence issues while renumbering a network. I have no idea
On 11/18/2010 11:16 PM, David Burgess wrote:
On Thu, Nov 18, 2010 at 3:11 PM, Adam Thompson athom...@athompso.net wrote:
I think the OP was referring to running two subnets concurrently on the
same wire, something I often have to do for various reasons, sometimes to
solve co-existence issues
Another easy solution is to just add another nic.
Sent from my iPhone
On Nov 18, 2010, at 2:46 PM, Karsten Becker karsten.bec...@ecologic.eu wrote:
On 11/18/2010 11:16 PM, David Burgess wrote:
On Thu, Nov 18, 2010 at 3:11 PM, Adam Thompson athom...@athompso.net wrote:
I think the OP was
On Thu, Nov 18, 2010 at 3:51 PM, fi...@7technw.com fi...@7technw.com wrote:
Another easy solution is to just add another nic.
Not an option in this case. The OP described a wireless network where
the client subnet and management subnet exist on the same physical
network. You can't change that in
22 matches
Mail list logo
