Re: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- From: "David" <david.goodyear@xxxxxxxxx>
- Date: 25 Nov 2006 15:19:31 -0800
David wrote:
Hi all,
Im trying to use Gentoo linux, to connect two networks.
Net 1 is served to be 192.168.1.*
Net 2 is served to be 192.168.2.*
I want server 192.168.1.1 to reach 192.168.2.1 to only communicate with
a Microsoft SQL Server via TCP/IP. What should I look for.
Orignally I went with moving everything, into 192.168.1.1 - 50 for Net
1, then 192.168.1.100-51 for Net 2. I figured then I could bridge with
a firewall. However, the linux box, on getting the two ips, using dhcp,
does not then know where to route the packets?
Is there an easy way, if possible gentoo tutorials on setting this up
available, so that 192.168.1.1 can communicate only with 192.168.2.1
passing through a gentoo computer, with a seperate NIC for each
network.
Also does anyone know if you can do this for MS-SQL Server,by opening
up a specific port? What are my options please help, this is now
driving me insane.
Thanks
David
This might explain it better, as i wrote it a while ago while still
clear headed:
Hi all,
We have two networks:
a) 192.168.1.*
b) 192.168.2.*
We want to bridge them so that Microsoft SQL Server via TCP-IP can go
from a computer on a) to one on b). Ive been looking at etables and
iptables, and am not sure what would fullfill the purpose best. Has
anyone done this, or have any suggestons. We dont want windows file
sharing, named pipes, DNS, DHCP to transerse between the bridges. Can
this be done, do we need to bring them into the same 192.168.* range,
for it to work? Each network is connected via a seperate network card
to the gentoo linux box, ideally via these it would be good to ssh into
it. If not I guess this can be done with a spare network card?
Thanks in advance
David
.
- Follow-Ups:
- Re: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- From: Jeroen Geilman
- Re: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- References:
- Prev by Date: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- Next by Date: Re: weird iptables behaviour
- Previous by thread: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- Next by thread: Re: Joining 192.168.1.* to 192.168.1.* with filtering for only MS SQL Server?
- Index(es):
Relevant Pages
|