Linux behind a DSL Linksys bluebox

I have several computers behind one of those Linksys
DSL Blue Boxes. This is a good way to set up a
business system on the interenet, because the blue
box is too simple to be hacked from the outside
world as I understand it.

Anyway I have Samba working on the network.
Using Samba the computers know each other by
name. But how does one give names to the Linux
computers behind the blue box? The blue box
uses dhcp to give the computers ip addresses but
that is it. You cannot specify which MAC address
gets which IP.

It seems like the solution to this problem should be
fairly trivial and also useful. Is there a solution out
there?

Tom wrote:

> I have several computers behind one of those Linksys
> DSL Blue Boxes. This is a good way to set up a
> business system on the interenet, because the blue
> box is too simple to be hacked from the outside
> world as I understand it.
>
> Anyway I have Samba working on the network.
> Using Samba the computers know each other by
> name. But how does one give names to the Linux
> computers behind the blue box? The blue box
> uses dhcp to give the computers ip addresses but
> that is it. You cannot specify which MAC address
> gets which IP.
>
> It seems like the solution to this problem should be
> fairly trivial and also useful. Is there a solution out
> there?


You can use a hosts file in Linux, to map names to IP addresses. If you use
long lease times, your dhcp addresses will be virtually static. You can
also use static addresses, if you wish.

What if he sets the Linux workstation's DNS to this Linksys box? Does
the Linksys box serve up DNS services? Otherwise, yes, the /etc/hosts
file editing would be the trick.

"Google Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> What if he sets the Linux workstation's DNS to this Linksys box? Does
> the Linksys box serve up DNS services? Otherwise, yes, the /etc/hosts
> file editing would be the trick.
>

It is a hack though. I would like a more elegant solution. I don't
understand why there isn't one.

On Sun, 13 Mar 2005 23:30:50 -0600, Tom wrote:

>
> "Google Mike" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
>> What if he sets the Linux workstation's DNS to this Linksys box? Does
>> the Linksys box serve up DNS services? Otherwise, yes, the /etc/hosts
>> file editing would be the trick.
>>
>
> It is a hack though. I would like a more elegant solution. I don't
> understand why there isn't one.

Why are you using DHCP? Use static IPs and put the names in /etc/hosts.

"General Schvantzkoph" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> On Sun, 13 Mar 2005 23:30:50 -0600, Tom wrote:
>
> >
> > "Google Mike" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) oups.com...
> >> What if he sets the Linux workstation's DNS to this Linksys box? Does
> >> the Linksys box serve up DNS services? Otherwise, yes, the /etc/hosts
> >> file editing would be the trick.
> >>
> >
> > It is a hack though. I would like a more elegant solution. I don't
> > understand why there isn't one.
>
> Why are you using DHCP? Use static IPs and put the names in /etc/hosts.
>

If you had read the original post you
would know that:

I have several computers behind one of those Linksys
DSL Blue Boxes. This is a good way to set up a
business system on the interenet, because the blue
box is too simple to be hacked from the outside
world as I understand it.

Anyway I have Samba working on the network.
Using Samba the computers know each other by
name. But how does one give names to the Linux
computers behind the blue box? The blue box
uses dhcp to give the computers ip addresses but
that is it. You cannot specify which MAC address
gets which IP.

It seems like the solution to this problem should be
fairly trivial and also useful. Is there a solution out
there?

On Wed, 16 Mar 2005 23:48:35 -0600, Tom wrote:

