[ 
https://issues.apache.org/jira/browse/KARAF-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

KG Anand updated KARAF-3512:
----------------------------
    Issue Type: Bug  (was: Question)

> Modify the sshHost(org.apache.karaf.shell.ssh) is not working in Karaf 2.3.2
> ----------------------------------------------------------------------------
>
>                 Key: KARAF-3512
>                 URL: https://issues.apache.org/jira/browse/KARAF-3512
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: KG Anand
>
> Karaf version 2.3.2. 
> I want to change the sshHost parameter from 0.0.0.0 to xxx.xxx.xxx.xxx (i.e. 
> Server IP Address). 
> Editing the file,then restart the karaf instance. 
> config:edit org.apache.karaf.shell
> config:propset sshHost 192.168.1.1
> config:update 
> After the Restart, Instance is not coming up.
> Revert the value to "0.0.0.0"  in config file (org.apache.karaf.shell.cfg), 
> then its working fine.
> Now my question is, we can edit the config file and the set the IP address 
> will work in Karaf 2.3.3 Version or not ?
> I found some fixes in your website, Its little related to My question.
> https://issues.apache.org/jira/browse/KARAF-3130
> Existing:
> tcp        0      0 0.0.0.0:8101               0.0.0.0:*                   
> LISTEN
> Expectation : i want to the change the sshHost from "0.0.0.0" to "192.168.1.1"
> tcp        0      0 192.168.1.1:8101               0.0.0.0:*                  
>  LISTEN
> I want to bind my karaf instance to the specific IP Address.
> I have 4 ethernet interfaces, i want to set the karaf instance has to use the 
> particular ethernet.
> Is there any possiblilty to make it possible in Karaf 2.3.2 version itself.
> One more Question is, this sshHost parameter is already available in config 
> file(org.apache.karaf.shell.cfg), then why editing this file with the IP 
> address and restarting the Karaf instance is Not working ?
> Thanks in Advance :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to