Welcome, Guest. Please login or register.
Did you miss your activation email?
Wednesday 25 December 2024, 07:15:21 pm

Login with username, password and session length

Visit the official Endian Community Mailinglist  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  routing to network behind green
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: routing to network behind green  (Read 7774 times)
TheTortoise
Jr. Member
*
Offline Offline

Posts: 8


« on: Wednesday 17 November 2010, 09:53:18 am »

I believe this is similar to a post already made, but that post is from 2007 and I don't know if things have changed in version 2.4.0 that I am using.

Similar to the prior post:

I have a working connection to the Internet: eth1/Red

Then I have eth0/br0/Green using 10.15.0.1 with clients getting IPs DHCP - network is 10.15.0.0/24.

I have a third interface, that is eth2, connected to another network running 192.168.0.0/16. I configured it through the Network>>Interfaces>>Uplink editor>>Create an uplink feature. I set it to "Ethernet static" type, since the network it is connected to does not have DHCP, and gave it an IP of 192.168.0.200.

I then used the Network>>Routing>>Add a new route feature to set a new route. I set the source network to 10.15.0.0/24 and destination network to 192.168.0.0/16 and the set the "Route via" option to use the uplink on eth2 that I created.

I can ping the uplink/interface IP of 192.168.0.200, but I can't ping any of the other 192.168.#.# IP addresses that are in use on the network.

The routing table under Status>>Network status>>Routing table entries reports (I obscured some numbers with # symbols):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0 0.0.0.0         255.255.0.0 U     0      0        0 eth2
10.15.0.0       0.0.0.0         255.255.255.0   U     0      0        0 br0
174.#.###.#    0.0.0.0         255.255.252.0   U     0      0        0 eth1
0.0.0.0         174.##.###.1    0.0.0.0         UG    0      0        0 eth1

Am I unable to communicate with the systems on 192.168.0.0/16 because the gateway for that network is showing to be 0.0.0.0? Shouldn't be listed as 192.168.0.200?
Logged
TheTortoise
Jr. Member
*
Offline Offline

Posts: 8


« Reply #1 on: Thursday 18 November 2010, 04:01:22 am »

Never mind. Everything is working, there was a bad link to the switch.

So, to answer my own question, it is apparently correct that the gateway for the custom route still show 0.0.0.0.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

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