Routing 'up' and 'down'.

[George Zeeman]

Hi, I am a starter on this matter, and my questions concern an existing configuration/situation.

It is about a router (edge) with private ip address 10.66.0.1. One of the ports has ip address 10.66.0.3 and is connected to a second router. Another port (10.66.0.4) is connected to a workstation.

The second router has ip address 10.66.34.1 and has a printer connected on one port (10.66.34.2) and a server on another port (10.66.34.3).

My questions are: (1) with this configuration is it possible for the workstation tot connect to shared folders on the server or to print to the printer? And (2) is it possible to connect from the server to shared folders on the workstation? And if ‘yes’: (3 and 4) how should routing be configured on the routers to accomplish this?

Thanks in advance.

George

[Mohieddin Kharnoub]

Hi

I think you mean by the Router a Routing Switch, right ?

With a routing switch you can do what do want to achieve.

Simply, consider the first subnet 10.66.0.0 as one Vlan, and the second subnet 10.66.34.0 as another Vlan.

You need to enable routing between them, and let both routing switches exchange the routing table between each other.

If this answered your question 1&2 , then to configure this we need to know the Model of the switches and the Mask for both subnets.

Good Luck !!!

[George Zeeman]

Thanks Mohiddin.

I'm glad to hear it's possible ;-)

These are the routing switches:
The first one (edge) is a SMC7908WBRA and the second a SMCWBR14T-G.

The mask of the 10.66.0.0 subnet is 255.255.224.0 and the mask of the 10.66.33.0 subnet is 255.255.255.224.

The first routing switch has a routing table entry:
Network address Subnet mask Gateway
10.66.0.0 255.255.224.0 10.66.0.1 (WAN)

On this switch RIP v2 is enabled for the LAN.


The second router switch has a routing table entry:
Network address Subnet Mask Gateway
10.66.0.0 255.255.224.0 10.66.0.1 (WAN)
10.66.0.1 255.255.255.255 10.66.0.1 (WAN)
10.66.34.0. 255.255.255.224 10.66.34.1 (LAN)


I am not sure if a can remove/change these settings because, taking from the ip assignments, they have been generated by the configuration software.
And it obviously is'nt doing what I want.
But I can add static routing table entries if needed.

I hope this info helps you. If you need more please let me know.

George

[Mohieddin Kharnoub]

Hi

I think you should add on the FIRST router the following Static Route:

Network address Subnet Mask Gateway
10.66.34.0 255.255.255.224 10.66.0.3

Where the 10.66.0.3 is the Second router IP (correct me if i'm wrong )

Now after adding that Static route, the first router knows how to reach the 10.66.34.0 subnet and the Second Router as we can see from the routing table, it knows how to reach the 10.66.0.0 subnet through 10.66.0.1

After that, you should check the gateways of the PC and the Printer
PC should have a GW: 10.66.0.1
Printer should have a GW: 10.66.34.3

That should be enough for them to communicate.

Good Luck !!!

[George Zeeman]

Hi Mohieddin,

It took some time because it works for 50%, and so I tried all kind of ways to get the right result.

After adding the static route on the first router I can ping and reach the PC from the server site. That's fine!

But I cannot reach the printer or the server from the PC. I can ping the GW 10.66.0.1. But when I ping the server or the printer from the PC, GW 10.66.0.1 replies: Cannot reach target subnet.
So 'going up' works, but 'going down' does'nt.

So the question that's pondering me is why the route from server 10.66.34.3 via GW 10.66.34.1 up to port 10.66.0.3 from GW 10.66.0.1 to the PC 10.66.0.4 actualy works, but the same route down does not.

If you have any further suggestions I'd be greatfull.

George

[George Zeeman]

As I am not getting another response for some time I am considdering to close this thread.

But the question that keeps me busy is how it is posible after adding the static route (as pevious descibed) to the first routing switch does not enable to 'route down'. But that is does enable to 'route up'. For to route up the second routing switch has to learn from the first routing switch how to route. So the first routing switch must have passed this info to the second routing switch. How than is it not possible to route from the first routing switch to the second?

If someone has an idea I'll be glad to hear. So I'll wait a week or so and than... close this thread. Thanks anyway everybody.

George

[George Zeeman]

I have no solution yet.