Announcement

Collapse
No announcement yet.

Howto: Ethernet connection without a GUI

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #61
    Re: Howto: Ethernet connection without a GUI

    When I wrote the howto I did not consider that someone would be using it remotely. Glad you got it worked out.

    Comment


      #62
      Re: Howto: Ethernet connection without a GUI

      bookmarked for use

      needed this all day great post thanks should help a lot

      Comment


        #63
        Re: Howto: Ethernet connection without a GUI

        I seem to be having similar problems with getting (K)Ubuntu net-working on a circa 2003 IBM/Lenovo Netvista machine where I would like to be running Linux.

        Except for deleting the KDE networking manager programs, I think I have followed most of the directions in this thread. The built-in network card works with (UGH!) Microsloth (on a separate HD) but not with Kubuntu 9.10 on another HD.

        I get the temporary IP address in ifconfig with settings for DHCP. My router is set for DHCP and I get a listing for the Linux box (an IP address x.x.x.103) with a MAC address matching the built-in NIC (and another test with an _OLD_ additional NIC card).

        Trying the static configurations still doesn't allow me to connect with my LAN/the internet.

        I cannot ping my router as the false IP address I have cannot reach the router at 192.x.x.x.

        I've been struggling with this for a couple of days now. I can't get anything out of this machine. If I were to try to get output, it would be transcribed from one machine's screen to another on my LAN. USB sticks don't seem to be recognized either (That's a different thread somewhere.)

        I've enjoyed the versatility of (K)Ubuntu for a Linux environment, I just have had problems with machines that didn't like Linux. I hope that this scant outline might provide some point of departure for a solution to my problem.

        Bucky
        --It isn't easy being green.
        Kermit

        Comment


          #64
          Re: Howto: Ethernet connection without a GUI

          Originally posted by buckyjunior
          Except for deleting the KDE networking manager programs, I think I have followed most of the directions in this thread.
          If you don't do that, then the rest of the howto is not going to help. The whole premise of this is to get your network running without a network manager screwing things up.

          Comment


            #65
            Re: Howto: Ethernet connection without a GUI

            Thank you for the reply Detonate.

            I've gone back and deleted the kde-network programs, rebooted, checked all the settings and I'm still not able to connect with my Kubuntu (8.04) Linux box through my router with DHCP. Other machines on my LAN are connected.

            Perhaps my transcription of what I see will help solve my problem.

            ifconfig shows two NICs connected with eth0 with a false IP address.
            Code:
            bucky@localhost:~$ ifconfig -a
            eth0   Link encap:Ethernet HWaddr 00:09:6b:d5:aa:f6
                 inet6 addr: fe80::209:6bff:fed5:aaf6/64 Scope:Link
                 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                 collisions:0 txqueuelen:1000
                 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
            
            eth1   Link encap:Ethernet HWaddr 00:10:4b:6d:68:5f
                 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                 RX packets:122 errors:0 dropped:0 overruns:2 frame:0
                 TX packets:64 errors:11 dropped:0 overruns:0 carrier:0
                 collisions:0 txqueuelen:1000
                 RX bytes:37254 (36.3 KB) TX bytes:7199 (7.0 KB)
                 Interrupt:7 Base address:0x2040
            
            eth0:avahi Link encap:Ethernet HWaddr 00:09:6b:d5:aa:f6
                 inet addr:169.254.10.213 Bcast:169.254.255.255 Mask:255.255.0.0
                 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
            
            eth1:avahi Link encap:Ethernet HWaddr 00:10:4b:6d:68:5f
                 inet addr:169.254.5.105 Bcast:169.254.255.255 Mask:255.255.0.0
                 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                 Interrupt:7 Base address:0x2040
            
            lo    Link encap:Local Loopback
            inet addr:127.0.0.1 Mask:255.0.0.0
            inet6 adddr: ::1/128 Scope:Host
                 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                 RX packets:61 errors:0 dropped:0 overruns:0 frame:0
                 TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
                 collisions:0 txqueuelen:1000
                 RX bytes:5228 (5.1 KB) TX bytes:5228 (5.1 KB)
            Looking at the modified interfaces file, eth0 is set for DHCP as prescribed.
            Code:
            bucky@localhost:~$ cat /etc/network/interfaces
            # network interfaces
            
            # the loopback network interface
            auto lo
            iface lo inet loopback
            address 127.0.0.1
            netmask 255.0.0.0
            
            # the primary network interface
            auto eth0
            iface eth0 inet dhcp
            
            # the secondary network interface
            # auto eth1
            # iface eth1 inet dhcp
            The resolv.conf file is set to external DHCP servers as well as the IP for my router--which is the same as in your example.
            Code:
            bucky@localhost:~$ cat /etc/resolv.conf
            nameserver 192.168.0.1
            nameserver 208.67.222.222
            nameserver 208.67.220.220
            My router is set to serve DHCP addresses and it seems to have located the Linux box's NICs and their MAC addresses.
            [img width=400 height=98]http://home.comcast.net/~p.wehr/gfx/routerDHCP.jpg[/img]

            Restarting the network doesn't seem to be able to locate the router's DHCP server. Bummer.
            Code:
            bucky@localhost:~$ sudo /etc/init.d/networking restart
            sudo: unable to resolve host localhost
            ...
            Listening on LPF/eth0/00:09:6b:d5:aa:f6
            Sending on  LPF/eth0/00:09:6b:d5:aa:f6
            Sending on  Socket/fallback
            ...
            Listening on LPF/eth0/00:09:6b:d5:aa:f6
            Sending on  LPF/eth0/00:09:6b:d5:aa:f6
            Sending on  Socket/fallback
            DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
            DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
            DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
            No DHCPOFFERS received.
            No working leases in persistent database - sleeping.
            And then obviously, my Linux box cannot ping the router or other machines on the LAN.
            Code:
            bucky@localhost:~$ ping -c3 192.168.0.1
            PING 192.168.01. (192.168.0.1) 56(85( bytes of data.
            From 169.254.5.105 icmp_seq=1 Destination Host Unreachable
            From 169.254.5.105 icmp_seq=2 Destination Host Unreachable
            From 169.254.5.105 icmp_seq=3 Destination Host Unreachable
            
            --- 192.168.0.1 ping statistics ---
            3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 20076ms, pipe 3
            As expected, other machines on the LAN and the router get 100% packet loss trying to find the Linux box.

            Obviously, I've done something wrong or am missing some detail here.

            Perhaps it's my karma. High overcast, mid 50s. I should be out planting my garden or up the Poudre fishing.

            Thanks for helping to solve my network problem.
            Bucky

            "And don't tell me there isn't one bit of difference between null and space, because that's exactly how much difference there is. :-)" -- Larry Wall

            Comment


              #66
              Re: Howto: Ethernet connection without a GUI

              What do you have in /etc/hosts

              Comment


                #67
                Re: Howto: Ethernet connection without a GUI

                Detonate.

                the /etc/hosts file.
                Code:
                127.0.0.1  ibm/a0a5d118e94
                
                # the following lines are desirable for IPv6 capable hosts
                ::1 ip6-localhost ip6-loopback
                fe00::0 ip6-localnet
                fe00::0 ip6-mcastprefix
                fe02::1 ip6-allnodes
                fe02::2 ip6-all-routers
                fe02::3 ip6-allhosts
                192.168.0.1 DI-524
                Hmmm. I would speculate but I'm really in a foreign land here.

                Bucky

                Comment


                  #68
                  Re: Howto: Ethernet connection without a GUI

                  First, I would recommend disabling ipv6.

                  A search on this, or on the Ubuntu forum will tell you how to do this. I think that may be your problem.

                  Comment


                    #69
                    Re: Howto: Ethernet connection without a GUI

                    Originally posted by buckyjunior
                    bucky@localhost:~$ sudo /etc/init.d/networking restart
                    sudo: unable to resolve host localhost
                    ...
                    Surely you need to have (at least) localhost defined in your /etc/hosts file

                    Comment


                      #70
                      Re: Howto: Ethernet connection without a GUI

                      Adding localhost to the /etc/hosts file, 127.0.0.1 seems to be now recognized as localhost.

                      As per http://kubuntuforums.net/forums/inde...opic=3108234.0 followed by the link to disable ipv6 at http://www.webupd8.org/2009/05/how-t...tu-jaunty.html, I set about to disable ipv6.

                      I get a response that the file
                      Code:
                      /proc/sys/net/ipv6/conf/all/disable_ipv6
                      does not exist.

                      Editing
                      Code:
                      /boot/grub/menu.lst
                      and rebooting does not change anything. The file still doesn't exiist and I'm still not able to connect. I still get a self-generated IP address instead of the router suggested address.

                      I'm certainly at a loss.

                      Bucky
                      --
                      How can you have any pudding if you don't eat your meat?

                      Comment


                        #71
                        Re: Howto: Ethernet connection without a GUI

                        Try rebooting your router. Turn it off. Leave it off for a few minutes. Turn it back on. Then see if you get a dhcp offer from the router.

                        Comment


                          #72
                          Re: Howto: Ethernet connection without a GUI

                          Detonate,

                          Don't you ever sleep, or eat? You always seem to be here.

                          I rebooted the router which wiped out the references to the MAC addresses associated with the hardware on the Linux box.

                          A quick ping from the Linux box turned up nothing.
                          Restarting the network--again didn't receive any DHCPOFFERS from my router.

                          Is there something about
                          DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval (number varies)
                          ?

                          Isn't it supposed to be looking to my defined DHCP server/gateway? 192.168.0.1.
                          The $ff.ff.ff.ff seems like a mask to either nowhere or anywhere. This is getting deeper into unknown territory for me.

                          Do you think another distribution (not Debian based) might have some antique network routines that would better recognize my ~2002 vintage NIC card and router from probably the same era?

                          Or in your experience, are the possibilities narrowing toward a solution?

                          Bucky
                          Tools that follow standards NOT Standard tools - K.Prager

                          Comment


                            #73
                            Re: Howto: Ethernet connection without a GUI

                            For information only.

                            I've given up trying to get Linux to play nice with the NIC on the old IBM/Linovo desktop. My guess is that it may need proprietary drivers. Drivers that work are apparently included in the Windoze installation.

                            My (less than optimal) solution to meet my current needs is to run Virtual Box on the original XP disk and install Kubuntu on that. The NIC does all the things is it supposed to do through Virtual Box.

                            Thanks for trying folks.

                            Bucky

                            Comment


                              #74
                              Re: Howto: Ethernet connection without a GUI

                              Also for information and to say a big THANKS to you, Detonate!

                              I didn't see any eth0 when I ran ifconfig but I did see lo.

                              I went ahead and followed your guide.

                              Happily I have a working wired connection again! I'm using 10.04, Lucid Lynx also.

                              I'm still puzzled as to how the connection got lost but I have your excellent fix to refer to now.

                              Many thanks from a UK Linux noob.
                              Beanpod, anyone?! www.Beanpods.co.uk

                              Comment


                                #75
                                Re: Howto: Ethernet connection without a GUI

                                Happy to be of help. Great you got it working!!

                                Comment

                                Working...
                                X