[Irinikus]

Is this the setup that I must use?

---

Ikrinus.. how the feck can you own so many different computers and not know how to set up networking.. let alone what a loopback is? Are you trolling us?

All of my other systems do this automatically!

No Im not trolling you, Im a military pilot who fancies hardware among many other things, and seeing that this isn't my profession, I'm learning here. (This is the point isn't it?)

That comment of yours was rather nasty and unnecessary, I have explained before that I'm no expert here and that I bought these machines simply to have a learning experience.

---

I initially set the system up as a standalone system, so therefore I'm now reinstalling solaris 10 with the machine setup for networking. (I know that there are probably better ways to do this, but this is what I'm doing.)

[uunix]

Is this the setup that I must use?

---

Ikrinus.. how the feck can you own so many different computers and not know how to set up networking.. let alone what a loopback is? Are you trolling us?

No Im not trolling you, Im a military pilot who fancies hardware among many other things, and seeing that this isn't my profession, I'm learning here. (This is the point isn't it?)

Can you land a Super Puma helicopter on the deck of a ship in bad weather, because I can!

All of my other systems do this automatically!

---

I initially set the system up as a standalone system, so therefore am now reinstalling solaris 10 with the machine setup for networking. (I know that there are probably better ways to do this, but this is what I'm doing.)

Oh chill the fsck out man..  And no, all your other machines do not use DHCP (automatic) as I assisted you with your flame/smoke setup and know the layout of your stone mappings file. So don't come it.

Each to their own job btw, I doubt you could carry out heart surgery either. I also doubt you could use the collection computers our bin men use each day. Hey ho though.

Now, I wasn't actually having a go at you, I was just taking the micky somewhat (my bad I know), but you will, I assure you get a much better experience if you learn the basic of networking, and none is rocket science I tell you.

DNS - Maybe your routers address, that way it can resolve names outside your network - like bbc.co.uk. (resolv.conf is a common file).
Gateway - First point of call for anything outside your network. static-route.options[off top of my head] on sgi. Traffic destined for the outside world goes to this and gets passed on.
/etc/host - good file for mapping out the other computers so you can reference them by name. A central DNS is better though as it allows you to amend addresses at a single point but is reliant on it being available (turned on).

Having a good internal network setup really helps you share files etc and carry out all sorts of tasks. You enjoy the ability to remote administer machines and even run them headless.

Learn the basics, and it will save you time installing and re-installing.

[Irinikus]

I've sorted it out an am now up and running:

[uunix]

I've sorted it out an am now up and running:

Good show chap.

[Irinikus]

Each to their own job btw, I doubt you could carry out heart surgery either. I also doubt you could use the collection computers our bin men use each day. Hey ho though.

I apologise for taking your comment the wrong, way and I especially apologise for my initial response (It was way out of line).

[uunix]

Each to their own job btw, I doubt you could carry out heart surgery either. I also doubt you could use the collection computers our bin men use each day. Hey ho though.

I apologise for taking your comment the wrong, way and I especially apologise for my initial response (It was way out of line).

It's fine chap, I can see how it was read as it was.

[Irinikus]

Having a good internal network setup really helps you share files etc and carry out all sorts of tasks. You enjoy the ability to remote administer machines and even run them headless.

Learn the basics, and it will save you time installing and re-installing.

At some point, I agree that it will be very useful for me to setup and manage a network connecting all of my machines.

Besides the internet connections for the Tezro, Mac and now the V880z, the only "network" that I do currently have a NFS setup between my Tezro and my Mac, allowing file sharing between the two machines.

I found this now, it would have been useful to know this before I reinstalled Solaris:

https://docs.oracle.com/cd/E19455-01/806...index.html

[uunix]

Having a good internal network setup really helps you share files etc and carry out all sorts of tasks. You enjoy the ability to remote administer machines and even run them headless.

Learn the basics, and it will save you time installing and re-installing.

At some point, I agree that it will be very useful for me to setup and manage a network connecting all of my machines.

Besides the internet connections for the Tezro, Mac and now the V880z, the only "network" that I do currently have a NFS setup between my Tezro and my Mac, allowing file sharing between the two machines.

I found this now, it would have been useful to know this before I reinstalled Solaris:

https://docs.oracle.com/cd/E19455-01/806...index.html

Just some advice.

You should only resort to DHCP in a network if the DHCP server notifies the DNS server of any changes of address or if you have host files set up on each client and each client has a DHCP reservation (meaning it never changes - this negates the need to change the host files on UNIX machines).

As an example, the nfs setup you have relies on IP addresses? Unless you have a host entry. This host entry will fail if the DHCP releases a different address to the NFS host. Again though it will still fail if the DHCP gives the nfs host a different address and the nfs client is set to mount an IP address. With me? the nfs server (corner shop) moves house and the nfs client (person) cannot go get it's groceries ! The Shop has moved. 

A lot of routers will fail on this, not all but most I would say. 

So in my setup, I do not use DHCP for anything other than Windows, Linux and Apple machines. The DHCP Server and the DNS server is the same (but can be different). Once a DHCP address is released it notifies the DNS service, which then updates it records. So any client of the DNS knows where to go. The DNS server also has forwarders, meaning if it doesn't know the answer it then asks the routers (the only reason it doesn't know is because it outside the network aka bbc.co.uk). If the routers doesn't know, it then asks whatever DNS it has been supplied with and so forth.

IRIX though is fine with certain things, but the naming concept is like many UNIX systems and fails. My DHCP also supplies many others things which do not concern the UNIX machines. Hence UNIX machines are static.

So I have a DHCP range for some machines, and others have static addresses and each of the static machines have their own identical hosts file.

Now this is not the best setup, we have many things including NIS, which is similar but different. So I will one day get round to something a bit better, but for 6 or 7 machines I'm ok with hosts and remembering myself what each address is.

That's it simply. There is more, but I need a new Gin & Tonic.

[commodorejohn]

Awesome to see that this beast is finally, officially up and running

[Irinikus]

Just some advice.

You should only resort to DHCP in a network if the DHCP server notifies the DNS server of any changes of address or if you have host files set up on each client and each client has a DHCP reservation (meaning it never changes - this negates the need to change the host files on UNIX machines).

As an example, the nfs setup you have relies on IP addresses? Unless you have a host entry. This host entry will fail if the DHCP releases a different address to the NFS host. Again though it will still fail if the DHCP gives the nfs host a different address and the nfs client is set to mount an IP address. With me? the nfs server (corner shop) moves house and the nfs client (person) cannot go get it's groceries ! The Shop has moved. 

A lot of routers will fail on this, not all but most I would say. 

So in my setup, I do not use DHCP for anything other than Windows, Linux and Apple machines. The DHCP Server and the DNS server is the same (but can be different). Once a DHCP address is released it notifies the DNS service, which then updates it records. So any client of the DNS knows where to go. The DNS server also has forwarders, meaning if it doesn't know the answer it then asks the routers (the only reason it doesn't know is because it outside the network aka bbc.co.uk). If the routers doesn't know, it then asks whatever DNS it has been supplied with and so forth.

IRIX though is fine with certain things, but the naming concept is like many UNIX systems and fails. My DHCP also supplies many others things which do not concern the UNIX machines. Hence UNIX machines are static.

So I have a DHCP range for some machines, and others have static addresses and each of the static machines have their own identical hosts file.

Now this is not the best setup, we have many things including NIS, which is similar but different. So I will one day get round to something a bit better, but for 6 or 7 machines I'm ok with hosts and remembering myself what each address is.

That's it simply. There is more, but I need a new Gin & Tonic.

Thanks very much for the advice!

Awesome to see that this beast is finally, officially up and running

I have to admit that it's taken quite a while!