Steele DGC Network: Difference between revisions
From Murray Wiki
Jump to navigationJump to search
No edit summary |
mNo edit summary |
||
| Line 9: | Line 9: | ||
Ken and Andrew transferred 4 machines out of the development cluster to Steele. These have been set up and are working, but don't have NIS or NFS services => only root and team can log in. We are currently using the DGC wireless access point as a NAT box so that the local network is 192.168.0.x. The access point is set up as 192.168.0.1 so that it can serve as a gateway and also route DNS request. | Ken and Andrew transferred 4 machines out of the development cluster to Steele. These have been set up and are working, but don't have NIS or NFS services => only root and team can log in. We are currently using the DGC wireless access point as a NAT box so that the local network is 192.168.0.x. The access point is set up as 192.168.0.1 so that it can serve as a gateway and also route DNS request. | ||
--[[User:Murray|Murray]] 20:17, 12 June 2006 (PDT) | --[[User:Murray|Richard Murray]] 20:17, 12 June 2006 (PDT) | ||
Latest revision as of 03:17, 13 June 2006
This page describes the proposed network structure for the DGC network in Steele and CES.
Status update
Initial transfer of development PCs to Steele
Ken and Andrew transferred 4 machines out of the development cluster to Steele. These have been set up and are working, but don't have NIS or NFS services => only root and team can log in. We are currently using the DGC wireless access point as a NAT box so that the local network is 192.168.0.x. The access point is set up as 192.168.0.1 so that it can serve as a gateway and also route DNS request.
--Richard Murray 20:17, 12 June 2006 (PDT)
