View previous topic :: View next topic |
Author |
Message |
soroh6 Apprentice


Joined: 07 Nov 2002 Posts: 232
|
Posted: Tue Jan 16, 2007 12:28 pm Post subject: Home Network + Dnsmasq, Only One Lan Computer Gets Internet? |
|
|
I recently installed a 3rd network card into my server, so that I could connect 2 computers up to my server computer which works as a NAT/router box.
However upon completing the installation of the card, and changing some necessary settings, only one computer is able to get internet access for some reason. Both computers connect to the server with crossover cables, I use dnsmasq to serve dhcp to the connecting clients (my 2 computers), the one that gets internet seems to come online right away and dhcp seems to be working normally, the one that doesn't, it just sits there trying to get an IP, I see in the logs that dnsmasq is offerring it the right IP, but then it (the connecting computer) just times out, it receives the IP that dnsmasq offered it but the connection is limited, can't access the internet or anything, can't even ssh to the dnsmasq box.
But all works well from the other client computer.
The way it's setup is eth0 = 192.168.0.1 on the server, and eth1 = 192.168.0.2, eth2 = dhcp. dnsmasq serves dhcp to eth0 & eth1
What I'm wondering is if anyone could supply me an up to date /etc/conf.d/net for this scenario (mine is out-dated and I really don't seem to grasp the new format of this file), and if anyone else knows what might be causing only 1 client computer to be able to connect fully.
I'll be around to answer any questions.. thanks in advance. _________________ :: soroh -*~ |
|
Back to top |
|
 |
Paczesiowa Guru

Joined: 06 Mar 2006 Posts: 593 Location: Oborniki Śląskie, Poland
|
Posted: Tue Jan 16, 2007 3:04 pm Post subject: |
|
|
you cant have 2 computers connected with ip addresses from the same subnet but different network cards. server has eth0 in route tables to reach computers in 192.168.0.* and doesn't know it should use the other card for that one computer. u can do 3 things:
1)bridge interfaces (the best option but a bit complicated to set up)
2)static route (but it's stupid and hard to maintain)
3)give these interfaces ip's from different subnets (the easiest option)
just give eth0 192.168.0.1 and eth1 192.168.1.1 and modify dnsmasq to server ip and dns at both interfaces and to give appropriate ips to other computers (eg. 192.168.0.2 first computer and 192.168.1.2 second) |
|
Back to top |
|
 |
soroh6 Apprentice


Joined: 07 Nov 2002 Posts: 232
|
Posted: Tue Jan 16, 2007 3:08 pm Post subject: |
|
|
Hey thanks, that sounds great (the 3rd option). I'll look into bridging the connections as well, as that's a bit out of the scope of this post I suppose, and surely there's tons of stuff around about doing it in linux It makes sense that it should work then once I get home from work to test it out.
Ideally I do want them to be in the same subnet.. 192.168.0.x, but whatever for now. _________________ :: soroh -*~ |
|
Back to top |
|
 |
Paczesiowa Guru

Joined: 06 Mar 2006 Posts: 593 Location: Oborniki Śląskie, Poland
|
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|