Re: nm eth0 connection(2)
On Thu, Sep 12, 2013 at 2:27 PM, Robert Holtzman <holtzm@cox.net> wrote:
> On Thu, Sep 12, 2013 at 10:14:07AM -0400, Tom H wrote:
>> On Wed, Sep 11, 2013 at 4:59 PM, Robert Holtzman <holtzm@cox.net> wrote:
>>> On Wed, Sep 11, 2013 at 07:47:10AM -0400, Tom H wrote:
>>>>
>>>> What's the output of
>>>>
>>>> nm-tool
>>>> cat /etc/network/interfaces
>>>> cat /etc/NetworkManager/NetworkManager.conf
>>>
>>> tail --lines=50 /var/log/dmesg | grep NetworkManager yields nothing
>>> the same with tail --lines=50 /var/log/messages | grep NetworkManager
>>
>> Why are you limiting your search to the last 50 lines?
>
> Good point for which I have no good answer except that I thought that 50
> would be far enough back. No, huh?
>
> Nothing shown no matter how far back I go.
>>
>> (dmesg won't have any NM logs.)
>>
>>
>>> nm-tool yields, in part,
>>>
>>> - Device: eth0 [Auto (eth0)]
>>> --------------------------------------------------
>>> Type: Wired
>>> Driver: e1000e
>>> State: connected
>>> Default: yes
>>> HW Address: 00:21:CC:B6:06:8F
>>>
>>> Capabilities:
>>> Carrier Detect: yes
>>> Speed: 100 Mb/s
>>>
>>> Wired Properties
>>> Carrier: on
>>>
>>> IPv4 Settings:
>>> Address: 192.168.1.102
>>> Prefix: 24 (255.255.255.0)
>>> Gateway: 192.168.1.1
>>>
>>> DNS: 68.105.28.12
>>> DNS: 68.105.29.12
>>> DNS: 68.105.28.11
>>>
>>> Strange!
>>
>> No strange, working! :)
>
> Plenty strange. If I'm connected, why can't I ping my router or a web
> site?
I'd check elsewhere. NM seems to have done its job.
What's the output of
ip a
ip r
iptables -nL
Can you ping 127.0.0.1?
Can you ping 192.168.1.102?
Reply to: