> Here is what we put in st.cmd to get IOCs to be able to talk both to the
> outside world and to each other:
>
> routeAdd "0","164.54.160.1"
> routeDelete "164.54.160.0","164.54.160.1"
>
> which, as I understand it first tells the IOC to go to 160.1 for all
> connections, but then says that any connections on the local subnet should not
> go through this router.
I don't recommend giving VxWorks such a wide-open default, for security reasons.
Unless your router itself (164.54.160.1 in the example above) is carefully
configured--or some external router beyond that is acting as a serious
firewall--you are open to many attacks using TCP. VxWorks is not very
secure (although it is quite *OBSCURE*). I do recommend adding just: 1) host
routes to specific hosts that you intend to use CA; and 2) net routes to nets
that you know are truly secure--and have intended CA hosts on them.
- Navigate by Date:
- Prev:
IOC communication Mark Rivers
- Next:
Power PC floating point underflow William Lupton
- 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:
IOC communication Mark Rivers
- Next:
Power PC floating point underflow William Lupton
- 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
|