Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 28 December 2024, 12:42:08 am

Login with username, password and session length

Download the latest community FREE version  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Connect 2 internal Lan
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Connect 2 internal Lan  (Read 19282 times)
the_driver
Jr. Member
*
Offline Offline

Posts: 4


« on: Friday 02 September 2011, 01:47:48 am »

Hi all , i want to connect 2 LANs with these subnets:

lan1  --> 192.168.0.0/24 (office physical lan)
lan2 --> 192.168.1.0/24  (hyper-v internal lan)

lan2 is virtual because is a network used by virtual machines (it is internal of HYPER-V, a vmserver inside Lan1).

I have created a virtual machine in HYPER-V with endian community, with 3 Lan cards: eth0 is connected with lan1 (through hyper-v) as GREEN , eth1 is connected to hyper-v internal lan as BLUE. I dont want use RED INTERFACE (is it possible???)

GREEN and BLUE must communicate between,without filters.

Can i use endian like bridge?



Is it possibile?

thx



Logged
fqureshi
Sr. Member
****
Offline Offline

Posts: 126


« Reply #1 on: Friday 02 September 2011, 08:28:25 am »

Would you please state briefly what you want to achieve?
Logged
the_driver
Jr. Member
*
Offline Offline

Posts: 4


« Reply #2 on: Friday 02 September 2011, 07:27:14 pm »

I currently have a private network (LAN1) with this subnet : 192.168.0.X/24
This is a physical LAN. Inside of it there are domain controllers, clients, printers and so on.
In these days I have implemented a virtual server (Hyper-V), having inside many virtual machines.
I have created a second LAN inside Hyper-V (LAN2) with the subnet : 192.168.1.X/24
This network is internal to Hyper-V and is not bridget to LAN1.
Next, I implemented a virtual machine with an endian firewall. This machine has two network adapters
(eth0, eth1). eth0 is bridged with LAN1 and eth1 is inside LAN2.
I want to setup routing between LAN1 and LAN2 (green and blue, I think) because I need
clients from LAN1 to be able to access both machines from LAN2 and Internet (LAN1 has a physical firewall
connected to the ISP router). Furthermore, clients of LAN2 should be able to access specific machines in LAN1
and go on Internet through LAN1.
Logged
fqureshi
Sr. Member
****
Offline Offline

Posts: 126


« Reply #3 on: Saturday 03 September 2011, 10:53:56 pm »

If you have already defined ips on ur network card then everything should be working as endian will be responsible for the routing...

Would you please paste the output of the following command:

Netstat -rn


I prefer you do it from console....

Also if you can attach snapshot of interfaces under endian firewall. It will help to come up to a solution. N thanks for taking time and providing details...
Logged
the_driver
Jr. Member
*
Offline Offline

Posts: 4


« Reply #4 on: Tuesday 06 September 2011, 02:05:09 am »

Ok,

in this post wou will find 2 schema..

First one is the current lan configuration.

Second one is the target. Clients of private Lan must see clients of virtual network. Virtual network must be a separated network. With Endian (implemented like a virtual machine in Hyper-V) I want to create a Bridge between the two LANs.

Netstat result

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.0.254     192.168.0.58     30
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.0.0    255.255.255.0         On-link      192.168.0.58    286
     192.168.0.58  255.255.255.255         On-link      192.168.0.58    286
    192.168.0.255  255.255.255.255         On-link      192.168.0.58    286
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    276
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    276
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.56.1    276
        224.0.0.0        240.0.0.0         On-link      192.168.0.58    286
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.56.1    276
  255.255.255.255  255.255.255.255         On-link      192.168.0.58    286
===========================================================================



THANK YOU!!!
Logged
fqureshi
Sr. Member
****
Offline Offline

Posts: 126


« Reply #5 on: Tuesday 06 September 2011, 12:37:04 pm »

Ok. I belv we might need to first isolate network segments.

Are you able to ping from network client to virtual clients? If you trace yahoo.com from virtual client, which gateway it takes and where it stops?
tracert yahoo.com or traceroute yahoo.com

Also try to ping from your endian firewall to your virtual client and your network client. Are you able to ping it?

and are you talking about VMware? what do you mean by VMserver?
Logged
the_driver
Jr. Member
*
Offline Offline

Posts: 4


« Reply #6 on: Wednesday 07 September 2011, 07:38:33 pm »

VMServer is Hyper-V


No, I cant ping clients from private network to virtual . Also I cant ping clients from virtual to private network.

When I change gateway on clients (on private network) and set Endian Ip address, I can ping virtual clients.

But I dont want to set  Endian Ip , because clients use 192.168.0.254 for gateway (and go outsite to the web)



Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #7 on: Wednesday 14 September 2011, 12:33:54 am »

If your Endian isn't the default gateway, you must create an static route on your 192.168.0.254 gateway.
that route must send 192.168.1.X traffic to the Endian IP on 192.168.0.X.
Your 192.168.1.X machines must have Endian as Gateway (the 192.168.1.X IP of Endian).
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.111 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com