ANNOUNCEMENT - New Slackware Book Scheduled for...

Main Page | Report this Page

Linux Forum Index » Linux - Slackware Forum » ANNOUNCEMENT - New Slackware Book Scheduled for...

Page 4 of 4 Goto page Previous 1, 2, 3, 4

Author

Message

Helmut Hullen...

Posted: Fri Sep 05, 2008 1:38 am

Guest

Hallo, Sylvain,

Du meintest am 05.09.08:

Quote:

Say you want a fixed IP in one wireless scenario and want to use
DHCP in another. Can you do that?

I'm not sure, as I've never tried. If you give the interface an IP
address by default, but also configure it for DHCP, that might work.
I've not tested that, though.

Usually DHCP uses a range from (p.e.) 192.168.0.60 to 192.168.0.240, it
works from high to low numbers.

If you give an interface a fixed IP address from the range 192.168.0.1
to 192.168.0.59: that works.
Then the client doesn't call for an IP address per DHCP.

You shouldn't take a fixed address from the DHCP range - that may
sometimes work, but not in all cases.

I don't know how to realise "give the interface an IP address by
default, but also configure it for DHCP".

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

Sylvain Robitaille...

Posted: Fri Sep 05, 2008 7:09 am

Guest

Mark Madsen wrote:

Quote:

I'm not continuing the discussion in order to argue, ...

discussion needn't be argument. I think we do basically agree, and I
think we both have the same basic intention (to suggest ways in which we
think the SLE book can be most useful to Slackware users).

Quote:

If you want to know details about your system's bootup sequence,
start at inittab, ...

... but that isn't really Slackware-specific (despite its appearance
at first look).

Hmm. It isn't like any of the other major distros, ...

It's a lot more similar than it appears at first glance. All of
the distributions you mentioned use a system-5 based initd. So does
Slackware. If I (or you) want to understand the boot sequence of any
of these distributions, the place to start looking is inittab, and the
scripts that it calls. This is an often misunderstood point about
Slackware.

Quote:

Alan would probably be better off writing his stuff than reading ours.

Ah, just 'cause we're writing it doesn't mean he's reading it! ;-)

--
----------------------------------------------------------------------
Sylvain Robitaille syl at (no spam) alcor.concordia.ca

Network and Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Sylvain Robitaille...

Posted: Fri Sep 05, 2008 7:49 am

Guest

Eef Hartman wrote:

Quote:

IPADDR[0]="192.168.7.80"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]="yes"

Won't work when you got a working DHCP server, as rc.inet1 tests for
the USE_DHCP first and ONLY if it is NOT yes it will use the static
IPADDR value.

Thanks for clarifying. I see from a quick glance at rc.inet1 that it
won't use the IPADDR setting at all if USE_DHCP = "yes". Hrmmm...
that's not the sequence I would have expected, but there it is. :-(

--
----------------------------------------------------------------------
Sylvain Robitaille syl at (no spam) alcor.concordia.ca

Network and Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

+Alan Hicks+...

Posted: Fri Sep 05, 2008 3:56 pm

Guest

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008-09-04, Jim Diamond <Jim.Diamond at (no spam) nospam.AcadiaU.ca> wrote:

Quote:

Aside from the DHCP/fixed-IP issue, I need to use a different
sendmail relay, I want different /etc/hosts.allow files, different
resolv.conf files (for various fixed IP scenarios), different ntp.conf
files, different IP forwarding and firewall rules, and so on,
depending on where I am. And start up a VPN tunnel in some places but
not others.

I'm not sure that any Linux distro will support this in their init
scripts; however, you might want to take a look at wicd. wicd is
maturing and should be able to handle your needs. It's a python app
with a daemon and a GUI client. I'm not certain how useful it would be
if you're not running X, but it can handle all these sort of odd-ball
cases with some tuning. wicd can run pre-connection, post-connection,
and disconnection scripts based on the SSID of the wireless network
you're connecting to. There should be a build script available at
slackbuilds.org. Older versions placed everything in /opt, but I
believe newer versions are storing things in /usr. HTH

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjBnPoACgkQrZS6hX/gvjr40ACdGMqkirZOB1ZeIGgAJBeEI1N6
fHQAn3bu5SNRmczfUsMBtFCUTf6GZ88n
=q5Fr
-----END PGP SIGNATURE-----

Jim Diamond...

Posted: Fri Sep 05, 2008 6:30 pm

Guest

On 2008-09-05, Sylvain Robitaille <syl at (no spam) alcor.concordia.ca> wrote:

Quote:

Jim Diamond wrote:

