Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Ubuntu 9.1 with a wireless connection which works well via DHCP.
I now wish to set up two different static IPs and still have the option to use DHCP but I want to retain control over which route is used and not have it select DHCP when I am trying to use a static IP.
This is easy on various Macs but my attempts to get it working on Ubuntu have failed.
I would prefer to stick to 9.1 - I tried later versions some years ago and found them OTT.
I have discovered that I can get it to remember my static settings by restarting immediately after inputting them in the GUI but I have not yet discovered how to stop it creating and attempting to use a new Auto DHCP route despite having DHCP switched off at the router.
I am happy to use command-line solutions or edit files directly as long as the GUI is retained for future use.
The link appears very useful - thanks - I will play with some of the commands later.
I tried the main release after 9.1 and did not like it - it had lost much of the simplicity I liked. There are probably better solutions than Ubuntu for me but I still had my original 9.1 install CD.
Upon further investigation the link is about wired server connections.
I assume that server commands may be the same in a non-server situation but wired commands are unlikely to be the same as wireless commands. This thread is about: 'Force Ubuntu to use wireless with static IP'.
Please see my earlier remarks about using Ubuntu 9.1.
As a Mac PPC user I have no concerns about unsupported OSs.
that's not how linuxes work.
and with EVERY problem you ask us, there's an almost 100% probability that it has at least partly to do with you using an EOL distro.
or we cannot offer advice or even a fix, because the first step will always be "update your system"...
i understand it wasn't easy to get your realtek thingy working, but you were told before that it would be neither harder nor easier on a current distro.
and with EVERY problem you ask us, there's an almost 100% probability that it has at least partly to do with you using an EOL distro.
or we cannot offer advice or even a fix, because the first step will always be "update your system"...
i understand it wasn't easy to get your realtek thingy working, but you were told before that it would be neither harder nor easier on a current distro.
There are many of Linux versions in use that are no longer supported - perhaps I will let others list a few !
Last edited by Neville Hillyer; 03-31-2017 at 09:59 AM.
Are you trying to configure a static IP address for a particular access point/router?
NetworkManager is the service that automatically finds and connects to access points or switches between wired and wireless on the fly. I don't remember if the nm-applet version running on Ubuntu 9.1 has the capability to set a static address for an each access point.
Please see my earlier remarks about using Ubuntu 9.1.
As a Mac PPC user I have no concerns about unsupported OSs.
On a system that is well supported you would have to hunt down the DHCP configuration file and change the arguments in it so that DHCP is not the default.
Like ondoho said in post #7 we really can't offer advise or a fix on such a old distro.
Even if the newer version of Ubuntu may seem OTT to you however; it's totally worth it to have the most current version installed. <seriously>
A system that is not supported has way too many security vulnerabilities. Aside from that the functionality of the libraries, API's, GUI and DE are generally misconfigured and things don't run or launch properly.
Are you trying to configure a static IP address for a particular access point/router?
NetworkManager is the service that automatically finds and connects to access points or switches between wired and wireless on the fly. I don't remember if the nm-applet version running on Ubuntu 9.1 has the capability to set a static address for an each access point.
I am trying to set up a laptop for use in various locations.
In these days of router hacking I prefer to make my routers as secure as possible and not transmit half the required information via DHCP. Also most of my router settings are non-default including the IP range.
I have discovered that Network Manager was designed to work with a combination of GUI and text data but the documentation/examples could be better. I suspect it is not as unreliable as most say but simply needs setting up properly.
Last edited by Neville Hillyer; 04-01-2017 at 05:35 AM.
On a system that is well supported you would have to hunt down the DHCP configuration file and change the arguments in it so that DHCP is not the default.
Like ondoho said in post #7 we really can't offer advise or a fix on such a old distro.
Even if the newer version of Ubuntu may seem OTT to you however; it's totally worth it to have the most current version installed. <seriously>
A system that is not supported has way too many security vulnerabilities. Aside from that the functionality of the libraries, API's, GUI and DE are generally misconfigured and things don't run or launch properly.
Your first link is about DHCP servers - I have a client !
The other link is too general to assist with locating anything in an old OS.
The only dhclient.conf file is a sample file at /etc/dhcp3/dhclient.conf
By sample file do you mean it's not the real configuration file?
What is the output of:
Code:
locate dhcp
IF you don't have /etc/dhcp/dhclient.conf than you would have to create one.
Each distribution is different so I don't think my configuration file (Debian based) would work on your Ubuntu system. I could be wrong:-
----------------------------------------------------------------------------------
root@fractcat:/home/Linuxcat# cat /etc/dhcp/dhclient.conf
# Configuration file for /sbin/dhclient, which is included in Debian's
# dhcp3-client package.
#
# This is a sample configuration file for dhclient. See dhclient.conf's
# man page for more information about the syntax of this file
# and a more comprehensive list of the parameters understood by
# dhclient.
#
# Normally, if the DHCP server provides reasonable information and does
# not leave anything out (like the domain name, for example), then
# few changes must be made to this file, if any.
#
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
#send host-name "andare.fugue.com";
send host-name = gethostname();
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#send dhcp-lease-time 3600;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
#require subnet-mask, domain-name-servers;
#timeout 60;
#retry 60;
#reboot 10;
#select-timeout 5;
#initial-interval 2;
#script "/etc/dhcp3/dhclient-script";
#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;
#alias {
# interface "eth0";
# fixed-address 192.5.5.213;
# option subnet-mask 255.255.255.255;
#}
#lease {
# interface "eth0";
# fixed-address 192.33.137.200;
# medium "link0 link1";
# option host-name "andare.swiftmedia.com";
# option subnet-mask 255.255.255.0;
# option broadcast-address 192.33.137.255;
# option routers 192.33.137.250;
# option domain-name-servers 127.0.0.1;
# renew 2 2000/1/12 00:00:01;
# rebind 2 2000/1/12 00:00:01;
# expire 2 2000/1/12 00:00:01;
Is your sample the same as mine?
The man page for dhcp should help you to make your own configuration file.
I'm sorry, Neville Hillyer but I can't create that file for your system. I don't have that skill yet. <still learning from the RHCE Exam Books>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
