R
ray65536
Guest
I have iSCSI-target (software-based, server with Debian 6.0), which have two IP addresses - one is "real", for example "50.50.50.1", and second - private, for example "192.168.0.1".
My PVE-cluster running on private IP's, 192.168.0.10-192.168.0.20, for example.
When I want to connect iSCSI to Proxmox via GUI - it's scanning portal "192.168.0.1", detects my target. When I pressing "save" - it's hang for a while, and displays timeout-related problem.
In syslog I see, that it's tries to connect to another IP of target (50.50.50.1) instead of IP 192.168.0.1, entered by me.
WHY???
I have checked via tcpdump - it's really connects to another IP
Sorry, didn't found solution on the forum..
P.S. Sorry for bad English.
My PVE-cluster running on private IP's, 192.168.0.10-192.168.0.20, for example.
When I want to connect iSCSI to Proxmox via GUI - it's scanning portal "192.168.0.1", detects my target. When I pressing "save" - it's hang for a while, and displays timeout-related problem.
In syslog I see, that it's tries to connect to another IP of target (50.50.50.1) instead of IP 192.168.0.1, entered by me.
WHY???
I have checked via tcpdump - it's really connects to another IP
Sorry, didn't found solution on the forum..
Code:
# pveversion --verbose
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.18-5-pve
proxmox-ve-2.6.18: 1.8-14
pve-kernel-2.6.18-5-pve: 2.6.18-14
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-14P.S. Sorry for bad English.
