Re: Hooking 2 Networks
Hooking is illegal in the USA. Even over networks. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hooking 2 Networks
Thats why the call it 'escorting' :) On Mon, 3 Mar 2003, northern snowfall wrote: Hooking is illegal in the USA. Even over networks. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hooking 2 Networks
Thats why the call it 'escorting' :) Hahaha, I spat out some pepsi when I read that Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Hooking 2 Networks
As long as it wasnt out ur nose - cool :) On Mon, 3 Mar 2003, northern snowfall wrote: Thats why the call it 'escorting' :) Hahaha, I spat out some pepsi when I read that Don To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Hooking 2 Networks
Subject: Hooking 2 Networks
I have two separate connections to the Internet with static
IPs and two separate networks. Each network has an internal
FBSD Gateway/NAT/caching DNS connected to the backbone
each have a separate LAN subnet (192.168.0.x on one and
10.0.0.x on another). The default router for each LAN is
its internal Gateway machine, so they know which GW to use
to get out to the Net. Each also operates web mail
servers. Each have their own switches from the Gateway
machine cabled to the servers/workstations.
This is possible and easy, it will however become a problem
if your machines are getting thier ip addresses via DHCP.
There may be a better way. (see below)
You may find it more conveinient to attach one box to both
networks. The most simple solution would be to attach both
gateways to both networks. But dont attach the networks
together. Doing it this way avoids cable usage, and ethernet
broadcasts dont have to be advertized on both networks.
You also will not have to worry about setting up a specific
routes on each client. And because both routers will have
addresses on both networks they will auto-forward packets
between the two networks.
The following is my idea of what your network looks like
now:
{192.168.0.0}--[freebsd gateway]--{internet conn1}
(10.0.0.1}--[freebsd gateway]--{internet conn2}
And what you want to do would be the following:
{192.168.0.0}--[freebsd-gateway]--{internet conn1}
(link)
{10.0.0.0}--[freebsd gateway]---{internet conn2}
This will simplify the number of hops between the boxes
and you will get much higher speeds. And if you attach
the two FreeBSD boxes to both networks, you can still
safely use DHCP for providing IP addresses to the
clients.
I would like to hook the two networks together via the
switches I assUme I do this by running a cable from
the one switch to the uplink on the other???
Is my assumption correct?
Yes, this will work, but you may want to simply attach
both gateways to the two networks.
I would like to have all machines have direct fast
access via the internal NW cables for NFS access.
Attaching both unix boxes to both networks will solve
this for you.
As simple as this sounds, I have not found anything
anywhere about hooking 2 networks together and if
there is any problems. Guess I could just hook up
and try it, but rather double-check with some one
who has a similar setup -- or point me to a URL
(I've googled, visited the networking and router sites
- none talk about directly hooking 2 NWs).
Appreciate any replies. thanks!
No problem, let us know if you wish to continue this.
Lots of people on this list can provide good advise.
(better than me in many cases)
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
RE: Hooking 2 Networks
At 11:00 AM 3.1.2003 -0800, Aaron Burke wrote:
Subject: Hooking 2 Networks
I have two separate connections to the Internet with static
IPs and two separate networks. Each network has an internal
FBSD Gateway/NAT/caching DNS connected to the backbone
each have a separate LAN subnet (192.168.0.x on one and
10.0.0.x on another). The default router for each LAN is
its internal Gateway machine, so they know which GW to use
to get out to the Net. Each also operates web mail
servers. Each have their own switches from the Gateway
machine cabled to the servers/workstations.
This is possible and easy, it will however become a problem
if your machines are getting thier ip addresses via DHCP.
There may be a better way. (see below)
Each machine has static internal IPs and listed in the /etc/hosts so
finding them is easy.
You may find it more conveinient to attach one box to both
networks. The most simple solution would be to attach both
gateways to both networks. But dont attach the networks
together. Doing it this way avoids cable usage, and ethernet
broadcasts dont have to be advertized on both networks.
You also will not have to worry about setting up a specific
routes on each client. And because both routers will have
addresses on both networks they will auto-forward packets
between the two networks.
The following is my idea of what your network looks like
now:
{192.168.0.0}--[freebsd gateway]--{internet conn1}
(10.0.0.1}--[freebsd gateway]--{internet conn2}
And what you want to do would be the following:
{192.168.0.0}--[freebsd-gateway]--{internet conn1}
(link)
{10.0.0.0}--[freebsd gateway]---{internet conn2}
How did you link the two machines? I have 2 NICs in each box - 1 for
external and 1 for internal.
This will simplify the number of hops between the boxes
and you will get much higher speeds. And if you attach
the two FreeBSD boxes to both networks, you can still
safely use DHCP for providing IP addresses to the
clients.
I would like to hook the two networks together via the
switches I assUme I do this by running a cable from
the one switch to the uplink on the other???
Is my assumption correct?
Yes, this will work, but you may want to simply attach
both gateways to the two networks.
I would like to have all machines have direct fast
access via the internal NW cables for NFS access.
Attaching both unix boxes to both networks will solve
this for you.
As simple as this sounds, I have not found anything
anywhere about hooking 2 networks together and if
there is any problems. Guess I could just hook up
and try it, but rather double-check with some one
who has a similar setup -- or point me to a URL
(I've googled, visited the networking and router sites
- none talk about directly hooking 2 NWs).
Appreciate any replies. thanks!
No problem, let us know if you wish to continue this.
Lots of people on this list can provide good advise.
(better than me in many cases)
Just have those two questions above inline. thanks again.
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
RE: Hooking 2 Networks
Each machine has static internal IPs and listed in the
/etc/hosts so finding them is easy.
You dont have to worry about this. It should be fine that
they are in hosts.
(snip)
{192.168.0.0}--[freebsd-gateway]--{internet conn1}
(link)
{10.0.0.0}--[freebsd gateway]---{internet conn2}
How did you link the two machines? I have 2 NICs
in each box - 1 for external and 1 for internal.
In my case I just an other ethernet card.
Which would bring the total number of network cards to 3
instead of 2. This unfortunatly means that (with this
plan) you would need an other network connection between
the two machines.
Assume the following:
FreeBSD Machine on 192.168.0.0
ethernet to 192.168.0.0
ethernet to FreeBSD Machine 10.0.0.0
internet connection
FreeBSD Machine on 10.0.0.0
ethernet to 10.0.0.0
ethernet to FreeBSD Machine 192.168.0.0
internet connection
And you can buypass a hub/switch by using a
cross-over cable. A cross over cable is simply
an ethernet cable that maps outbound (TX RX)
to incomming (RX TX).
Just have those two questions above inline. thanks again.
Well, I seem to have answered at least one, whats the
other question?
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
RE: Hooking 2 Networks
At 01:13 PM 3.1.2003 -0800, Aaron Burke wrote:
Each machine has static internal IPs and listed in the
/etc/hosts so finding them is easy.
You dont have to worry about this. It should be fine that
they are in hosts.
(snip)
{192.168.0.0}--[freebsd-gateway]--{internet conn1}
(link)
{10.0.0.0}--[freebsd gateway]---{internet conn2}
How did you link the two machines? I have 2 NICs
in each box - 1 for external and 1 for internal.
In my case I just an other ethernet card.
Which would bring the total number of network cards to 3
instead of 2. This unfortunatly means that (with this
plan) you would need an other network connection between
the two machines.
Assume the following:
FreeBSD Machine on 192.168.0.0
ethernet to 192.168.0.0
ethernet to FreeBSD Machine 10.0.0.0
internet connection
FreeBSD Machine on 10.0.0.0
ethernet to 10.0.0.0
ethernet to FreeBSD Machine 192.168.0.0
internet connection
And you can buypass a hub/switch by using a
cross-over cable. A cross over cable is simply
an ethernet cable that maps outbound (TX RX)
to incomming (RX TX).
Just have those two questions above inline. thanks again.
Well, I seem to have answered at least one, whats the
other question?
No, this answers my questions. The need for the 3rd NIC was what I really
wanted to confirm. And, your cross-over cable makes sense to bypass a
need for switch or hub. I like this.
Thanks for the help
Best regards,
Jack L. Stone,
Administrator
SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
