We have a Class B network 145.75.0.0 that is connected to the internet
with a portmaster using RIP. We currently want to connect a few class c
subnets to the portmaster. The 145.75.75.0 net is the 'backbone' on which
the portmaster is (the portmaster has ip# 145.75.75.250) located . On that
same network is another router 145.75.75.253/145.75.20.253 that is the
router for the 145.75.20.0 network.
If a machine from the 20 network (eg 145.75.20.78) pings the portmaster,
the portmaster sends out an arp request for that machine, instead of
sending the reply to the router.
Here is our routing table:
Portmaster> show routes
Destination Gateway Flag Met Interface
--------------------- -------------------- ---- --- ---------
0.0.0.0 145.41.13.193 NS 1 ptpW1
145.75.20.0 145.75.75.253 HS 2 ether0
145.75.75.0 145.75.75.250 HS 1 ether0
145.41.13.193 145.41.13.193 HL 1 ptpW1
145.75.75.235 145.75.75.236 HS 2 ether0
145.75.0.0 145.75.75.250 NL 1 ether0
Portmaster>
So, packets from 145.75.20.78 should be send to 145.75.75.253, and no arp
requests for 145.75.20.x should be generated.
The only possible thing I can come up with, is that because of the RIP
learned route 145.75.0.0 (from our isp or deduced from the settings of the
w1/ether0 port ?) is used before 145.75.20.0.
Is there anyway this problem can be solved?
Paul Wouters