To tell the DHCP server to use eth1, add the line
to /etc/default/dhcp3-server.Code:INTERFACES=eth1
The interface assignment does not happen in dhcpd.conf. It is a command-line parameter so it is controlled by the file in /etc/default.
Printable View
To tell the DHCP server to use eth1, add the line
to /etc/default/dhcp3-server.Code:INTERFACES=eth1
The interface assignment does not happen in dhcpd.conf. It is a command-line parameter so it is controlled by the file in /etc/default.
I think I might not be explaining myself correctly. Sorry darkod for the noobness lol well the eth0 is connected to a router which is also the modem that gives me internet. The eth1 is going to give internet to the clients. That is my ultimate goal. I actually got the DHCP to work but had the wrong config so that would explain why the internet would not work. I need to keep making some configs but now my internet is gone completely from eth0 so now I have to figure that out as well.
Seiji...
Thank you for the help and I have done that already it worked, thanks again. The issue I'm having is that the clients are not receiving internet. There is a connection established but it does not give out a internet connection. But that was great info...thanks again!
Hi lestertorres,
It looks to me like you have 3 problems here;
1/ No internet access on your "server" via eth0
2/ DHCP is not serving to your clients on eth1
3/ The server is not routing traffic from eth1 to eth0 (although that may be working but you can't tell as the other 2 things are broken.
You need to solve these 1 at a time.
For 1/
can you ping your router?
can you ping the internet (using and IP address)
can you ping the internet (using a dns name)
I would bring down eth1 for the time being and get the net working again first.
OK, if the clients have no internet, the order in which I would check things is:
1. On any clients try ping 8.8.8.8 to see if you really have no internet or it's only a DNS problem.
2. If there is no reply, first check whether internet on the server is working. If it's not, try pinging the router IP. On the server's eth0 we used 192.168.1.93 but are you sure that can work with the router? And does the router have the 192.168.1.1 IP or another one?
3. If internet on the server is working, check the forwarding configuration you did, the ip_forward enabled in /etc/sysctl.conf and the iptables MASQUERADE rule. Remember they are needed if you want the server to be able to forward packets between eth0 and eth1.
TheMightyGirth...
1) Yes I can ping the router using 192.168.1.93
2) I cannot ping the internet using an IP address using 199.181.132.250 for espn. It states the destination host unreachable.
3) I cannot ping the dns using 8.8.8.8 it says the destination host unreachable as well.
I tried bringing down eth1 but it said it was not configured. I went back to interfaces and # on all eth0 and did a network restart, then reboot and still got no wired connection to the internet through eth0.
Darkod...
1) When I did a ping I did get a response so it has to be a DNS config problem.
2) I honestly do not think that eth0 192.168.1.93 can work with the router because that is the address I have for eth0. The router at this time does not have 192.168.1.1 but if I recall when I had on there 10.10.10.1 it might have worked.
3) In the sysctl.conf file I do have net.ipv4.ip_forwarding=1 active but I do not see a section where it states MASQUERADE. Should I add that line somewhere in there?
Can you post the results of pinging the router?
Also, don't comment out with # the eth0 interface. If you do, it will not work definitely. Leave it as it is configured with 192.168.1.93 and post the ping results.
PS VERY IMPORTANT: What address does the router have? This is very important and you need to know it, you can't just invent IPs. Using the 192.168.1.93 for the eth0 interface and the 192.168.1.1 as gateway was under the assumption the router is 192.168.1.1. If it isn't, of course the server will not have working internet access.
I put the address 192.168.0.1 for the router being that it is a netgear and I found out that is the typical address for the router.Quote:
ping 192.168.0.1
ping 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
From 192.168.1.50 icmp_seq=1 Destination Host Unreachable
^C
--- 192.168.0.1 ping statistics ---
7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6031ms pipe 3
I am going to give in and nuke the pc and just start again from scratch :(. I do want to thank everyone that has helped me and ubuntu is great...i just need to figure it out more. I am only on my third week using ubuntu and i really like it. Thanks everyone.