[Wylug-help] Help needed setting up server and LAN
Chris Davies MBCS
chris.davies at bcs.org.uk
Fri Aug 17 13:19:36 BST 2007
Mike Goodman wrote:
> 5. Configure the Router to have a route to 192.168.1.0/24 // Broken.
> The router (coming out in sympathy with me, I presume ;o) ) doesn't
> understand this syntax. I can get a specific IP address to a specific IP
> address, but not to a range.
At the risk of letting you stuff you already know, don't get confused between
port forwarding and routing.
Port forwarding lets you forward inbound connections on a specific port (e.g.
80 for web traffic) to a specific internal IP address. Routing tells the
Netgear where to send packets based on their destination network address.
The terminology 192.168.1.0/24 is shorthand for "the network 192.168.1.0 with
a 24-bit netmask, i.e. 255.255.255.0". On a Netgear DG814 configuration of
such routes can be found under Advanced - Static Routes
(http://192.168.1.0/staticroutes.htm).
>> 6. Install something like "dhcp3-server" and configure
>> /etc/dhpc3/dhcpd.conf (more on that later)
> eerrmm - shouldn't I have done this earlier? Now the connection's
> broken, it won't download.
Your interfaces should be defined as static, so the presence (or absence) or a
DHCP Server is moot - as long as the interface is up, of course.
>> Networks are defined in /etc/network/interfaces (see "man
>> interfaces"), e.g.
> Hmm. Error message says can't read /etc/network/interfaces at every
> attempt to make a connection and at shutdown. At boot, there's a message
> which flies by, to the effect that no network facilities are set up so
> failed. As always, this must be fixable - but where to start?
Log in as root and try this:
ifdown eth0 # Don't worry if it says it's already down
ifup eth0 # This should "just work" silently
You should then have an interface defined for eth0, i.e. "ifconfig eth0"
should show you an IP address, etc.
Chris
More information about the Wylug-help
mailing list