Koozali.org: home of the SME Server

Unable to reach server on local network from SME server

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Unable to reach server on local network from SME server
« on: September 01, 2007, 02:09:16 PM »
Hi,

I have recently bought a wireless router (Linksys WRTG54GL) to make connecting laptops a little easier. The setup is like this:
Code: [Select]
      WAN
       |
  SME Server (local 192.168.55.0:255.255.255.0)
       |
   WRTG54GL (192.168.55.251)
       |
Local network (10.0.0.0:255.255.255.0)
I have assigned the Linksys WRTG54GL router a fixed IP address using the MAC address and added a local network to SME Server like this:
network: 10.0.0.0
subnet: 255.255.255.0
router: 192.168.55.251

I have disabled the firewall on the Linksys WRTG54GL router.

Now I would like to try and access a server on my local network (10.0.0.0:255.255.255.0) from my SME Server (192.168.55.251) as I want to configure a proxypass forward to the server in the localsubnet but that somehow fails. I can ping the server but a traceroute does not resolve the route to the host, and connecting to a webserver or telnet port on that host does not work. From the server in the local subnet I am able to access the SME Server and traceroutes also resolve properly.

The routing table on my SME Server looks like this:
Code: [Select]
[root@homer ~]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.55.0    0.0.0.0         255.255.255.0   U         0 0          0 br0
192.168.55.0    0.0.0.0         255.255.255.0   U         0 0          0 eth0
10.0.0.0        192.168.55.251  255.255.255.0   UG        0 0          0 br0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth1
I have the smeserver-openvpn-bridge contrib installed and that is why my routing table has a br0 interface listed. Could that be the problem?

The routing table on my server in the local network looks like this:
Code: [Select]
[root@localhost html]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.0.0.0        0.0.0.0         255.255.255.0   U         0 0          0 eth0
192.168.113.0   0.0.0.0         255.255.255.0   U         0 0          0 vmnet1
192.168.180.0   0.0.0.0         255.255.255.0   U         0 0          0 vmnet8
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
0.0.0.0         10.0.0.1        0.0.0.0         UG        0 0          0 eth0

Who can help me solve the problem or tell me what needs to be done/corrected?
« Last Edit: September 01, 2007, 02:13:19 PM by cactus »
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline mmccarn

  • *
  • 2,626
  • +10/-0
Re: Unable to reach server on local network from SME server
« Reply #1 on: September 01, 2007, 05:05:13 PM »
Have you created a 'local network' on your SME to tell it to route 10.0.0.0/24 through 192.168.55.251?

When you access your SME from your local network, does the traffic originate from 10.0.0.x or from 192.168.55.251?  That is, is your Linksys still doing NAT?  If so, you won't get anything back through the Linksys from the WAN side with out:

- turning off NAT (set 'router' mode?)
- creating port forwarding rules
- setting up a 10.0.0.x host as the 'DMZ' on the Linksys.

It's a lot easier if you get a WAP54G instead...

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Unable to reach server on local network from SME server
« Reply #2 on: September 01, 2007, 07:50:56 PM »
Have you created a 'local network' on your SME to tell it to route 10.0.0.0/24 through 192.168.55.251?
Yes I did as stated above.

When you access your SME from your local network, does the traffic originate from 10.0.0.x or from 192.168.55.251?  That is, is your Linksys still doing NAT?  If so, you won't get anything back through the Linksys from the WAN side with out:

- turning off NAT (set 'router' mode?)
It turned out that switching to router was the key to solving the problem, all other steps were unnecessary! Stupid I did not think of that.

It's a lot easier if you get a WAP54G instead...
Thanks for your help, it seems that a WRTG54GL is even easier after all. :-)
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)