Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Mepis11 WIRED networking pooched

Questions about Networking that deals with wireless cards, ethernet, modems, samba and anything else related to these, including software help. Tutorials for any of these can be posted too.

Remember to provide relevant info in your posts, such as the following information:

Version of Mepis being used
Card Manufacturer (i.e. Linksys)
Card Model (i.e. WMP54G)
Type: (PCI or PCMCIA)
Current Kernel in use on their system (i.e. 2.6.10)
Udev or Hotplug
Exact steps taken to get the card working if it is not immediately recognized by MEPIS.
Message
Author
User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#11 Post by uncle mark » Fri Jun 13, 2014 9:58 pm

Is it possible the onbord NIC on this machine is just starting to go flaky, enough that Linux balks but Windows doesn't? I have a PCIe-1 slot avaialble, so adding a NIC wouldn't be an issue.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9302
Joined: Wed Jul 12, 2006 2:26 pm

Re: Mepis11 WIRED networking pooched

#12 Post by kmathern » Fri Jun 13, 2014 10:03 pm

uncle mark wrote:Is it possible the onbord NIC on this machine is just starting to go flaky, enough that Linux balks but Windows doesn't? I have a PCIe-1 slot avaialble, so adding a NIC wouldn't be an issue.
I suppose that's possible.

Does `ifconfig -a` show anything different after running the `dhclient eth0` command ?

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#13 Post by uncle mark » Fri Jun 13, 2014 10:10 pm

kmathern wrote:
uncle mark wrote:Is it possible the onbord NIC on this machine is just starting to go flaky, enough that Linux balks but Windows doesn't? I have a PCIe-1 slot avaialble, so adding a NIC wouldn't be an issue.
I suppose that's possible.

Does `ifconfig -a` show anything different after running the `dhclient eth0` command ?
Looking at them side by side I see no difference.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9302
Joined: Wed Jul 12, 2006 2:26 pm

Re: Mepis11 WIRED networking pooched

#14 Post by kmathern » Fri Jun 13, 2014 10:15 pm

Does it work in a LiveCD/LiveDVD/LiveUSB live session of M11 and/or MX14?

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#15 Post by uncle mark » Fri Jun 13, 2014 10:32 pm

kmathern wrote:Does it work in a LiveCD/LiveDVD/LiveUSB live session of M11 and/or MX14?
Good thought. Yes, it does. I'm posting from the MX live CD right now. It also shows up in the router under Attached Devices.

So that tells me it has to be in the M11 networking stack somewhere, not hardware.

I'd really like to fix this rather than reinstalling. It won't be the end of the world, but now is really not a good time. Thanks for your interest and efforts.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#16 Post by uncle mark » Fri Jun 13, 2014 10:56 pm

Here's another thought. I'm now booted to the M11-64 live DVD. Would there be some files or configs I could copy over from this working live OS into the pooched installed OS? (and which takes into account my (un)sophistication level)
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15971
Joined: Fri Dec 15, 2006 8:07 pm

Re: Mepis11 WIRED networking pooched

#17 Post by Stevo » Fri Jun 13, 2014 11:07 pm

On M11, can you get it working if logged in as root or as another user? It's a wild guess, since I think network-manager stores just one configuration for the machine.

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#18 Post by uncle mark » Fri Jun 13, 2014 11:18 pm

Stevo wrote:On M11, can you get it working if logged in as root or as another user? It's a wild guess, since I think network-manager stores just one configuration for the machine.
No joy logging in as root. Same output with 'ifconfig -a' as in user.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: Mepis11 WIRED networking pooched

#19 Post by uncle mark » Fri Jun 13, 2014 11:57 pm

Okay, here's another data point I found interesting.

Here's the output of ipconfig in Windows:

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mark>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::493f:76f2:b418:4b1f%10
   IPv4 Address. . . . . . . . . . . : 192.168.1.3
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:1c0d:1d2e:9d20:4768
   Link-local IPv6 Address . . . . . : fe80::1c0d:1d2e:9d20:4768%11
   Default Gateway . . . . . . . . . : ::

Tunnel adapter isatap.{1A825D27-5B3F-4092-8D4C-FE20954EB1A8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

C:\Users\Mark>
Here's the contents of etc/network/interfaces in my borken M11 install:

Code: Select all

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
#
# If you are using the MEPIS Network Assistant
# then DO NOT use this file to define wireless/wpa options
#

# lo should ALWAYS be enabled!
auto lo
iface lo inet loopback

# DO NOT EDIT BELOW THIS LINE
#auto eth0
#allow-hotplug eth0
iface eth0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto eth1
#allow-hotplug eth1
iface eth1 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto eth2
#allow-hotplug eth2
iface eth2 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto ath0
#allow-hotplug ath0
iface ath0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto wlan0
#allow-hotplug wlan0
iface wlan0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto ra0
#allow-hotplug ra0
iface ra0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto rausb0
#allow-hotplug rausb0
iface rausb0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
#auto wifi0
#allow-hotplug wifi0
iface wifi0 inet dhcp
  address 192.168.79.1
  netmask 255.255.255.0
  broadcast 192.168.79.255
  gateway 192.168.79.1
# DO NOT EDIT ABOVE THIS LINE
Now look at the IPs. The non-working MEPIS has 192.168.79.1 listed for the both the address and gateway, while the working Windows lists 192.168.1.3 for the machine address and 192.168.1.1 for the gateway.

I also saw in (I think) etc/networkmanager/config a "managed=false" entry.

Would it be reasonable to edit the IP listings in etc/network/interfaces to the working IPs as reported by Windows? And/or should I change the "managed=false" entry to "managed=true"?

Thanks to all for you interest and assistance. I may not last much longer tonight, but will be back in earnest tomorrow.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9071
Joined: Sun Dec 16, 2007 1:17 pm

Re: Mepis11 WIRED networking pooched

#20 Post by dolphin_oracle » Sat Jun 14, 2014 12:14 am

I haven't used M11, but aren't those entries defining a static IP? maybe if you just remove entries so the line looks like

Code: Select all

iface eth0 inet dhcp
that should allow network manager to do its thing. leave networkmanager config with managed = false, this is the correct default entry.

that's how the interface should look in MX anyway. Not sure about M11 and if you used mnetwork to set things up.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

Post Reply

Return to “Networking”