LinuxQuestions.org - Internet help

[EDIT]
BTW-
Ignore the_tflk's post -- he obviously hasn't read your problem in that you can't ping 192.168.1.1 from 10.10.0.0 when your next hop needs to be 192.168.1.0, and furthermore, doesn't understand basic networking where if you can't ping an IP (such as your router), you certantly won't be able to browse to it using FireFox!
Gah!
[/EDIT]

but only the debian install is having trouble on your dual-boot (i assume)

-- do you want a static ip, or dynamic?
here's a reference for you:
http://www.debian.org/doc/manuals/re...ateway.en.html

--it's long, so i skimmed it and targeted the following for you... let me know if that gets you there...

Quote:

10.5 Configuring network interfaces using DHCP

Low-level configuration of network interfaces can be automated by means of the Dynamic Host Configuration Protocol (DHCP). Your firewall or router box or your broadband ISP may furnish IP addresses and other parameters this way.

To make this work you must install one of the following packages:

* dhcp3-client (version 3, Internet Software Consortium)
* dhcpcd (Yoichi Hariguchi and Sergei Viznyuk)
* pump (Red Hat)

pump is simple and widely used. dhcp3-client is complex but more configurable. [58]
10.6 High level network configuration in Debian

In order to make network configuration easier Debian provides a standard high level network configuration tool consisting of the ifup and ifdown programs and the /etc/network/interfaces file. [59] If you choose to use ifupdown to do your network configuration then normally you should not use low-level commands too. [60] The ifupdown program was written with the intent that it alone be used to configure and deconfigure network interfaces.

To update interface configuration do this:

# ifdown eth0
# editor /etc/network/interfaces # tweak as you wish
# ifup eth0

For more information see interfaces(5), /usr/share/doc/ifupdown/examples/network-interfaces.gz, and ifup(8).
10.6.1 Configuring an interface with a static IP address

Suppose you want to configure an Ethernet interface such that it has a fixed IP address of 192.168.0.111. This address begins with 192.168.0 so it must be on a LAN. Suppose further that 192.168.0.1 is the address of the LAN's gateway to the Internet. Edit /etc/network/interfaces so that it includes a stanza like this:

iface eth0 inet static
address 192.168.0.111
netmask 255.255.255.0
gateway 192.168.0.1

You can configure other aspects of the interface or perform other actions after the interface is brought up or before it is brought down by specifying appropriate commands on "up" and "down" lines.

iface eth0 inet static
address 192.168.0.111
netmask 255.255.255.0
gateway 192.168.0.1
up route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.0.2 dev $IFACE
down route del -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.0.2 dev $IFACE
up echo Interface $IFACE going up | /usr/bin/logger -t ifup
down echo Interface $IFACE Going down | /usr/bin/logger -t ifdown

Alternatively, commands can be inserted into scripts in the /etc/network/if-up.d and /etc/network/if-down.d directories. Such scripts can also implement extended options. See interfaces(5) for details. For example, the resolvconf package includes scripts that allow you to add options specifying DNS information to be included in /etc/resolv.conf while the interface is up:

iface eth0 inet static
address 192.168.0.111
netmask 255.255.255.0
gateway 192.168.0.1
dns-search somedomain.org
dns-nameservers 195.238.2.21 195.238.2.22

The argument somedomain.org of the dns-search option corresponds to the argument of a search option in resolv.conf(5). The arguments 195.238.2.21 and 195.238.2.22 of the dns-nameservers option correspond to the arguments of nameserver options. Other recognized options are dns-domain and dns-sortlist. See Managing nameserver information – resolvconf, Section 10.4.2.
10.6.2 Configuring an interface using DHCP

To configure an interface using DHCP edit /etc/network/interfaces so that it includes a stanza like this:

iface eth0 inet dhcp

In order for this to work you must have installed one of the DHCP clients mentioned in Configuring network interfaces using DHCP, Section 10.5.