Since change the configuration of Net of the server?

[unzizu de Goñi]

I have a server Vax VMS in the net with the following configuration of Net
IP - 192.168.1.100
Network_MASK 255.255.255.0
Broadcast_mask 192.168.1.255

In the net there are other computers with the same IP's range 192.168.1.xxx that execute across KEA an application in the server.

Now I need that another group of computers with IP's ranhe 192.6.21.xxx access across KEA to this server.

I have test to changing the subnet of the servant to 255.0.0.0 of a following way
Ucx set interface WE0/network_mask = 255.0.0.0
But I do not achieve that the computers access to the server. Also I have seen that if I restart the server the modification itdisappears.

Can someone indicate me like do this change?
Thank you

[Ian Miller.]

Try reconfiguring the address
@SYS$STARTUP:TCPIP$CONFIG
(or UCX$CONFIG if UCX V4.x)

option 1 core environment
option 4 interfaces

and follow the prompts. Restart TCP or reboot afterward

[Bojan Nemec]

Unzizu,

Try with the ucx configuration utility:

$ @SYS$MANAGER:UCX$CONFIG

Select the "4 - interfaces" option and reconfigure the interface.

You can access the VMS also if you have a router which will do the routing. You have to setup the routes using UCX SET ROUTE /PERMANENT. See UCX HELP SET ROUTE.

Bojan

[Michael Yu_3 · Accepted solution]

Hi Unzizu,

You can try to use multiple addresses on the same interface.

Obtain an address in the 192.6.21.0/24 subnet, say 192.6.21.100/24. Then

$ ifconfig we0 192.6.21.100/24

Make sure both the oringal address 192.168.1.100 and the new address 192.6.21.100 are configured on we0 with the command.

$ ifconfig -a

Then check the routing table.

$ netstat -rn

The routing table should have a route for 192.168.1/24 and a route for 192.6.21/24 both going out we0.

Thanks and regards.

Michael

[Antoniov.]

Nevertheless multiple address on same interface solve your problem I think change of network mask on server is necessary but insufficient condition to work. You must change network mask also on client of 192.6.21.xxx to work fine.
The reason is simple:
client in 192.6.21.xxx network with netmask 255.255.255.0 send socket to 192.168.1.100 at its gateway, not directly to host, even fi both hosts are on same physical network.

Antonio Vigliotti