Welcome, Guest. Please login or register.
Did you miss your activation email?
Tuesday 19 November 2024, 11:26:36 pm

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
14258 Posts in 4377 Topics by 6515 Members
Latest Member: hulteends
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  EFC v2.41 - routing not working to 'Source Network' but only for one IP address.
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: EFC v2.41 - routing not working to 'Source Network' but only for one IP address.  (Read 6459 times)
jr3151006
Full Member
***
Offline Offline

Posts: 13


« on: Tuesday 03 September 2013, 12:00:08 am »

Hi,

we have one Endian FW Community v2.41, it has the following interfaces (physical):

Eth0 = Br0 = Static IP (192.168.0.1/22)
Eth1 = Main = DHCP (behind ADLS Modem with DMZ settings - 10.1.1.2/24)
Eth2 = Uplink1 = DHCP (behind ADLS Modem with DMZ settings  - 10.0.0.2/24)
Eth3 = Uplink2 = Static IP (187.x4.2x5.x3/29)

We have another company in our building, using the following network Ip range for internal usage '200.255.255.0/24'; we provide one IP address (192.168.0.251/24) to they put on their Linux. Just to explain out environment, our company uses the 192.168.0.0/24 to servers, 192.168.1.0/24 to printers, 192.168.2.0/24 to computers and 192.168.3.0/24 to visitors/guest.

The access to their main server (200.255.255.1/24) worked fine after adding an entry at Network/Routing, like:

---------------------------------------------------
Source Network/IP = 192.168.3.10
Destination Network = 200.255.255.0/24
Route via = Static Gateway = 192.168.0.251
Enable = yes
---------------------------------------------------

But we need more servers/computers at our side reaching them; after change the "Source Network/IP" to a IP range, like "192.168.0.0/22" it didnīt work, also not work as "192.168.3.0/24" - even put it at the 'First' position in the 'Policy Routing' menu. In that case, the tracert command show that the packets we forwarded to main uplink (red interfaces).

#######################

Is there anything missing since we are able to route only PC/IP to another company/network but not able allow our internal IP range??
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

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