Re: my little network

On Fri, 26 May 2006, peter j norris <magicpeter@xxxxxxxxxxxx> wrote:-

peter j norris wrote:

this is what ifconfig said
ifconfig
eth0 Link encap:Ethernet HWaddr 00:0D:61:79:18:A8
inet6 addr: fe80::20d:61ff:fe79:18a8/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2541 errors:0 dropped:0 overruns:0 frame:0
TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:188052 (183.6 Kb) TX bytes:18576 (18.1 Kb)

modem0 Link encap:Point-to-Point Protocol
inet addr:203.220.204.17 P-t-P:203.220.249.177
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:18076 (17.6 Kb) TX bytes:2904 (2.8 Kb)
still cannot acess internet from other computers
is there anyone that can help me please

From these two, my guess is that you're using a dial-up account[0] and
would like to have you machine act as a gateway for the other machines
on your LAN.

If so there are a few things you'll need to do:

1, you need to set a static IP address for eth0;
2, you need to enable masquerading so traffic from machines on your LAN
appear to come from your machine;
3, you need to set up the other machines on your LAN so they use your
machine as the gateway;
4, you need to make sure that the default route is that of your dial-up
connection;

NB. The following is based on SUSE 10.0 and the graphical YaST, but
should apply to earlier versions as well. SUSE 10.1 is slightly
different, but not so much as to make a huge difference. The console
versions of YaST are very similar but require use of keys rather than
clicks.

#1 is fairly easy. Under YaST, Network Devices -> Network card you need
to reconfigure eth0. To do this:
select the network card and click on the edit;
enable "Static Address Setup";
since you already seem to be using 192.168.0.1, enter that in
the box for the IP address;
under routeing configuration, enable IP forwarding;

#2 may be fairly easy. My guess would be that you'd need to configure
the firewall to handle the masquerading. Unfortunately, since I
preferred to write my own iptables rules, I've never used the SUSE
firewall and can't help here.

#3 can be very easy, or fairly easy, depending on how many machines you
have on your network. If you've only a couple of machines, the easier
way would be to configure the other machines with static IP addresses,
give them your ISPs DNS servers and specify 192.168.0.1 as their
gateway.

If you have more than two other machines on your network, or expect to
add other machines in the future, a better idea would be to configure
your machine to be a DHCP server. To do this, under YaST, select Network
Services -> DHCP server. If you don't have the DHCP server installed,
YaST will install it for you.

Next, you'll be taken through the DHCP server wizard where you first
need to select the interface the server listens on by selecting the
interface and clicking on add. Once you've added the interface, click
next.

The next page is where you enter the DNS servers, the default gateway
(192.168.0.1), time server and lease time. Once you've entered the
required details (DNS server, gateway and, possibly, domain name), click
next.

The third page is where you enter the IP address range the DHCP server
will use when handing out IP addresses. My personal choice would be to
pick a start address of 192.168.0.32 and an end address of
192.168.0.127. This provides for upto 96 different machines connecting
to your network before addresses need to be reused. This is probably
overkill for a home network, but it's better to have spare space without
having to reconfigure sometime in the future.

Finally, on the fourth page, you get to choose when the server starts.
The default is for a manual start, but it's probably better the enable
it when booting.

#4 is also fairly easy. Under YaST, Network Devices -> Modem ->
Providers, you may need to edit the connection details under your
provider details. To do this:
select the provider you use (probably called comindico[1]) and
click edit;
click next;
click IP details;
if it isn't enabled, enable Default route;
click Okay;
click next;
click Finish.

These should help you get the machines on your network talking to the
outside world. I don't think I've missed anything, with the exception of
the firewall configuration. Unfortunately, that's the only part I can't
help you with.


[0] 203.220.204.17 has an rDNS of
dialup-17.204.220.203.acc01-fred-lau.comindico.com.au

Regards,
David Bolt

--
Member of Team Acorn checking nodes at 50 Mnodes/s: http://www.distributed.net/
AMD1800 1Gb WinXP/SUSE 9.3 | AMD2400 256Mb SuSE 9.0 | A3010 4Mb RISCOS 3.11
AMD2400(32) 768Mb SUSE 10.0 | Falcon 14Mb TOS 4.02 | A4000 4Mb RISCOS 3.11
AMD2600(64) 512Mb SUSE 10.0 | | RPC600 129Mb RISCOS 3.6
.

Relevant Pages

  • Re: SBS 2003 Win XP/2000 Pro Clients TCP/IP Problems
    ... network and no DHCP services provided by any machines still on the network. ... Check all machines for DNS entries. ... It really sounds like a IP Address conflict the way the server stops ... > PCs, 3 of which are running Windows XP Pro, the rest 2000 Pro. ...
    (microsoft.public.windows.server.sbs)
  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Problem getting a new XP computer to join an NT 4.0/Win 98 domain
    ... > the computers and the file server with the goal of getting ... > If you scan Network Neighborhood for the Entire Network after ... > booting, there are 3 workgroups: ... > machines to see and map to shares on the NT file server. ...
    (microsoft.public.win2000.networking)
  • Re: Connecting from Suse to windows workgroup on
    ... > pool of IPs) and I have just installed a Suse 9.3 Enterprise Server ... > From Suse pinging 127.0.0.1 works but no other machines on the Lan. ... problem with the network card or cabling... ...
    (alt.os.linux.suse)
Loading