Assuming that your router is at a.b.c.e then add the following to
the top of your startup script to eliminate the route created
by the gateway entry in the boot parameters.
routeDelete ( "a.b.c.0", "a.b.c.e" );
routeAdd ( "a.b.0.0", "a.b.c.e" );
This will allow communication with any host on network a.b.x.x.
You can be more specific about what you will allow by using
several routeAdd commands specifying only the subnets that
you will communicate with. For example this will allow communication
only with subnet a.b.10.x a.b.11.x.
routeAdd ( "a.b.10.0", "a.b.c.e" );
routeAdd ( "a.b.11.0", "a.b.c.e" );
Or if you don't want to allow any off-subnet communication then
perform the routeDelete() and don't bother with the routeAdd
above.
Jeff
- Navigate by Date:
- Prev:
Re: Problem talking CA across two CPUs in same crate??? Leonard J. Reder
- Next:
portable ca server john sinclair
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Problem talking CA across two CPUs in same crate??? Andrew Johnson
- Next:
mbboDirectRecord changes (3.13.4 vs 3.13.[1,2]) Brian McAllister
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|