Peter McCracken ([EMAIL PROTECTED]) scribbled: > I'm looking for some tips to start off creating a specific home > network. My ISP gives me two IPs, I'd like to use one of them for my > desktop, and one for a wireless router (I don't want to put my desktop > behind the router because I don't want to compete with my roommate for > forwarding ports). However, my desktop has two network cards, and I'd > like to also attach my desktop to the router (as net.eth1). Then, I'd > like to configure it so that my desktop knows to use eth1 for any > 192.168.x.x IP, and eth0 for all other internet usage. > > My problem is that I really have no idea what software I should use on > my computer to configure it in this fashion. Can someone give me a hint > on where to start learning?
seems pretty straight forward. If the router hands out addresses by dhcp, configure eth0 as such. eth1, same deal. The trick will be in the routing table. I've modified my routing table to look like what you want: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo 0.0.0.0 <dhcp-set> 0.0.0.0 UG 0 0 0 eth1 When processing a request, the kernel will hit the top line first, if the IP address falls in 192.168.0.x, it will send it out eth0, if it falls in 127.x.x.x, it'll go the the loopback device (stay on localhost), anything that falls through the previous rules goes to the default rule. In this case, it will be sent out eth1 to the default gateway. the default gw is assigned by your ISP. If your net.eth0 and net.eth1 are configured correctly, you shouldn't have to mess with the routing table, it will be set up automagically. the only bugger is that when you get dhcp address via the home router, it will try to assign the default gateway. check the manpage for dhcpcd (client daemon) and see what option you may need to add to the init script... HTH, Cooper. -- [EMAIL PROTECTED] mailing list
