LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   How to set up a bridge? (http://www.linuxquestions.org/questions/linux-networking-3/how-to-set-up-a-bridge-204952/)

tlawlessrr 07-14-2004 11:58 AM

How to set up a bridge?
 
I want to set up a network that does not include any Microsoft machines.

The network consists of 2 slackware 10 boxes and 1 Fedora Core 2 box.

We want the fedoa box to be a Domain Controller so that the 2 client machines can authenticate threw it using samba.

Problem is Fedora Box only has 1 nic card.
We have set the nic card so that it is a part of our larger windows network. Only for connecting to the router.
192.168.1.69
192.168.1.1 is its gateway.

And it has an address for our smaller nework.
192.168.3.1
192.168.1.69 is its gateway

Both of our client machines .3.10 and .3.15 have their gateways set to 192.168.3.1

But neither machine can get out threw the router.

What am I doing wrong here?

keefaz 07-14-2004 12:30 PM

Quote:

I want to set up a network that does not include any Microsoft machines.
ok ;)
Quote:

We want the fedoa box to be a Domain Controller so that the 2 client machines can authenticate threw it using samba.
I don't get it, why not use NFS, it is more suitable for unix network.
Quote:

Problem is Fedora Box only has 1 nic card.
Explain me how do you connect the two other PCs to this box as it is already connected to a network and it has just one net card.

tlawlessrr 07-15-2004 07:15 AM

All of these computers are connected to a switch. All the switches are connected to a router.

I would use NFS but I did not know I could use it as a Domain Controller to authenticate users.

We have set the compters nic card so that it has 2 IP addresses so that it is pingable from both networks.

zaphodiv 07-16-2004 04:32 AM

You need to configure the fedora BOX to NAT connections from the 192.168.3 network onto the other network.

Alternativly, if you are using a hardware NAT router as your internet gateway you could give it a netmask of 255.255.0.0 so it will provide a connection for machines in 192.168.x.x and enable packet forwarding on the fedora box without NAT.

tlawlessrr 07-16-2004 06:13 PM

Quote:

Originally posted by zaphodiv
You need to configure the fedora BOX to NAT connections from the 192.168.3 network onto the other network.

Alternativly, if you are using a hardware NAT router as your internet gateway you could give it a netmask of 255.255.0.0 so it will provide a connection for machines in 192.168.x.x and enable packet forwarding on the fedora box without NAT.

The break in my subnet mask stops at the last 0 which differentiates between the portion of the ip that defines the network and the portion that defines the client. My subnet mast is the same on both class C networks
255.255.255.0
192.168.003.*
192.168.001.*
These 2 networks have no need to ever interact with one another. However both networks will need access to the Internet.
The fedora box now has 2 NIC cards and is on both networks. The fedora box can communicate with both networks.

The clients on the Linux network cannot access the clients on the windows network which is they way we want it.

However we are unable to access the Internet.

Here is the current setting for Fedora netconfig

Eth0
192.168.1.69
255.255.255.0
192.168.1.1
ISP DNS IP

Eth1
192.168.3.1
255.255.255.0
192.168.1.1
ISP DNS IP

tlawlessrr 07-16-2004 06:22 PM

Quote:

Originally posted by zaphodiv
You need to configure the fedora BOX to NAT connections from the 192.168.3 network onto the other network.

Alternativly, if you are using a hardware NAT router as your internet gateway you could give it a netmask of 255.255.0.0 so it will provide a connection for machines in 192.168.x.x and enable packet forwarding on the fedora box without NAT.

I re-read your post and I do see what you are saying. You are saying instead of have 2 class C networks should more my zero over and create 1 class B network.

zaphodiv 07-17-2004 10:39 AM

You internet connection is provided by the device which is 192.168.1.1

That device is only going to talk to machines in 192.168.1.x

To allow the 192.168.3.x machines to send packets to and from the internet through 192.168.1.1 you need your fedora box to NAT the traffic so that connections from the 192.168.3.x machines appear to be coming from the fedora box's 192.168.1.69 address.

I re-read your post and I do see what you are saying. You are saying instead of have 2 class C networks should more my zero over and create 1 class B network.

No that's not what I said. Read the words. I suggested a bodge. You could
a) enable packet forwarding on the fedora machine and b) assuming that the 192.168.1.1 device is a hardware NAT router box not a PC configure it so that it's netmask is 255.255.0.0
This will change it's broadcast address but that dosn't matter because it dosn't use it so it should still work. IF 192.168.1.1 is a PC than mixing up subnet like that will cause problems with widows network neighbourhood.


All times are GMT -5. The time now is 12:49 AM.