Dont know what I am doing. Yes this is basic can't seem to see the fault

I have 2 MT Rtr's
Ether 1
One with ip 41.168.6.68/26 ( gateway 41.168.6.65)
Standard rule 0.0.0.0.0/0 - 41.168.6.65
Ether2
10.0.0.1/24

The masqurade is src ip 10.0.0.0/8
Dst !10.0.0.0/8

I have an added route 41.168.6.84 - 10.0.0.2 ( via ether 2)
Rtr 2
Ether 1 10.0.0.02/24
route 0.0.0.0/0 - 10.0.0.01

If I tourch I see the ip comming from 196.33.159.131 on ether1

see nothing on ether2 or on second router
Can somebody pls tell where I am stupid

Tnx

get rid of your "!dst address" and change the "out interface" to ether1?

Thanks no luck

I have an added route 41.168.6.84 - 10.0.0.2 ( via ether 2)

What is the goal here?

You should have posted this in General instead of Hardware. You would get more responses on this subject.

Did not think of the posting place thanks . I am trying to route the 41.168.6.X ip's to the wireless network. Router 1 is connected to internet and router 2 10.0.0.2 connected to wifi and fiber network.
The ip 41.168.6.84 reaches ether 1 but does not leave on ether2 or arrive at router 2 on ip 10.0.0.2

All networks via fiber wireless etc comes from ip 10.0.0.2 on ether 2 get nated by router 1 and then leaves to the internet. works 100% ip 41.168.6.68 works from internet. Ip 41.168.6.84 is arriving on ether1 but some how I am doing something stupid as I can't get it to go to 10.0.0.2 on ether2

from a client located within the 10.0.0.0/8 address space, can you ping the default gateway on 41.168.6.65? If you can, then the problem is elsewhere. If you can't ping the default gateway, then either it is not responding to ping on purpose or you still have some other problem.

Looking at your partial list of some of the routes you have, I suspect the problem is now there.
(41.168.6.64/26 also contains the same subnet as your default gateway - was this allocated via DHCP>?). Investigate throughly your subnetting on all interfaces to make sure you have no overlap, otherwise how does a packet know where to go? All interfaces should have non overlapping address ranges. But print off the full list of all your routes, then we can see better what is going on

The ip range is static 41.168.6.65 is the gateway 41.168.6.68 is the router ip and the ip's are routed statically from ip 41.168.6.65 to ip 41.168.6.68

Address: 41.168.6.68 00101001.10101000.00000110.01 000100
Netmask: 255.255.255.192 = 26 11111111.11111111.11111111.11 000000
Wildcard: 0.0.0.63 00000000.00000000.00000000.00 111111
=>
Network: 41.168.6.64/26 00101001.10101000.00000110.01 000000 (Class A)
Broadcast: 41.168.6.127 00101001.10101000.00000110.01 111111
HostMin: 41.168.6.65 00101001.10101000.00000110.01 000001
HostMax: 41.168.6.126 00101001.10101000.00000110.01 111110
Hosts/Net: 62

This is the routing table:
[mnr.theweb.co.za] /ip route> print
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 A S ;;; ROute to Internet
0.0.0.0/0 41.168.6.65 1
1 A S ;;; Route to Wireless Network
10.0.0.0/8 10.0.0.2 1
2 ADC 10.0.0.0/24 10.0.0.1 ether2 0
3 S ;;;
10.0.103.0/24 10.1.254.1 1
4 S ;;;
10.1.251.0/24 10.1.254.1 1
5 S ;;;
10.1.253.0/24 10.1.254.1 1
6 S ;;;
10.1.254.3/32 10.1.254.1 1
7 S ;;;
10.1.254.254/32 10.1.254.1 1
8 ADC 41.168.6.64/26 41.168.6.68 ether1 0
9 A S ;;;
41.168.6.75/32 10.0.0.2 1
10 A S ;;; Alan Cove Cameras
41.168.6.80/32 10.0.0.2 1
11 A S ;;;
41.168.6.81/32 10.0.0.2 1
12 A S ;;;
41.168.6.82/32 10.0.0.2 1
13 A S ;;;
41.168.6.83/32 10.0.0.2 1
14 A S ;;;
41.168.6.84/32 10.0.0.2 1
15 A S ;;;
41.168.6.96/32 10.0.0.2 1
16 A S ;;;
41.168.6.97/32 10.0.0.2 1
17 A S ;;;
41.168.6.98/32 10.0.0.2 1
18 A S ;;;
41.168.6.99/32 10.0.0.2 1
19 A S ;;;
41.168.6.120/29 10.0.0.2 1
20 ADC 192.168.0.0/24 192.168.0.1 ether3 0
21 ADC 192.168.1.0/24 192.168.1.1 ether4 0
22 ADC 192.168.2.0/24 192.168.2.1 ether5 0

I must say that no ip 41.168.6.X is reaching router 2 ( 10.0.0.2) via tether 2

from a client located within the 10.0.0.0/8 address space, can you ping the default gateway on 41.168.6.65? If you can, then the problem is elsewhere. If you can't ping the default gateway, then either it is not responding to ping on purpose or you still have some other problem.

Looking at your partial list of some of the routes you have, I suspect the problem is now there.
(41.168.6.64/26 also contains the same subnet as your default gateway - was this allocated via DHCP>?). Investigate throughly your subnetting on all interfaces to make sure you have no overlap, otherwise how does a packet know where to go? All interfaces should have non overlapping address ranges. But print off the full list of all your routes, then we can see better what is going on

All outgoing data is working 100% only data from 41.168.5.65 to 10.0.0.2 is not working. But the routing from router 2 to router 1 and then out is working 100%

Your last post suggests you want two way traffic to be possible - then you will need a dst-nat as well as a src-nat rule? I assumed you wanted to perform only one way masquerade (i.e. the normal requirement for most people). Is this what you want? That all traffic arriving at your default gateway is to all go to one internal IP or do you want only some traffic types and destination ports to go to specific internal IPs?

That is 100% correct.
All out going traffic gets natted to 41.168.6.68
The incoming traffic get routed to the clients cpe.
Currently I have 62 ip's with another 1024 on the way
I would like to route all traffic types from the internet to the remote cpe. No port no ... must be blocked

What a waste of time. Was digging into the network and trying to look at all possibilities. The fault.
Simple and basic. The ip's was not routed to the unit only the gateway worked. We are waiting for the inter connect supplier to fix the routing.

Thanks to all and many thanks to nest.

We will use them as support and additional help

I CAN RECOMMEND THEM !!!