RE: [Netpass-users] Network Arch Opinions/Questions

[White, S. P. <wh...@um...>]

On our core router/switch you can create a VLAN with no IP address, so =
here is how I will handle this when/if we implement netpass. (assuming =
my understanding of its mechanisms is complete.)

Create the actual vlan with a router interface, IP address, and default =
gateway of X.

the quarrantine VLAN you would create with no router interface and put =
the default gateway IP on the quarrantine card of the netpass box. We do =
this all the time when we want a firewall or smaller router to be the =
default gateway of a particular network.

take care,

Steve

-----Original Message-----
From: net...@li... on behalf of Don Rugh
Sent: Fri 8/12/2005 7:51 AM
To: net...@li...
Subject: Re: [Netpass-users] Network Arch Opinions/Questions
=20
..quick questions about the nic described below, with all the VLANs =20
on it: does each vlan have it own subnet to it?? and does each subnet =20
have an IP address on the NP server nic??

The reason I'm asking -- looks like there may be an issue on our core =20
that we cannot assign a 2 vlans to the same subnet (won't let us put =20
the same subnet router on 2 vlans), which is causing us some problems =20
at the moment -- but assigning an address for each subnet to the NP =20
server nic would solve this problem....thought, opinions?

Thanks,
Don

On Jun 21, 2005, at 1:46 PM, Jeff Murphy wrote:

>
>
>> I think we're leaning towards central servers, so the two VLANs from
>> each building would be directed back to the core, and the core ports
>> for the NP servers would be tagged with _all_ the VLANs, 10 in this
>> case. Things get a little fuzzy here -- those 10 VLANs would then
>> also have to be defined on each server, so that they could be members
>> of each VLAN, correct?
>>
>
> if you use 2 servers you'll either need to manually split the =20
> config in
> half or use a load balancer (e.g. www.linuxvirtualservers.org)
>
> in either case, you can use interfacecfg.pl to spit out the =20
> appropriate
> ifconfig commands to bring up all of the interfaces.
>
> then your server(s) will have 5-10 interfaces (depending on what =20
> sort of
> LB design you go with).
>
> we might need to examine interfacecfg.pl if you are doing a non-LVS
> deployment, as we've written it with the expectation that you are =20
> doing
> an LVS deployment.
>
> you eventually wind up with something like:
>
> % ip link
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> 4: sit0: <NOARP> mtu 1480 qdisc noop
> 5: eth1.813: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> 6: eth1.13: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> 7: eth1.812: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
> 8: eth1.12: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>
>
>
> our production NP servers have ~53 interfaces (2 physical) configured.
>
> jeff
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
> _______________________________________________
> Netpass-users mailing list
> Net...@li...
> https://lists.sourceforge.net/lists/listinfo/netpass-users
>



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle =
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & =
QA
Security * Process Improvement & Measurement * =
http://www.sqe.com/bsce5sf
_______________________________________________
Netpass-users mailing list
Net...@li...
https://lists.sourceforge.net/lists/listinfo/netpass-users