On Sat, Apr 06, 2002 at 01:30:25PM -0800, Brian W. Carver wrote:
> I boot up and first thing I type: ifconfig
> I get:
>
> eth1 Link encap:Ethernet HWaddr 00:C0:F0:56:2E:E9
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqeuelen:100
> Interrupt:9 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqeuelen:0
>
> So eth0 is not UP. Then I type: ifconfig eth0 up
> and then I type: ifconfig
> and I get:
>
> eth0 Link encap:Ethernet HWaddr 00:20:78:E0:00:8A
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:7 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqeuelen:100
> Interrupt:10 Base address:0x1800
>
> eth1 Link encap:Ethernet HWaddr 00:C0:F0:56:2E:E9
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:19 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqeuelen:100
> Interrupt:9 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:8 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqeuelen:0
>
> So, as you can see, eth0 is NOT assigned an inet addr:
>
> As a result, I have no internet connection.
> This is particularly frustrating because it was on the internet just
> fine the other evening. I didn't purposely change anything, but now the
> internet connection is lost.
>
> I've taken all the advice I've gotten so far, but I'm still not online.
> Here's my files for scrutiny. Thank you so much for any help!
> -----
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> iface lo inet loopback
>
> #first network card connected to isp
> auto eth0
> iface eth0 inet dhcp
>
> #network card connecting to the local network
> auto eth1
> iface eth1 inet static
> address 192.168.0.1
> netmask 255.255.255.0
>
> -----
>
> # /etc/dhcpd.conf
I am assuming the following:
1) You have a home network, and eth0 and eth1 are two network cards on
the gateway machine. eth0 is the interface connecting to your ISP.
2) Your gateway machine is unable to establish a connection with your
ISP's dhcp server - simply put, your gateway is without internet access.
This file (dhcpd.conf) is really for the dhcp server (d as in daemon). Unless I
misunderstood my DHCP setup, this file has little to do with having
access on your gateway machine - the one with eth0 and eth1 interfaces.
Are you using sid, woody or potato?
You should post the /etc/dhcp3/dhclient.conf (location on sid) - this file
deals with your dhcp lease as far as your ISP goes.
Andy
> #
> # Brian's configuration file for ISC dhcpd
> #
> # April 4 2002
> # option definitions common to all supported networks...
> # Change domain-name to your domain name. I just preceeded my ISP with
> # the name of my Linux computer. Someone suggested not doing that 4-6-02
>
> option domain-name "charterpipeline.com";
>
> # The domain-name-servers you enter here will be used by all other
> # computers on your LAN. They are ip addresses of your ISP's.
> # Someone suggested it be 192.168.0.1, so I put it first. 4-6-02.
> option domain-name-servers 192.168.0.1, 24.205.1.62, 24.205.1.14,
> 24.205.192.36;
>
> # This just tells all the other computers that you're a Class C network.
>
> # If you're using the 192.168.x.x address, you're Class C. Don't change
> # the IP address for this. It really should be 255.255.255.0
> option subnet-mask 255.255.255.0;
>
> # I went with the default lease times. I guess they could be longer.
> default-lease-time 600;
> max-lease-time 7200;
>
> # These next two are important. They are your primary computer, I think.
>
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.1;
>
> # Here's where you set up your range of Dynamic IP Addresses. I set mine
>
> # for 10 because I don't honestly think I'll have more than 10 computers
>
> # hooked up. It is in this range that your Laptop will have an IP
> Address
> # of. You could certainly set it to a range of 100-255 if you want,
> # reserving the first 100 IPs for Static.
> # Someone suggested it is customary for clients to be 3 digits
> # hence the 100-200 range. 4-6-02.
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.100 192.168.0.200;
> }
>
> # The host fields below are the names of your computers.
> #
> # When you do a winipcfg on your Windows boxen, the MAC Address is the
> # hardware address given here. The fixed address is the Static IP you
> want
> # to assign to that computer.
> # You don't need an entry here for your "server" computer because it is
> # set up in the /etc/network/interfaces file.
> host JSDESKTOP {
> hardware ethernet 00:A0:CC:76:76:AB;
> fixed-address 192.168.0.2;
> }
>
> host LAPTOP {
> hardware ethernet 00:E0:98:73:5E:F7;
> fixed-address 192.168.0.3;
> }
>
> host JSLAPTOP {
> hardware ethernet 00:00:00:00:00:00;
> fixed-address 192.168.0.4;
> }
>
> ## eof
>
> --
> Brian W. Carver
> brianwcarver at yahoo dot com
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
