command for downloading a package to save
stevenvollom at sbcglobal.net
Mon Jun 15 04:24:54 UTC 2009
On Sunday 14 June 2009 09:47:38 pm Billie Erin Walsh wrote:
> David McGlone wrote:
> > On Sunday 14 June 2009 05:17:09 pm Lisi Reisz wrote:
> >> On Sunday 14 June 2009 20:37:07 Eberhard Roloff wrote:
> >>> After you return from your break, please issue this command
> >>> on your laptop:
> >>> sudo ifconfig
steven at steven-laptop:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:02:93:4f:8c
inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::208:2ff:fe93:4f8c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70958 errors:0 dropped:0 overruns:0 frame:0
TX packets:62517 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:74112186 (74.1 MB) TX bytes:8969135 (8.9 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1920 (1.9 KB) TX bytes:1920 (1.9 KB)
steven at steven-laptop:~$
At the moment, I am connected directly to the DSL modem, not the router.
> >>> usually, one of the interfaces will have an address
> >>> beginning with 192.168.x.y
> >> Eberhard -
> >> Stephen said that he cannot connect through his router, but only
> >> directly through his DSL modem. If this is correct, and if the term DSL
> >> modem means the same thing his side of the pond as it does here (by no
> >> means a forgone conclusion), his laptop must be connecting directly with
> >> his ISP, probably with a dynamic IP, and it is not going to tell us
> >> anything about his network.
> > It might not reveal much, but it will give us a starting point. It'll
> > help us figure out whether he is calling his modem a router or he
> > actually has a router.
> > I used to think the way you do, and I failed the A+ Cert 1 time because
> > of that thinking.
> > After 10 years, I learned to start with the most simplest of problems and
> > work your way up.
> > A perfect example, last year I got a computer in for repair, I tried
> > turning it on No fan, no lights, zilch, Nada. My first reaction was the
> > power supply, so I drive 25 minutes to get a new power supply, popped it
> > in and still got zilch, no power, no lights. I assumed they sold me a bad
> > power supply so I returned it, popped in the new one an hour later, still
> > Nada.
> > Finally I took the faceplate to check the wiring to the power button and
> > found that the plastic "stem" on the power button that pushes the button
> > on the chassis was broken!
> > So I put the original power supply back in and returned the brand new one
> > once again, replaced the power button on the case and the computer is
> > still working to this day.
That sounds like the problem with my laptop.
> Sometimes the simplest problems are the hardest to fix. Simple problems
> are often overlooked because they are so simple.
> Treat all stressful situations like a dog does.
> If you can't eat it or play with it,
> just pee on it and walk away
Do you want me to reconnect to the router. I don't have it set up to operate
wirelessly, it is just set up to serve two cabled computers. It is not a
problem. I believe we are on the same side of the water with terminology. My
modem is a DSL modem telephone in, power in, Eth cable to computer.
The router is a D-link Air Plus extreme wireless, but I don't have it set up
for wireless. I really don't need it that way at the moment.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kubuntu-users