hello, for automatic configuration my recommendation is (if you have a router or a modem/router who work with dhcp services): in your /etc/network/interfaces only stay this: auto lo iface lo inet loopback next.. you open a terminal and put this: sudo dhclient eth0 if you will have an ip, it's ok. next ping <a href="http://www.google.com.ar">www.google.com.ar</a> regards! christian <div class="gmail_quote">2009/1/21 Leonard Chatagnier <<a href="mailto:lenc5570@sbcglobal.net">lenc5570@sbcglobal.net</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> --- On Wed, 1/21/09, Bas Roufs <<a href="mailto:basroufs@gmail.com">basroufs@gmail.com</a>> wrote: > From: Bas Roufs <<a href="mailto:basroufs@gmail.com">basroufs@gmail.com</a>> > Subject: Re: Is it possible to manually activate an eth0 connection? > To: "Ubuntu user technical support, not for general discussions" <<a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a>> > Cc: "Kubuntu Help and User Discussions" <<a href="mailto:kubuntu-users@lists.ubuntu.com">kubuntu-users@lists.ubuntu.com</a>> > Date: Wednesday, January 21, 2009, 6:08 AM > Dear Everybody > > Thanks for all your useful advise so far. However, I still > get stuck > in my attempts to connect my laptop to the internet. In > this message, > I summarise how recent advises from some amongst you worked > out in the > case of Kubuntu 8.10 at my laptop - a Medion 5400, 40 GB, > Pentium 4/ > 2,5 Ghz processor. > > I start with the file /etc/network/interfaces. > > > > auto lo > > > iface lo inet loopback > > > > modify the file to include _only_ those two lines. You > can comment out > > the rest by placing a # in front if you wish: > > > > # auto eth0 > > # iface eth0 inet static > > # address 192.168.1.20 > > # netmask 255.255.255.0 > > # gateway 192.18.1.1 > > > > or delete them. It does not matter. > > After carrying out this advise in at least 2 ways, I did > not manage > any more to ping my router (192.168.1.254) and desktop > (192.168.1.33). > The 'destination host' was in both cases > 'unreachable', according to > the Unix terminal feedback. Also an attempt to ping an > external > website ended up in an 'unknown host' feedback. > > That's why I have re-edited etc/network/interfaces back > to as it was > at the 19th of January: > > auto eth0 > iface eth0 inet static > address 192.168.1.20 > netmask 255.255.255.0 > gateway 192.168.1.254 > > After saving the file re-edited like this, I manage again > to "ping" > the router and desktop. The terminal test feedbacks were > again like > those in the alinea after this one. "^C" = the > control-C command meant > to manually stop the 'ping' process. (Thanks for > that idea, NoOp!) > > bas@Viaconsensus2:~$ ping 192.168.1.254 > PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. > 64 bytes from <a href="http://192.168.1.254" target="_blank">192.168.1.254</a>: icmp_seq=1 ttl=254 time=1.00 > ms > 64 bytes from <a href="http://192.168.1.254" target="_blank">192.168.1.254</a>: icmp_seq=2 ttl=254 time=0.971 > ms > 64 bytes from <a href="http://192.168.1.254" target="_blank">192.168.1.254</a>: icmp_seq=3 ttl=254 time=1.00 > ms > ^C > --- 192.168.1.254 ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time > 2007ms > rtt min/avg/max/mdev = 0.971/0.993/1.008/0.015 ms > > However, I still do not yet manage to ping <a href="http://google.com" target="_blank">google.com</a> or > any other > external website. At a terminal, the fruitless attempt > looked like > this: > bas@Viaconsensus2:~$ ping <a href="http://google.com" target="_blank">google.com</a> > ping: unknown host <a href="http://google.com" target="_blank">google.com</a> > > With respect to the /etc/network/interfaces file, an advise > came in to > replace this: ... > > iface eth0 inet static > ...with this: > > iface eth0 inet dhcp > After doing so, attempts to ping my router > ('unreachable'), desktop > ('unreachable') and an external website > ('unknown host') were all > fruitless. > That's why, I put back 'inet static' in the > interfaces file. After > doing so, attempts to ping the desktop and router were > successful, but > pinging <a href="http://google.com" target="_blank">google.com</a> still did not work out. > > A core issue is now, whether it is possible to manually > configure an > eth0 connection via 'KNetwork', the network manager > of Kubuntu 8.10. > With respect to this issue, this advise recently came in: > > > Now open the intrepid network manager and click on the > Wired tab and > > entry for "Wired connection 1" then click > "Edit". In IPv4 Settings: > > > > Method: Manual > > Addresses: > > Address - 192.168.1.20 > > Netmask - 255.255.255.0 > > Gateway - 192.168.1.254 > > DNS Servers: enter the dns servers for your ISP ... > With respect to this issue, I get this info via > <a href="http://www.whatsmyip.org" target="_blank">http://www.whatsmyip.org</a> > NameServer: <a href="http://NS-PRI.RIPE.NET" target="_blank">NS-PRI.RIPE.NET</a> > NameServer: <a href="http://NS3.NIC.FR" target="_blank">NS3.NIC.FR</a> > NameServer: <a href="http://SEC1.APNIC.NET" target="_blank">SEC1.APNIC.NET</a> > NameServer: <a href="http://SEC3.APNIC.NET" target="_blank">SEC3.APNIC.NET</a> > NameServer: <a href="http://SUNIC.SUNET.SE" target="_blank">SUNIC.SUNET.SE</a> > NameServer: <a href="http://TINNIE.ARIN.NET" target="_blank">TINNIE.ARIN.NET</a> > > The same site <a href="http://whatsmyip.org" target="_blank">whatsmyip.org</a> clarifies the "external > IP" of my DESKTOP > PC, from which I am writing this message: 82.169.250.209 > At a terminal on the desktop, I carried out a dig test with > this IP > number. This was the outcome: > > bas@Viaconsensus1:~$ dig 82.169.250.209 > ; <<>> DiG 9.5.0-P2 <<>> > 82.169.250.209 > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: > NXDOMAIN, id: 34038 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, > ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;82.169.250.209. IN A > > ;; AUTHORITY SECTION: > . 10800 IN SOA > <a href="http://A.ROOT-SERVERS.NET" target="_blank">A.ROOT-SERVERS.NET</a>. > <a href="http://NSTLD.VERISIGN-GRS.COM" target="_blank">NSTLD.VERISIGN-GRS.COM</a>. 2009012000 1800 900 604800 86400 > > ;; Query time: 28 msec > ;; SERVER: 192.168.1.254#53(192.168.1.254) > ;; WHEN: Tue Jan 20 12:11:19 2009 > ;; MSG SIZE rcvd: 107 > > If I understand you correctly, NoOp, my 'DNS' > should be, as a matter > of consequence: "192.168.1.254". > In KNetworkmanager, the manual menu for wired connections > contains two > lines I need to fill in with respect to DNS: 'DNS > Addresses' and 'DNS > Search'. First I filled in the 'name servers' > coming out of > <a href="http://whatsmyip.org" target="_blank">whatsmyip.org</a> in the line 'DNS Addresses' and > "192.168.1.254" (without > the "-signs) in the line 'DNS Search'. But > after saving, closing and > re-opening this output, the 'name server' names in > the DNS Addresses > line vanished. Three attempts worked out like that. > Than I put the DNS info inversely: '192.168.1.254' > in 'DNS Addresses' > and the 'name servers' in 'DNS Search'. > KNETWORKMANAGER does maintain > this input after saving and closing. However, even the > option 'save > and connect' does not yet result in an effectively > working internet > connection from my laptop. On the other hand, it did not > harm anything > neither. I still DO manage to ping my router and desktop > from the > laptop. > > > Now click on the "Wired" tab and enter the > mac address for your eth0 > > (from your ifconfig output): > > > > MAC Address: 00:40:ca:bc:9e:88 > > MTU: 1500 > > In 'KNetworkmanager' I did not find any tab or > option to fill in the > 'MAC Adress' and 'MTU'. Do I overlook > anything? Is there any other > option to manually fill in such information? > > > Now click OK. You'll get a password prompt: enter > your password. > In KNetworkmanager, it did not work out like this. > > From a terminal at the laptop, I carried out some tests, > advised to me > in this thread. > > > cat /etc/resolv.conf > The test "cat /etc/resolv.conf" delivered only > this feedback: > # generated by NetworkManager > > Then, I tried to run 'NetWorkManager' as root, from > the terminal. But > nothing happened: no menu popped up, but also no > information about any > mistake. > > > cat /etc/hosts > This test worked out in the feedback below and above the > ==== lines. > > ======================= > bas@Viaconsensus2:~$ cat /etc/hosts > 127.0.0.1 localhost > 127.0.1.1 Viaconsensus2 > > # The following lines are desirable for IPv6 capable hosts > ::1 ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > ff02::3 ip6-allhosts > ======================== > > > ping <a href="http://google.com" target="_blank">google.com</a> > As mentioned above, this ping test is fruitless: > ping: unknown host <a href="http://google.com" target="_blank">google.com</a> > > > ping 192.168.1.1 > This test worked out as indicated in between the === lines. > > ===================== > bas@Viaconsensus2:~$ ping 192.168.1.1 > PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. > From 192.168.1.20 icmp_seq=2 Destination Host Unreachable > From 192.168.1.20 icmp_seq=3 Destination Host Unreachable > .....seq=4.....sec=5 ...etc. ...sec=29 Destination Host > Unreachable > > --- 192.168.1.1 ping statistics --- > 29 packets transmitted, 0 received, +21 errors, 100% packet > loss, time 28029ms > , pipe 3 > ======================= > > This ping test was fruitless. On the other hand: as > indicated above, I > DO manage to ping the router and desktop. > > > cat /etc/udev/rules.d/70-persistent-net.rules > > The outcome of this test in between the === lines. > > ================================ > bas@Viaconsensus2:~$ cat > /etc/udev/rules.d/70-persistent-net.rules > # This file maintains persistent names for network > interfaces. > # See udev(7) for syntax. > # > # Entries are automatically added by the > 75-persistent-net-generator.rules > # file; however you are also free to add your own entries. > > # PCI device 0x10ec:0x8139 (8139too) > SUBSYSTEM=="net", ACTION=="add", > DRIVERS=="?*", > ATTR{address}=="00:40:ca:bc:9e:88", > ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > > # PCI device 0x115d:0x0003 (xircom_cb) > SUBSYSTEM=="net", ACTION=="add", > DRIVERS=="?*", > ATTR{address}=="00:10:a4:75:ba:4a", > ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > ==================================== > > Finally, I provide you with possibly useful information > that I got via > <a href="http://whatsmyip.org" target="_blank">whatsmyip.org</a>: > > External IP: 82.169.250.209 > (= desktop?) > Hostname: <a href="http://82-169-250-209.ip.telfort.nl" target="_blank">82-169-250-209.ip.telfort.nl</a> > Proxy: No Proxy or Invisible Proxy > Used > Internal (LAN) IP: 192.168.1.33 > Outgoing Port: 12639 > (...) > > ReferralServer: whois://<a href="http://whois.ripe.net:43" target="_blank">whois.ripe.net:43</a> > > NetRange: 82.0.0.0 - 82.255.255.255 > CIDR: <a href="http://82.0.0.0/8" target="_blank">82.0.0.0/8</a> > NetName: 82-RIPE > NetHandle: NET-82-0-0-0-1 > Parent: > NetType: Allocated to RIPE NCC > NameServer: <a href="http://NS-PRI.RIPE.NET" target="_blank">NS-PRI.RIPE.NET</a> > NameServer: <a href="http://NS3.NIC.FR" target="_blank">NS3.NIC.FR</a> > NameServer: <a href="http://SEC1.APNIC.NET" target="_blank">SEC1.APNIC.NET</a> > NameServer: <a href="http://SEC3.APNIC.NET" target="_blank">SEC3.APNIC.NET</a> > NameServer: <a href="http://SUNIC.SUNET.SE" target="_blank">SUNIC.SUNET.SE</a> > NameServer: <a href="http://TINNIE.ARIN.NET" target="_blank">TINNIE.ARIN.NET</a> > (.....) > % Information related to '82.169.224.0 - > 82.169.255.255' > (....) > inetnum: 82.169.224.0 - 82.169.255.255 > netname: NL-TELFORT-DSL > descr: Telfort internet > descr: Internet Service Provider > descr: DSL Customer Network > country: NL > admin-c: GITR1-RIPE > tech-c: GITR1-RIPE > status: ASSIGNED PA > mnt-by: WOLTECH-MNT > source: RIPE # Filtered > > admin-c: MH6157-RIPE > tech-c: RP1269-RIPE > tech-c: MH6157-RIPE > nic-hdl: GITR1-RIPE > mnt-by: WOLADM-MNT > source: RIPE # Filtered > > % Information related to '<a href="http://82.168.0.0/14AS5615" target="_blank">82.168.0.0/14AS5615</a>' > > route: <a href="http://82.168.0.0/14" target="_blank">82.168.0.0/14</a> > descr: Green ISP B.V. > origin: AS5615 > mnt-by: WISH-MNT > mnt-by: WOLADM-MNT > source: RIPE # Filtered > > To finish this message: nearly 3 days of testing still do > not result > in a working eth0-connection from my laptop. So, I hope get > some extra > feedback which could possibly enable me to fill in the > white spots on > my map...... My next possibility to carry out tests and to > get back to > you will be next Saturday or Sunday. > > Respectfully yours, > > Bas. > I read your entire reply and suspect your may be overwhelming yourself with all the details. One thing I noticed is that as you pointed out there is no info in /etc/resolv.conf where there should be. Why don't you just not change anything else and edit the /etc/resolv.conf file with your favorite editor adding the needed info. I use "sudo nano /etc/resolv.conf" and the data to add looks like this: search <a href="http://gateway.2wire.net" target="_blank">gateway.2wire.net</a> nameserver 192.168.1.254 Where "<a href="http://gateway.2wire.net" target="_blank">gateway.2wire.net</a>" is the name of my gateway/dns server. Use yours as you setup in knetwork manager. then try to connect and report back before doing/changing anything else. I'm no expert, but have set up wired/wireless connections before with help but can usually do it myself now. It's not that hard if you know the basics. good luck and HTH a little. Leonard Chatagnier <a href="mailto:lenc5570@sbcglobal.net">lenc5570@sbcglobal.net</a> > -- > =============== > Viaconsensus > Bas G. Roufs M.A. > Van 't Hoffstraat 1 > NL-3514 VT Utrecht > M. +31.6.446.835.10 > T. +31.30.785.20.40 > <a href="mailto:BasRoufs@gmail.com">BasRoufs@gmail.com</a> > =============== > > -- > ubuntu-users mailing list > <a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a> > Modify settings or unsubscribe at: > <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a> -- ubuntu-users mailing list <a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a> </blockquote></div>