On Sat, 2005-11-05 at 11:34 -0500, Robert Fitzpatrick wrote:

I have a problem seeing certain IP's in my own subnet assigned by the ISP, looking for help on how I can get it to work.

I have my SuSE Linux workstation with 192.168.1.25 behind a NAT router which is the default gateway for the workstation at 192.168.1.1. Now, I have a second IP in my wks within the subnet assigned by the ISP let's say 1.2.3.43/29, this is to allow hosting of some services, no firewall in place, yet. I have another Linux server at 1.2.3.44/29. I cannot see the other Linux server from my workstation. Perhaps routing can accomplish this for me, but I'm totally stupid on how to set that up, can someone suggest?

What brand of net router do you have? Most allow port forwarding to internal machines for supported services, i.e. mail HTTP etc. Why not have the nat router get the address from the ISP, use your internal network of 192.168.1.x and port forward. Why do you feel that you need internet routable addresses to provide services? The limitation is probably with your nat router not being able to handle more than one subnet. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

I have a problem seeing certain IP's in my own subnet assigned by the ISP, looking for help on how I can get it to work.

I have my SuSE Linux workstation with 192.168.1.25 behind a NAT router which is the default gateway for the workstation at 192.168.1.1. Now, I have a second IP in my wks within the subnet assigned by the ISP let's say 1.2.3.43/29, this is to allow hosting of some services, no firewall in place, yet. I have another Linux server at 1.2.3.44/29. I cannot see the other Linux server from my workstation. Perhaps routing can accomplish this for me, but I'm totally stupid on how to set that up, can someone suggest? I'm not sure exactly how you have this set up. The low cost Cable Modem Routers (Linksys, Netgear) really do not handle this well if you have multiple public IP addresses. Let's assume that you have 2 assigned IP addresses, 1 for the router and 1 for your server. External Network----------Switch---------Router----192.168.1 subnet | (.43) +--Server (.44) In this case, your default route should allow you to access the server, BUT

On Saturday 05 November 2005 11:34 am, Robert Fitzpatrick wrote: the server will not be able to directly access the 192.168.1 subnet directly unless one of those systems is set up as a DMZ host or you use port forwarding. A second NIC connected outside of the router would work, but the low cost routers can only handle a single subnet. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9