On Fri, Aug 25, 2006 at 08:42:19PM +0200, Geert Stappers wrote: > On Thu, Aug 24, 2006 at 01:36:00PM +0200, Jens Seidel wrote: > > On Thu, Aug 24, 2006 at 11:39:22AM +0200, Geert Stappers wrote: > > > On Thu, Aug 24, 2006 at 12:26:58AM +0200, Jens Seidel wrote: > > > > (please CC: me) > > > > My PC is connected via eth0 with my notebook which itself is connected > > > > (via eth2) > > > > to my router. There is no direct connection to the router. I enter my > > > > notebook as > > > > gateway but cannot specify a nameserver (I have not installed bind). > > > > I would like to use my router as nameserver but this requires a > > > > route add -host <router ip> gw <notebook ip> > > > > which I currently start manually from another console or ssh. > > So > [Inet--Router] )) (( [eth2:Laptop:ethX] --- [eth0:PC] > > Legenda: > > [ ] = "physical device" > )) (( = wireless connection > --- = cable connection > > > post-up route add --host <router> gw <notebook> > > is missing in /etc/network/interfaces, which I add always manually (it's > > Next is how I would configure a netwerk as yours. > > Assume that the router has IP address 192.168.0.1 due default factory > settings and eth2 is 192.168.0.23, which might DHCP assigned. (I try to always avoid DHCP for a small network <5 PCs since this speeds network initialisation up by 3-5 seconds. It's only required for netbooting which most of my hardware does not support.) > Import is that they are in the same IP network. > (In a class C network need the first three octets to match) > > Make ethX 192.168.6.1 and eth0 in the PC 192.168.6.2. > On the PC is 192.168.6.1 configured as his "default gateway. > > You have now two seperate IP networks 192.168.0.0 and 192.168.6.0
> To make it possible that the PC can to the Internet, you have the enable > IP forwarding in the laptop. The command for this is: > > echo 1 > /proc/sys/net/ipv4/ip_forward No, it's no longer so easy. You also have to do on the same host: iptables -t nat -A POSTROUTING -o br0 -j MASQUERADE where br0 is the network device. > (Again: Do that on the _laptop_ ) > > Tell the PC that it's nameserver is 192.168.0.1, your router. Hmm, indeed. Using two distinct networks probably will do what I want. That's also my very old configuration, but since some time I use bridging so that all devices are (locically) in the same network. That's why [eth0:PC] thinks it can reach the router directly without using [eth2:Laptop:ethX]. Maybe I will restore this configuration, thanks. > > > Back to your question: > > > > Is there a fixed IP list of nameservers available? Or maybe a Debian > > > > mirror IP list? > > > > > > Please don't waste your time on typing in IP-addresses. > > > > Would it be so bad to have a fixed IP list in d-i? Remember that DNS server > > are sometimes down (happens approximately twice per year for me for > > short time). > > An outdated (fixed) IP list is much worse then a DNS that _might_ fail. I would not suggest to use it in the installed system, but for the proper system installation from a mirror it may be handy. But I agree that it may not be worth the trouble ... > The ultimate test would be another install where the PC is configured > as: > > IP address = 192.168.6.2 > Netmask = 255.255.255.0 > Gateway = 192.168.6.1 > DNS = 192.168.0.1 I have no doubt that this would work. Thanks, Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