Aside from the DHCP/fixed-IP issue, I need to use a different sendmail
relay, I want different /etc/hosts.allow files, different resolv.conf
files (for various fixed IP scenarios), different ntp.conf files,
different IP forwarding and firewall rules, and so on, depending on
where I am. And start up a VPN tunnel in some places but not others.

Sounds like your needs are likely beyond most "typical" configurations.
Yes, but I don't think my needs are that unusual. I know some people

get around automagically changing their SMTP server by using things
like (*gag*) webmail when they are away from their LAN. (Titanic ;
Hindenburg ; Edsel ; webmail ; ...)

Quote:

I think in your case any Linux distribution would seem "arcane", if
we're defining "arcane" to mean that it can't do the above
automatically without your spending a lot of time configuring and
scripting.
I don't think that is a good definition of arcane. But anyway ...

Quote:

In your fixed-IP scenarios, could you not still use DHCP, but configure
a DHCP server in those cases to always assign the same IP address?
My wireless router does not seem to allow me to configure it to always

use the same IP. Yes, that is a shortcoming of the router, but there
you go.

Quote:

At least in those cases you could also have DHCP configure other
items, such as SMTP server, DNS resolvers, time servers, etc. You'd
have the benefit of a fixed address as well as that of dynamic
configuration.
I'm even more certain that I can't get the DHCP server on my router to

do any of that. Even if I could, I think (in my situation) a shell
script is far easier to set up, and more or less as convenient on a
day-to-day basic.

Quote:

So in the end, it seemed a lot simpler for me to write a custom shell
script than to shoehorn all this into the rc.d scripts. (But in
defence of slackware, I don't know if any other distribution has the
capability to do what I want either.)
The only other Linux distribution I have any real experience with
setting up wireless networking on is the Asus-modified Xandros that
comes on the EeePC. You would have to write custom scripts to get
any of the above.
And I suspect that is the case everywhere. But I don't think my

situation is completely unusual, either... I think a lot of people
tend to suffer through bad solutions to this problem, like the
afore-mentioned (*gag*) webmail.

Cheers.
Jim

Jim Diamond...

Posted: Fri Sep 05, 2008 6:35 pm

Guest

On 2008-09-05, +Alan Hicks+ <alan at (no spam) lizella.netWORK> wrote:

Quote:

On 2008-09-04, Jim Diamond <Jim.Diamond at (no spam) nospam.AcadiaU.ca> wrote:
Aside from the DHCP/fixed-IP issue, I need to use a different
sendmail relay, I want different /etc/hosts.allow files, different
resolv.conf files (for various fixed IP scenarios), different ntp.conf
files, different IP forwarding and firewall rules, and so on,
depending on where I am. And start up a VPN tunnel in some places but
not others.

I'm not sure that any Linux distro will support this in their init
scripts; however, you might want to take a look at wicd. wicd is
maturing and should be able to handle your needs. It's a python app
with a daemon and a GUI client. I'm not certain how useful it would be
if you're not running X, but it can handle all these sort of odd-ball
cases with some tuning. wicd can run pre-connection, post-connection,
and disconnection scripts based on the SSID of the wireless network
you're connecting to. There should be a build script available at
slackbuilds.org. Older versions placed everything in /opt, but I
believe newer versions are storing things in /usr. HTH

Thanks for the pointer, I hadn't seen that one before. I'll take a
closer look later, but it seems to cover the ground quite well. For
anyone starting from scratch, it looks like the way to go; in my case,
since I already have everything set up, the benefits aren't as clear.
But I'm glad you mentioned it.

Cheers.
Jim

Robby Workman...

Posted: Fri Sep 05, 2008 8:09 pm

Guest

On 2008-09-05, +Alan Hicks+ <alan at (no spam) lizella.netWORK> wrote:

Quote:

ACK on that.

Quote:

I'm not certain how useful it would be if you're not running X, but
it can handle all these sort of odd-ball cases with some tuning.

I spent several hours writing man pages documenting the configuration
file parameters and layout, so it's theoretically possible to set up
everything from the command line (but I've not tested it personally).
Once it's set up though, assuming you have the thing configured to
connect automatically, it doesn't require X to be running at all in
order to connect to *known* networks.

Adam (one of the two main developers) is working on a command line
client for it, so maybe when that matures, it will be just fine in
that regard.

Quote:

There should be a build script available at slackbuilds.org.

Indeed there is, or I have packages for 12.1 on my site.

Quote:

Older versions placed everything in /opt, but I believe newer
versions are storing things in /usr. HTH

That is correct - 1.4.x used /opt/wicd, but 1.5.x uses correct
FHS layout.

-RW

Page 4 of 4 Goto page Previous 1, 2, 3, 4 All times are GMT - 5 Hours The time now is Mon Dec 01, 2008 9:09 pm Linux Forum Index