On Jul 5, 2010, at 5:59 PM, Steve Bertrand wrote:
On 2010.07.05 12:57, David Kelly wrote:
On Mon, Jul 05, 2010 at 10:16:19AM -0600, Modulok wrote:
Criteria:
- HostA must never directly talk to HostB.
- Both hostA and hostB have an Internet connection.
What I have to work with:
proC
On 2010.07.05 12:57, David Kelly wrote:
> On Mon, Jul 05, 2010 at 10:16:19AM -0600, Modulok wrote:
>>
>> Criteria:
>> - HostA must never directly talk to HostB.
>> - Both hostA and hostB have an Internet connection.
>>
>> What I have to work with:
>> proCurve switch which supports VLANs
On 2010.07.05 14:36, Nathan Vidican wrote:
> On Mon, Jul 5, 2010 at 1:30 PM, Modulok wrote:
>
>> It was a simplified diagram of what I thought I needed. ( Which may or
>> may not be what I actually need! )
>>
>> Basically, I want a port on the switch that I can plug un-trusted
>> devices into. Sy
On Jul 5, 2010, at 12:30 PM, Modulok wrote:
> It was a simplified diagram of what I thought I needed. ( Which may or
> may not be what I actually need! )
>
> Basically, I want a port on the switch that I can plug un-trusted
> devices into.
Seconding Peter's request that you not top-post. We re
On Mon, Jul 5, 2010 at 1:30 PM, Modulok wrote:
> It was a simplified diagram of what I thought I needed. ( Which may or
> may not be what I actually need! )
>
> Basically, I want a port on the switch that I can plug un-trusted
> devices into. Systems wich are known to be just crawling with
> mali
On 5 jul 2010, at 19:30, Modulok wrote:
> It was a simplified diagram of what I thought I needed. ( Which may or
> may not be what I actually need! )
>
> Basically, I want a port on the switch that I can plug un-trusted
> devices into. Systems wich are known to be just crawling with
> malicious
It was a simplified diagram of what I thought I needed. ( Which may or
may not be what I actually need! )
Basically, I want a port on the switch that I can plug un-trusted
devices into. Systems wich are known to be just crawling with
malicious software. I need to provide them with an Internet
conn
On 5 jul 2010, at 18:16, Modulok wrote:
> Hopefully this doesn't get too garbled by various mail clients:
>
> Internet
> |
> FreeBSD router
> |
> (tagged frames)
> |
> switch
> ||
> vlan1 vlan2
> ||
> hostAhostB
>
> Criteria:
>- HostA must never directly t
On Mon, Jul 05, 2010 at 10:16:19AM -0600, Modulok wrote:
>
> Criteria:
> - HostA must never directly talk to HostB.
> - Both hostA and hostB have an Internet connection.
>
> What I have to work with:
> proCurve switch which supports VLANs.
> 2x Intel NICs in FreeBSD which support
Hopefully this doesn't get too garbled by various mail clients:
Internet
|
FreeBSD router
|
(tagged frames)
|
switch
||
vlan1 vlan2
||
hostAhostB
Criteria:
- HostA must never directly talk to HostB.
- Both hostA and hostB have an Internet connectio
10 matches
Mail list logo
