Linux behind a DSL Linksys bluebox

Linux behind a DSL Linksys bluebox

Post by Tom » Fri, 11 Mar 2005 13:33:33



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?

 
 
 

Linux behind a DSL Linksys bluebox

Post by James Knot » Fri, 11 Mar 2005 23:15:07



> 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.

 
 
 

Linux behind a DSL Linksys bluebox

Post by Google Mik » Sun, 13 Mar 2005 08:21:54


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.
 
 
 

Linux behind a DSL Linksys bluebox

Post by Tom » Tue, 15 Mar 2005 14:30:50



Quote:> 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.
 
 
 

Linux behind a DSL Linksys bluebox

Post by General Schvantzkop » Thu, 17 Mar 2005 03:05:17





>> 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.
 
 
 

Linux behind a DSL Linksys bluebox

Post by Tom » Fri, 18 Mar 2005 14:48:35






> >> 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?

 
 
 

Linux behind a DSL Linksys bluebox

Post by General Schvantzkop » Sat, 19 Mar 2005 02:09:47








>> >> 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.
 
 
 

Linux behind a DSL Linksys bluebox

Post by Ed Skinne » Sat, 19 Mar 2005 04:23:09



> 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.
 
 
 

Linux behind a DSL Linksys bluebox

Post by Ed Skinne » Sat, 19 Mar 2005 10:10:43




>> 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
 
 
 

Linux behind a DSL Linksys bluebox

Post by Tom » Sun, 20 Mar 2005 13:43:33









> >> >> 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?
 
 
 

Linux behind a DSL Linksys bluebox

Post by David Schwart » Sun, 20 Mar 2005 14:29:55



Quote:>> 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?

    The way he said in the paragraph you cited above, static IPs.

    DS

 
 
 

Linux behind a DSL Linksys bluebox

Post by Davi » Sun, 20 Mar 2005 14:57:39


Quote:> How does the computer connect to the internet
> without dhcp?

Static IP ;)
 
 
 

1. DSL with Linksys and Pacbell dsl

very new to solaris

i have a pc, thats working fine with linksys router via pacbell dsl. i
am now trying to connect my ultra solaris box to the router(another
port). what r the files that i have to configure in solaris for this.
the following r the results of ipconfig from my pc

DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 63.203.35.55
                                    206.13.28.12

2. HELP, can't get ghostview working

3. Problems w/ setting up a Linux DMZ Server behind a Linksys Router

4. Help: fresh Linux install OK except modem

5. Q: SSH to Linux behind Linksys router

6. Problem in printing in Solaris 2.5

7. Linux firewall behind Cisco DSL Router

8. FTP Setup

9. Is Windows beating Linux behind a Linksys box?

10. Linux behind a Linksys router

11. Setting up email in Linux behind Linksys Router

12. linux behind linksys - configuration of server

13. Linux server behind Linksys router problem!!