>
> "General Schvantzkoph" <(E-Mail Removed)> wrote in message
> news(E-Mail Removed)...
>> On Sun, 13 Mar 2005 23:30:50 -0600, Tom wrote:
>>
>> >
>> > "Google Mike" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed) oups.com...
>> >> What if he sets the Linux workstation's DNS to this Linksys box? Does
>> >> the Linksys box serve up DNS services? Otherwise, yes, the /etc/hosts
>> >> file editing would be the trick.
>> >>
>> >
>> > It is a hack though. I would like a more elegant solution. I don't
>> > understand why there isn't one.
>>
>> Why are you using DHCP? Use static IPs and put the names in /etc/hosts.
>>
>
> If you had read the original post you
> would know that:
>
> I have several computers behind one of those Linksys
> DSL Blue Boxes. This is a good way to set up a
> business system on the interenet, because the blue
> box is too simple to be hacked from the outside
> world as I understand it.
>
> Anyway I have Samba working on the network.
> Using Samba the computers know each other by
> name. But how does one give names to the Linux
> computers behind the blue box? The blue box
> uses dhcp to give the computers ip addresses but
> that is it. You cannot specify which MAC address
> gets which IP.
>
> It seems like the solution to this problem should be
> fairly trivial and also useful. Is there a solution out
> there?

The Linksys box can limit DHCP to a specific range, IP addresses outside
of that range can be used for static IPs. Use static IPs on the Linux
boxes, there is no good reason to use DHCP.

On Tue, 15 Mar 2005 13:05:17 -0500, General Schvantzkoph wrote:
> Why are you using DHCP? Use static IPs and put the names in /etc/hosts.


That's what I do.
The firewall will hand out an IP (between .100 and .199) for any boxes
that ask for an IP but I have all my Linux boxes configured with IP
addresses in the .000 to .099 range, and defined in /etc/hosts on all the
machines. They never ask for an IP address from the firewall, and use IPs
outside the range assigned by the firewall.
Works great.

On Thu, 17 Mar 2005 12:23:09 -0700, Ed Skinner wrote:

> On Tue, 15 Mar 2005 13:05:17 -0500, General Schvantzkoph wrote:
>> Why are you using DHCP? Use static IPs and put the names in /etc/hosts.
>
>
> That's what I do.
> The firewall will hand out an IP (between .100 and .199) for any boxes
> that ask for an IP but I have all my Linux boxes configured with IP
> addresses in the .000 to .099 range, and defined in /etc/hosts on all the
> machines. They never ask for an IP address from the firewall, and use IPs
> outside the range assigned by the firewall. Works great.


Er, make that .001 to .099

"General Schvantzkoph" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> On Wed, 16 Mar 2005 23:48:35 -0600, Tom wrote:
>
> >
> > "General Schvantzkoph" <(E-Mail Removed)> wrote in message
> > news(E-Mail Removed)...
> >> On Sun, 13 Mar 2005 23:30:50 -0600, Tom wrote:
> >>
> >> >
> >> > "Google Mike" <(E-Mail Removed)> wrote in message
> >> > news:(E-Mail Removed) oups.com...
> >> >> What if he sets the Linux workstation's DNS to this Linksys box?
Does
> >> >> the Linksys box serve up DNS services? Otherwise, yes, the
/etc/hosts
> >> >> file editing would be the trick.
> >> >>
> >> >
> >> > It is a hack though. I would like a more elegant solution. I don't
> >> > understand why there isn't one.
> >>
> >> Why are you using DHCP? Use static IPs and put the names in /etc/hosts.
> >>
> >
> > If you had read the original post you
> > would know that:
> >
> > I have several computers behind one of those Linksys
> > DSL Blue Boxes. This is a good way to set up a
> > business system on the interenet, because the blue
> > box is too simple to be hacked from the outside
> > world as I understand it.
> >
> > Anyway I have Samba working on the network.
> > Using Samba the computers know each other by
> > name. But how does one give names to the Linux
> > computers behind the blue box? The blue box
> > uses dhcp to give the computers ip addresses but
> > that is it. You cannot specify which MAC address
> > gets which IP.
> >
> > It seems like the solution to this problem should be
> > fairly trivial and also useful. Is there a solution out
> > there?
>
> The Linksys box can limit DHCP to a specific range, IP addresses outside
> of that range can be used for static IPs. Use static IPs on the Linux
> boxes, there is no good reason to use DHCP.
>

How does the computer connect to the internet
without dhcp?