lost my default gateway
Mac McTeague
running in a virtual machine. I had not really used solaris since 7.
So I needed to brush up on some basic skills. Anyway originally
solaris was set DHCP. So I manually changed the host name and made
the IIP static. I assumed, probably wrongly, that the default router
that was in use while it was DHCP would be the same for a static
configuration. So I put that into /etc/defaultrouter
So everything seemed to go fine. I have a static IP. The name change
went fine. But look at this
bash-3.00# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use
Interface
-------------------- -------------------- ----- ----- ----------
---------
192.168.117.0 192.168.117.50 U 1 77
e1000g0
224.0.0.0 192.168.117.50 U 1 0
e1000g0
127.0.0.1 127.0.0.1 UH 4 120 lo0
There is no gateway! When DHCP was providing the address the gateway
was 192.168.117.2 I tried pinging .1 .2.3 all on the 117 but I am
not getting anything. I could reset up DHCP and start again from
scratch. But I would rather try to find away to fix this. The
trouble is that I am not sure how to figure out where VMware thinks
the gateway is. Well other than writing some script to ping
everything on 192.168.. and wait for a response. I must be missing
something Any suggestions would be welcome. Thanks for any help
Mac McTeague
solaris. I am fairly certain that my solaris changes were correct. I
think that there is something about how vmware presents the virtual
network that I am misunderstanding. There should be someway in vmware,
not in the os, to see what ip it is presenting as the default
gateway. To be honest I could just rebuild the server. It only for
my personal study. But what if was a production server. I have to
think about what I would do if for some reason the setting vmware
became corrupted or had some other problem. Googling this problem has
only shown me unix commands I have known for 10 years, or the
suggestion to ask the system administrator. Not much help when that
is me.
So is there someway to determine what vmware thinks the gateway is.
Thanks
Hans-Peter Diettrich
> So is there someway to determine what vmware thinks the gateway is.
Can't you simply use NAT for the virtual network?
DoDi
Mac McTeague
I thought NAT was for when you want to use DHCP. However I think I
have figured out the issue. Although I admit that I am not 100% sure.
I am setting up a private network of virtual machines. A place to
setup clusters and hack about to my hearts content. Being as it is
private. That is all on the same network and will not have internet
access, or access to any of my other boxes, it probably does not need
a gateway. All I probably have to do is keep the host files updated
and there should not be a problem. I might setup a dns zone on the
private network, or nis. I haven't done either for a while. In fact I
am not even sure if people still use NIS. Anyway that is my current
answer. Private networks don't need gateways because they are
private. That is why netstat does not show any. If this is completely
wrong, I would appreciate it is some kind knowledgeable person could
set me straight. Thanks again