Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok, so here's my question...I'm pretty new to linux so please bare with me. I'm curently running Debian which was installed at my friends house. We got working and on the inernet, but now when I plug it in here, It won't resolve to my ip. I've tried to run dhcpcd and I get nothing...
Is their something else I can try??
That's the thing....that ip ain't mine....that's why I want to change it to my own and having problems
I have a linksys router...as for my network settings, my ip address is assiged by my dhcp server and the main gateway is 192.168.1.1
My main OS is windowsXP. On my other pc (which I can't get online)....debian and winXP
It's easier to use static IP settings within your home network.... Linksys can be a pain in the butt. Open up a terminal and try to ping your router - if you can ping the router, (192.168.1.1) then you are all set. Open up a browser, hopefully firefox, and ctrl-l your way to 192.168.1.1 - I dont know if you have messed with the configuration in your router or if this is something you have considered but make sure you can get to the router first. Then get out on the net.
I dont know what kind of network configurations tools you have available on debian, but it would seem that you have found the correct place to look that up.
I run Fedora Core 2 - Good luck.
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!
but only the debian install is having trouble on your dual-boot (i assume)
--it's long, so i skimmed it and targeted the following for you... let me know if that gets you there...
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. 
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.  If you choose to use ifupdown to do your network configuration then normally you should not use low-level commands too.  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:
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
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:
The argument somedomain.org of the dns-search option corresponds to the argument of a search option in resolv.conf(5). The arguments 18.104.22.168 and 22.214.171.124 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.