News: This forum is now permanently frozen.
Pages: [1]
Topic: can connect but cant do anything else  (Read 2609 times)
« on: November 19, 2007, 18:10:08 »
logemann *
Posts: 11

Hi,

i have the following scenario:

DMZ on 192.168.100.0/24
LAN on 192.168.170.0/24 (where m0n0 sits on 192.168.170.1)
WAN some public IP Address range

Now i configured my PPTP Server to:

Server: 192.168.101.254
Range: 192.168.101.192/28

I also added a FW rule to allow everything on that PPTP Interface and added a user.

So i can connect successfully and can even ping the router on 192.168.170.1. When i try to ping another PC in the lan oder a printer or something, it says "Network is down". I also cant connect to the m0n0 webconsole on port 80.

I then also tried using LAN addresses for server and address range, without any success. What am i doing wrong here?

Thanks for info.

UPDATE:
I can connect the console on the m0n0wall DMZ IP on 192.168.100.1 and i also can ping servers in the DMZ. What is different with the LAN?

UPDATE2:
i see this log message sometimes when doing my ping-tests:

   /kernel: arplookup 192.168.170.12 failed: host is not on local network

What does that mean? I am definitely sure that this address is a valid host on my local network. Furthermore a traceroute from my logged in VPN client system revealed that M0n0wall routes the ping to my uplink (WAN Gateway) even though it manages the 192.168.170.0/24 network as LAN. I am confused!

Marc
« Last Edit: November 19, 2007, 22:26:31 by logemann »
« Reply #1 on: November 20, 2007, 22:40:02 »
logemann *
Posts: 11

Below is my current network diagram. I dont inserted the PPTP interface there with the network attached to it, but you can imagine its there when i enable PPTP Smiley
« Last Edit: November 20, 2007, 23:47:48 by logemann »
« Reply #2 on: November 20, 2007, 23:51:06 »
logemann *
Posts: 11

what a nice monologue Smiley

Ok, i sorted it out. It was a local problem on my notebook because of a damn virtual VMWare (Fusion) vmnet1 iface which occupied 192.168.170.1 which in turn lead to a routing table locally who send all requests to 192.168.170.x to the VMware interface.

I looked at the wrong place the last thousand hours grrrr. Now i reconfigured VMware so that vmnet1 sits on a different IP.

Marc
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines