Re: nm eth0 connection(2)
On Fri, Sep 13, 2013 at 06:48:59PM -0400, Tom H wrote: ...snip.. I'd check elsewhere. NM seems to have done its job. What's the output of ip a ip r iptables -nL I put the results of these on http://pastebin.ca/2451440 I only included the parts of iptables -nL that looked relevant. If I was wrong I can give you the whole thing. Can you ping 127.0.0.1? yes Can you ping 192.168.1.102? yes, which confuses me as to why when I can't ping 192.168.1.1. I found a partial but unsatisfactory work around. If I boot and defeat the xceiver before the login screen appears I can connect with eth0. Can you account for this? -- Bob Holtzman Your mail is being read by tight lipped NSA agents who fail to see humor in Doctor Strangelove Key ID 8D549279 signature.asc Description: Digital signature
Re: nm eth0 connection(2)
On Thu, Sep 12, 2013 at 2:27 PM, Robert Holtzman hol...@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 hol...@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? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxU7pYmoRGxO671z-1BU=oqZNpmbpEjOFfS_h-Ls=l...@mail.gmail.com
Re: nm eth0 connection(2)
On Wed, Sep 11, 2013 at 4:59 PM, Robert Holtzman hol...@cox.net wrote: On Wed, Sep 11, 2013 at 07:47:10AM -0400, Tom H wrote: On Tue, Sep 10, 2013 at 4:01 PM, Robert Holtzm hol...@cox.net wrote: Running updated wheezy on a thinkpad T420i w/ xfce DE. With great embarrassment, after stoutly defending nm, eth0 no longer connects. This only happens when I run wheezy. The connection is fine when I run the other distros on the hdd, squeeze and ubuntu 12.04. Under wheezy it also happens when the laptop is hard wired directly to the cable modem. looking at dmesg root@localhost:/home/holtzm# tail --lines=50 /var/log/dmesg | grep eth0 [ 18.864912] ADDRCONF(NETDEV_UP): eth0: link is not ready Looking at messages root@localhost:/var/log# less messages | grep eth0 | less Sep 8 15:13:25 localhost kernel: [10656.049605] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Sep 8 15:13:25 localhost kernel: [10656.049617] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Sep 8 15:13:26 localhost kernel: [10657.229970] Unknown OutputIN= OUT=eth0 SRC=192.168.1.102 DST=68.105.28.12 LEN=51 TOS =0x00 PREC=0x00 TTL=64 ID=43051 PROTO=UDP SPT=59586 DPT=53 LEN=31 Notice the difference between 15:13:25 and 15:13:26. 26 is a netfilter dns query log. To troubleshoot NM, it would've been more useful to grep for NetworkManager as well as tail the messages log file. 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? (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! :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=syh8-b5qubqnavn0ddukh6080d_b7ta4qmd5ur-fs3...@mail.gmail.com
Re: nm eth0 connection(2)
On Thu, Sep 12, 2013 at 10:14:07AM -0400, Tom H wrote: On Wed, Sep 11, 2013 at 4:59 PM, Robert Holtzman hol...@cox.net wrote: On Wed, Sep 11, 2013 at 07:47:10AM -0400, Tom H wrote: ...snip... 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? -- Bob Holtzman Your mail is being read by tight lipped NSA agents who fail to see humor in Doctor Strangelove Key ID 8D549279 signature.asc Description: Digital signature
Re: nm eth0 connection(2)
On Wed, Sep 11, 2013 at 07:47:10AM -0400, Tom H wrote: On Tue, Sep 10, 2013 at 4:01 PM, Robert Holtzm hol...@cox.net wrote: Running updated wheezy on a thinkpad T420i w/ xfce DE. With great embarrassment, after stoutly defending nm, eth0 no longer connects. This only happens when I run wheezy. The connection is fine when I run the other distros on the hdd, squeeze and ubuntu 12.04. Under wheezy it also happens when the laptop is hard wired directly to the cable modem. looking at dmesg root@localhost:/home/holtzm# tail --lines=50 /var/log/dmesg | grep eth0 [ 18.864912] ADDRCONF(NETDEV_UP): eth0: link is not ready Looking at messages root@localhost:/var/log# less messages | grep eth0 | less Sep 8 15:13:25 localhost kernel: [10656.049605] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Sep 8 15:13:25 localhost kernel: [10656.049617] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Sep 8 15:13:26 localhost kernel: [10657.229970] Unknown OutputIN= OUT=eth0 SRC=192.168.1.102 DST=68.105.28.12 LEN=51 TOS =0x00 PREC=0x00 TTL=64 ID=43051 PROTO=UDP SPT=59586 DPT=53 LEN=31 Notice the difference between 15:13:25 and 15:13:26. 26 is a netfilter dns query log. To troubleshoot NM, it would've been more useful to grep for NetworkManager as well as tail the messages log file. 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 cat /etc/network/interfaces and cat /etc/NetworkManager/NetworkManager.conf are as shown in my other reply. 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! -- Bob Holtzman Your mail is being read by tight lipped NSA agents who fail to see humor in Doctor Strangelove Key ID 8D549279 signature.asc Description: Digital signature
