Skip navigation.
Home
Now Shipping Version 7.0

The Mepis Utilities tool fights back ! (Network)


Posts: 42

This is about Mepis Utilities -> Network Interfaces
No matter how one tries to insist that the gateway field (shown as four dots vacant before you fill it in) will be..
192.168.1.1 (the address of the router)
as soom as we go back to "Status" and click "Start eth0" , The attempt is forgotten.

It takes a full minute or so before the button goes over to "Stop eth0", but its all bananas because at no point in this entire dance does the network actually work properly!

We *DO* get a little tab pop up from KNemo on the command line claiming "eth0 connection established!

What counts for me is "ping -c 2 192.168.1.1" (can we ping the router?) followed by other pings to check DNS is OK.
Then discover the browser works Smiling None of this actually happens Sad
Attempts to open a terminal and run netcardconfig also go through the motions, but end up not working

I have a static address 192.168.1.x
The netmask is standard 255.255.255.0
The broadcast is standard 192.168.1.255
The gateway is supposed to be 192.168.1.1 BUT we cannot get it to "stick" there.

Is there anywhere a clearly set out list of what is supposed to be present in files in /etc/ and etc/network/ and perhaps whether or not a (Windows-style) reboot is needed to invoke them?

I am sure its not the hardware because it can be persuaded onto the internet with Knoppix. (Maybe I should just copy the Knoppix files!)
I really am not very good at this .. help.. Sad

RE:The Mepis Utilities tool fights back ! (Network)

The MEPIS OS Center has an annoying behavior - when you change any values on a tab you MUST click the APPLY button BEFORE you change to another tab.

You can, of course, bypass MOSC and set values in /etc/network/interface directly.
--
GreyGeek

At last! I got it figured

At last! I got it figured out.

The problems here were a combination of the setup stumble described by GreyGeek (many thanks) and an intermittent hardware connection to the network. About one third of the time it was operational, twice when I was checking it out with Knoppix.

It was steadily driving me mad. There was a danger I would become more familiar with Debian a-la-Knoppix than via Mepis!

I also will now opt for editing /etc/network/interface.

The /etc/gateways file has a long geeky command in it commented out. I will leave well alone. There is also /etc/hosts/ and /etc/hosts.allow and /etc/hosts.deny

Some places I just should not go! Thanks folks.

EnigmaOne's picture

I assume that this:#

I assume that this:

# /etc/gateways:<br />
#<br />
#<net | host> NAME1 gateway NAME2 metric VALUE<br />
<passive | active | external>

is what you're talking about. (Last commented line went and split on me. It's supposed to be all one line.)

Yeah...well....for those who may not know what that's all about...here ya go...

The general format of the entries contained within the /etc/gateways file is that of a single line of seven fields, following the form depicted above.

The seven fields have the following purposes:

<net | host>
Denotes the route destination field and indicates that one should specify the route to be to a network or specific host. In other words, "net" or "host" would go here.

NAME1
The name associated with the net or host destination. Name1 may be a dotted-decimal address, or a symbolic name; such as one would specify within the /etc/hosts or /etc/networks files.

gateway
Keyword. Indicating that the subsequent string is indicative of the gateway host.

NAME2
The name associated with the gateway host. Name2 may be a dotted-decimal address, or a symbolic name; such as one would specify within the /etc/hosts or /etc/networks files.

metric
Keyword. Indicating that the subsequent string is indicative of the "hop-count" to the destination host or network.

VALUE
Numeric. The number of gateways from the local network to the destination network.

<br />
<passive | active | external> 

The exchange of RIP information is not anticipated from a passive gateway.
An active gateway is handled like a network interface.
An external gateway is identified to inform the routed daemon that another routing process will install such a route and that alternative routes to that destination should not be installed.

We live to edify. Eye-wink

Home of the Point-N-Click Help Files
http://www.catb.org/~esr/faqs/smart-questions.html

Yes - thanks for the reply.

Yes - thanks for the reply. I had thought that it looked like quite a powerful way of pointing too a final gateway through a network, maybe one where the box connected to a router/modem is itself serving other PCs.

So - if after using netcardconfig, the PC is already set up to know the gateway is the router/ADSL modem, usually with an address something like 192.168.x , and there are no other networks involved, we can leave the /etc/gateways file alone.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.