News: This forum is now permanently frozen.
Pages: [1]
Topic: Confused about transparent bridge setup for internal network  (Read 1245 times)
« on: January 19, 2010, 05:09:55 »
Blark *
Posts: 1

Hi folks.

I am attempting to set up m0n0wall to act as a transparent bridge between some VMs and the rest of our network. Our network infrastructure is actually MPLS managed by a 3rd party so all the IPs here are internal...

I tried to explain what I am trying to do but I thought it was easier to attach a flowchart (attached).

Basically it is working now, but I think that I did it wrong. I have set up a route on our network so that all traffic for 192.168.20.0/24 goes to 192.168.1.159... but it doesn't seem to be working 100%

Pings to any machine on the 192.168.20.0 network come back as 192.168.1.159 instead of whatever machine I pinged:

Code:
Pinging 192.168.20.198 with 32 bytes of data:
Reply from 192.168.1.159: bytes=32 time=14ms TTL=123
Reply from 192.168.1.159: bytes=32 time=13ms TTL=123
Reply from 192.168.1.159: bytes=32 time=25ms TTL=123
Reply from 192.168.1.159: bytes=32 time=13ms TTL=123

Also, while the machines on the ESX box work fine outbound, I can't seem to RDP in to any of them.

Sorry I am having a hard time getting my head around all of this. Your help would REALLY be appreciated.

Thanks




* m0n0wall.jpg (19.75 KB, 580x396 - viewed 210 times.)
« Last Edit: January 19, 2010, 05:19:13 by Blark »
« Reply #1 on: January 19, 2010, 19:07:39 »
rpsmith ***
Posts: 113

Interfaces: WAN

Bottom of the page:

"When set, this option blocks traffic from IP addresses that are reserved for private networks as per RFC 1918 (10/8, 172.16/12, 192.168/16) as well as loopback addresses (127/8). You should generally leave this option turned on, unless your WAN network lies in such a private address space, too."

also, your network diagram indicates your m0n0wall is routing not bridging.  

Roy...
« Last Edit: January 19, 2010, 19:19:09 by rpsmith »
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines