command for downloading a package to save

Steven Vollom stevenvollom at sbcglobal.net
Tue Jun 16 19:53:47 UTC 2009


On Monday 15 June 2009 02:09:16 am Eberhard Roloff wrote:
> Dear Steven,
>
> Steven Vollom wrote:
> > 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 it
>
> Excellent, this means:
> Your laptop is on a private network, getting an IP Adress.
>
> > steven at steven-laptop:~$
> >
> >
> > At the moment, I am connected directly to the DSL modem, not the router. 
it
>
> Honestly, I am slightly confused. A real DSL-Modem, as Lisi
> pointed out, does not act as a dhcp server, but connects you
> directly to the internet. Obviously, your laptop is not
> connected directly to the internet, but is residing behind
> some kind of routing device, Otherwise imho it would not get
> a 192.168.1.64 address.
>
> So, what is the exact name and model of your "dsl-modem"?



Westell
Modem Access Code
5263820374
S/N 0BAK11091950



MAC:  00183AE7343E
ADSL2+ ROUTER



Style:MSTATEA



For advanced Device Configuration go to:  http://192.168.1.254



(Trim)



> Okay then.
> Simply have your laptop switched on, just at it is.
> This is just, since I remember you fear, that it will not
> start up, when you power it down.
>
> Now remove the ethernet cable from the laptop and plug the
> very same, known_working_good cable into your desktop.
> Should the cable be to short, just move the desktop to where
> the cable fits.
>
> Then fire up the desktop which does not connect to the internet.
>
> What happens?
Same error message.  Unknown Host.
> what does
> "sudo ifconfig"
> show?



I have to type this, it is the only way I can get it.  I tried a thumb drive 
yesterday; it showed the fine transfer to the thumb drive, but when I opened 
the thumb int the laptop, it did not show there.



eth0		Link encap;Ethernet  HWaddr 00:0d:88:1c:a7:71
		UP BROADCAST 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 frame:0
		collisions:0 txqueuelen:1000
		RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)t
		Interrupt:18 Bse adddress:0xd800



eth1		Link encap:Ethernet  HWaddr 00:40:05:39:47:8d
		UP BROADCAST 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.) B)  TX bytes:0 (0.0 B)
		Interrupt:18 Base  address:0xd400



eth2		Link encap:Ethernet  HWaddr 00:08:74:d4:1f:3a
		inet addr:192.168.1.64  Bcast:192.168.1.255  Mask:255.255.255.0
		iinet6 addr:  fe80::208:74ff:fec4:1f3a/64 Scope:Link
		UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1
		RX packets:16 errors:0 dropped:0 overruns:0 frame:0
		TX packets:14 errors:0 dropped 0 overruns:0 carrier:0
		collisions:0 txqueuelen:100
		RX bytes:3100 (3.1 KB)  TX bytes:2904 (2.9 KB)



Lo		Link encap:Local Loopback
		inet addr:127.0.0.1  Mask:255.0.0.0b
		inet6 addr: ::1/128 Scope:Host
		UP LOOPBACK RUNNING  MTU:16436  Metric:1
		RX packets:24 errors:0 dropped;0 overruns:0 frame:0
		TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
		collisions:0 txqueuelen:0)
		RX  bytes:1144 (1l1 KB)  TX bytes:1144 (1l1 KB)



> By doing this test, I put my money on you having problems
> with your "multiple ethernet-router-switch..."-devices
> inside your network, once again. I remember vaguely that
> network problems of this kind at your site were the reason
> for very long threads, some time ago. ;-)



I am very confused by what you said in the preceding paragraph.  What has 
changed by doing this test?  My memory is pretty bad, but I don't remember 
that.  After sending, I will search the archives.  What you said here sounds 
like if I direct connect the modem to the, what I call the infected box, it 
should work normally.  After I send, I will try direct modem to infected box 
and see.
>
> After having done the test with the desktop, you can easily
> reconnect the ethernet cable to your laptop and it will
> work, just as before.



When I connect the modem to the laptop, it always works.  Are you talking 
about connecting the modem to the router and the router to the laptop and 
having that work again?
>
> > 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.
>
> No problem. I also only use wireless when I absolutely
> cannot do without it.



But I haven't been using wireless, because I can't get it to work.  It has not 
been a priority though like other things, or I probably would have tried 
again.  I am not sure where the laptop wireless card is right now anyway.



Wow, if the infected box works direct to modem, I will consider this a 
success, even if it still isn't totally cured.  Thanks Mucho!



Steven
>
> Kind regards
> Eberhard



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20090616/e6ae9c59/attachment.html>


More information about the kubuntu-users mailing list