[Tfug] qwest high speed internet and linux

[Joel Howard]

Harry McGregor wrote:
> Joel Howard wrote:
>   
>> Harry McGregor wrote:
>>   
>>     
>>> Hi,
>>>
>>> What does the output of ifconfig -a show?
>>>   
>>>     
>>>       
>> eth0 Link encap:Ethernet HWaddr 00:50:22:BA:09:86
>> inet addr:192.168.2.8 Bcast:192.168.2.255 Mask:255.255.255.0
>> 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.0 b) TX bytes:0 (0.0 b)
>> Interrupt:11 Base address:0xd400
>>   
>>     
> Any idea where you are getting the 192.168.2.8 address from?
>   
That's the old IP address of this box when it was networked (wired) to
others in another room.
> Maybe the default config changed, try http://192.168.2.1
>   
This didn't load.
> What does "route -n" show?
>   
route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>> lo Link encap:Local Loopback
>> inet addr:127.0.0.1 Mask:255.0.0.0
>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>> RX packets:466 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:466 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:37833 (36.9 Kb) TX bytes:37833 (36.9 Kb)
>>   
>>     
>>> Also, dmesg | grep eth
>>>   
>>>     
>>>       
>> eth0: RealTek RTL8139 at 0xd400, 00:50:22:ba:09:86, IRQ 11
>> eth0: Identified 8139 chip type 'RTL-8100B/8139D'
>> eth0: link down
>> eth0: link down
>> eth0: link down
>> eth0: link down
>>
>> The above looks like a problem.
>>   
>>     
> Link down might not be good, does your NIC have it's link light on?
>   
The RJ45 on back of this box is the on-board one, and doesn't appear to
have a light near it.
> What about the DSL "modem" is the ethernet light on?
>   
Power light, ethernet light, DSL light are all on. Internet light is on,
but red.
>   
>>> and you can try running "pump -i eth0" or "dhclient eth0" and see if
>>> either of those get you an ip address.
>>>   
>>>     
>>>       
>> "command not found" on both, and which command for both gave me nothing
>> in my path.
>>   
>>     
>
> ok, maybe dhcpcd?
>   
not found - used which command and nothing came back from that or ps aux.
>                             Harry
>
>   
>>>                     Harry
>>>     
>>>       
>
>
> _______________________________________________
> Tucson Free Unix Group - tfug at tfug.org
> Subscription Options:
> http://www.tfug.org/mailman/listinfo/tfug_tfug.org
>
>