Eth0 configured but NO Working Network
Posts: 10
I have had problems with Mepis since 3.4.1. On the live cd the network is setup and configured with the same configuration as my Ubuntu desktop. All the network settings are the same but it can't connect or ping to anything. I thought that it would get fixed with the merger with Ubuntu but as of 6.0 Beta 2 it still doesn't work. It sets up DHCP like it should and when you check the numbers are correct and the same as the Ubuntu setup but it won't work. Even the hardware address's are the same when you do a ifconfig. Anyone out there have any ideas as what's wrong? I even checked Guard dog and it defaults to Off. Thanks for any ideas..
Mike
Eth0 configured but no working network
Posts: 10
This is the configuration from my working Ubuntu..below I will list what shows up with SimplyMepis 6.0 beta2. This is All on the SAME Computer network card etc..
eth0 Link encap:Ethernet HWaddr 00:80:AD:80:8D:A9
inet addr:192.168.2.39 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::280:adff:fe80:8da9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:182 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:174760 (170.6 KiB) TX bytes:16034 (15.6 KiB)
Interrupt:19 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:838 errors:0 dropped:0 overruns:0 frame:0
TX packets:838 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:243276 (237.5 KiB) TX bytes:243276 (237.5 KiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
This is from Mepis 6.0Beta 2
eth0 Link encap:Ethernet HWaddr 00:80:AD:80:8D:A9
inet addr:192.168.2.39 Bcast:192.168.79.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:224 dropped:0 overruns:0 frame:0
collisions:0 txqueuelen:1000
RX bytes:7510 (7.3 KiB) TX bytes:0 (0.0 KiB)
Interrupt:193 Base address:0xec00
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:134 errors:0 dropped:0 overruns:0 frame:0
TX packets:134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15186 (14.8 KiB) TX bytes:15186 (14.8 KiB)
It seems to me the problem is in DHCP not configuring everything correctly.
I have 3 computers that connect to the Net through a router and all use DHCP with no problems. It's just when I use the Mepis disk that the connection doesn't work and like I said it all started about 3.3.1 or somewhere in that general time frame. I kept hoping that it will get fixed with the next version but it didn't.
Hope this helps
Mike
Quote:This is from Mepis
Posts: 613
This is from Mepis 6.0Beta 2eth0 Link encap:Ethernet HWaddr 00:80:AD:80:8D:A9
inet addr:192.168.2.39 Bcast:192.168.79.255 Mask:255.255.255.0
The broadcast address (192.168.79.255) is set for the wrong subnet. It should be 192.168.2.255. Use the 'Mepis OS Center', turn off eth0, set up a static address.
e.g.:
inet 192.168.2.39
broadcast: 192.168.2.255
Mask: 255.255.255.0
Restart eth0.
If that doesn't do it, let me know.
no working network
Posts: 10
qtech
tried your suggestion and it still won't connect. I checked it when i first logged in and DHCP had it set as...
IP 192.168.79.1
netmask 255.255.255.0
gateway 192.168.79.1
bcast 192.168.79.255
When I set it up as static as you suggested it starts eth0 and the network card on the task bar turns green and says it's connected and in the Mepis control it says it is connected but nothing. If you change it back to DHCP again in can't ever connect again until you reboot but if you change it back to static in does what I said above but can never get to the net. I had a similar thing once with Suse and that turned out that it was selecting the wrong driver, I don't know if that has anything to do with this or not or that maybe it's just a DHCP issue.
Thanks for your help
Mike
Go to mepis config. Stop
Posts: 165
Go to mepis config. Stop eth0, click on eth0 tab, clic on static address if not already chosen make sure that your ip address is 192.168.2.xxx, default gateway 192.168.2.1, broadcast 192.168.2.255. then click apply. Click on status and restart eth0
As an example my router network is 192.168.1.1 and is also the default gateway. My ip address is 192.168.1.104 and my broadcast address is 192.168.1.255. I'm assuming from your above post of ifconfig that your router address is 192.168.2.1.
Now when I boot up my network works. I'm just confised as to why dhcp no longer works in beta1.
192.
A Day Without M$ Windoze is a Great Day Indeed !!! 
Wrong gateway
Posts: 613
IP 192.168.79.1
netmask 255.255.255.0
gateway 192.168.79.1
bcast 192.168.79.255
Your IP cannot be the same as your 'gateway' (which is the router)
Static setting should read:
IP 192.168.2.3 (your computer)
netmask 255.255.255.0
gateway 192.168.2.1 (Router)
bcast 192.168.2.255
Your home network resides on 192.168.2.XX
Edit: Alternately do what Wpfaff said to do, which if I had bothered to read the first time I could of saved the trouble...
Re: Wrong gateway
Posts: 10
Quote:IP 192.168.79.1
netmask 255.255.255.0
gateway 192.168.79.1
bcast 192.168.79.255Your IP cannot be the same as your 'gateway' (which is the router)
Static setting should read:
IP 192.168.2.3 (your computer)
netmask 255.255.255.0
gateway 192.168.2.1 (Router)
bcast 192.168.2.255Your home network resides on 192.168.2.XX
Edit: Alternately do what Wpfaff said to do, which if I had bothered to read the first time I could of saved the trouble...
qtech & Wpfaff
NOTE: The settings in the top quote above IS what DHCP sets up which is part or all of the problem...
I thank you both for all your effort but it still doesn't work. I tried all your suggestions and settings to no avail. I can't even connect with the router. It makes connection with the card, at least it says that the connection is made but it doesn't work. The network stuff is just messed up. DHCP flat doesn't work and hasn't for me, since like i said about 3.3.1 or somewhere in there when something got changed. I'll continue to keep checking the releases until I find one that will work but Warren's got to figure out what's wrong with DHCP before that will happen.
DHCP
Posts: 613
Mike,
DHCP is controlled by the router, not Mepis.
The router uses DHCP to assign an IP address to each computer on the network. Mepis simply accepts whatever IP is offered by the router.
You can override this by setting a very specific static IP in Mepis as noted earlier.
With Ubuntu, the router gives you "192.168.2.39" for your IP. This means your router is using a range of IP addressess from
192.168.2.1 through 192.168.2.254
If you are seeing "192.168.79.1" in the Mepis OS center, then change every instance of a "79" to a "2" and restart eth0.
q
Good Luck and Stay on Em
Posts: 311
I have had the same problem since 3.4.1 came out....
I accuse udev a new completely rewritten alternative to kudzu or
(auto hardware).
I cannot use my machine with any version of Mepis from 3.4.1 on
I have posted probably 50 messages
Good Luck
I'm stuck at 3.3.1 stable release until either they go back and fix things or I find an alternative distro to move to...
DHCP I understand what you
Posts: 10
qtech
I understand what you are saying and I have tried that and it still doesn't work (just tried again). But just like the guy who jumped in right after your post (he has the same issue) and has had since 3.3.1 I think that's the version he said. I have had, and continue to have the same problem since about the same time. The settings that supposedly come from the router are completely different than the other 3 machines that are connected to it and they all work. With Mepis I can't even type in the router address and connect with the router ( I can with the other 3 ). Most of the settings compared to the other 3 are totally bogus. For instance, most of the other units are around IP 192.168.2.39, Bcast 255.255.255.255, Mask 255.255.255.0 Gateway notlisted but I assume it's 192.168.2.1 (router) (THIS WORKS on the others). Then you have the settings from Mepis, IP 192.168.79.1, Bcast 192.168.79.255, Mask 255.255.255.0, Gateway 192.168.79.1 (THIS DOESN'T work) even if you change all the 79's to 2. So, like the guy that posted after you there is still a problem someplace that happened back a bunch of versions ago that needs to be addressed. Thanks for all your time and trouble. Hopefully things can be fixed soon.
Mike
Hmm.
Posts: 613
Well, damn. It should have worked.
I can tell you that part of the confusion are these specific settings:
IP 192.168.79.1
Bcast 192.168.79.255
Mask 255.255.255.0
Gateway 192.168.79.1
They are 'static' setings that Warren leaves for reasons unknown (unless maybe they are simply an 'example'). They have nothing to do with anything and will generally not work for anyone else. However, they only effect you if the box for using a static address is ticked in the Mepis control center. If the box is un-ticked, then DHCP from the router comes into play.
If you wish, there are a couple more things we can try. If you'll change the static setting to 192.168.2.3 etc., (or maybe try .38 -your router's DHCP might have a smaller range of IPs than 1-254, it could be say 36-45. I can only make an educated guess without looking at the router configuration) and then run 'ifconfig -a' and post the results again, I can give you an idea of whats going on.
and of those 50 messages
Posts: 4864
the censor (myself) has removed a lot because they were completely repetitive.
And there isn't any real problem at 'being stuck at 3.3.1' really. My laptop is using an even older version, but everything that needs to is working so I have left it alone.
Well Hello
Posts: 311
So you know and understand that this udev thing has killed off some
legacy hardware ?
including
Posts: 4864
the pci-scsi card which runs my scanner
i have to boot into an old version now to use that.
Is this problem still open or was it resolved?
Posts: 3
I'm having the same problem with the recent distro (3.4) from Linux Format Mag.
I'm using a static address and not dhcp as my DSl provider has assigned me the static address. It works just fine with OS/2 and Winblows XP on the same machine (IBM Thinkpad - A31).
I'm a newbe to Linux and this isn't a good first experience! I'm at a point in my life that I don't want to be a techie, just load and go with the software.
Any ideas, or is it truly a software problem?
Thanks
Is this problem still open or was it resolved?
Posts: 2280
If you can look in the control panel hardware manager and post info on your network cards-chips maybe some one can give you an answer to your questions . There are so many its impossible to even guess. It may or maynot be supported.
jim
It's an Intel pro/100 VE &
Posts: 3
It's an Intel pro/100 VE & any help would be appreciated!
Mel
It's an Intel pro/100 VE &
Posts: 2280
Ok now in a console as normal user do a lspci to see what the system recognises and then lsmod to see if anything is loaded in the way of modules for it. You might copy and paste that or start your own thread & paste it so others will get involved .
jim
I found the problem. In this
Posts: 3
I found the problem. In this system the static IP setup requires a broadcast address (my other systems do not) and once I plugged in a dummy address it all took off.
So, I'm using Firefox on MEPIS to post this message.
Now on to explore more of the system (remember I'm new to Linux).
Thanks for your help!
Mel
Re: I found the problem. In this
Posts: 2280
I found the problem. In this system the static IP setup requires a broadcast address (my other systems do not) and once I plugged in a dummy address it all took off.
So, I'm using Firefox on MEPIS to post this message.
Now on to explore more of the system (remember I'm new to Linux).Thanks for your help!
Mel
Great glad you got it working! Have fun i think youll enjoy Mepis.
jim
Driver problem?
Posts: 36
Mike, maybe its worth to look at this threads:
http://www.mepislovers.org/modules/newbb/viewtopic.php?topic_id=14831&forum=23$
http://www.mepislovers.org/modules/newbb/viewtopic.php?topic_id=14274&viewmode=flat&order=ASC&start=0
I think also it is a problem with udev and/or a driver problem.
Andy
dhcp doesn't seem to work on mepis?
Posts: 95
Static IP works fine for me but can't get dhcp working at all on 3.4.3. Not sure if we have the same issue but it could be related.
In your case, do you actually get dhcp working?
Details-
Posts: 613
Describe your network configuration.
Post your output from ifconfig -a