I'm trying to create an unattended windows 7 setup DVD. I'm using WSIM to make the XML. I have the felowing issues:
Here's the script: http://pastebin.com/vbP556hZ
The PC is fairly simple: one ssd, one dvdr
Thank you!
I have a main router (10.20.0.1 (lan), 10.20.201.1 (vpn server)) connected to 5 other GW via VPN. Every gateway can ping every other one, and the PC behind them. One of my router, 10.20.6.1 (lan), 10.20.201.5 (vpn), has access to another network (10.10.10.x) and I want to give all my network access to it.
On the main router I added a route:
10.10.0.0 netmask 255.255.0.0 gw 10.20.201.5
when I run a traceroute, I don't even have a first hop. If I remove the route, the first hop is internet (which is the default). I can ping 10.20.201.5 and everything behind it. On the remote router, I don't see any icmp packet from 10.20.0.1 while pinging a host on the 10.10.x.x network. THe remote router can ping the 10.10.x.x network and access it whitout issues.
I'm trying to setup pervasive client to access a windows server.
/etc/odbcinst.ini
[Pervasive] Driver=/usr/local/psql/lib/libodbcci.so Driver64=/usr/local/psql/lib64/libodbcci.so
/etc/odbc.ini
[ODBC Data Sources] DALCON = Pervasive ODBC
[DALCON] Description=Maestro's DALCON database DBQ=DALCON Driver=Pervasive Servername=DALCON3 Username=username Password=password
Error:
isql -v dalcon
[01000][unixODBC][Driver Manager]Can't open lib '/usr/local/psql/lib64/libodbcci.so' : file not found [ISQL]ERROR: Could not SQLConnect
root@dalcon-www:/usr/local/psql/etc# ls -l /usr/local/psql/lib64/libodbcci.so lrwxrwxrwx 1 psql pvsw 15 sep 13 08:47 /usr/local/psql/lib64/libodbcci.so -> libodbcci.so.11 root@dalcon-www:/usr/local/psql/etc# ls -l /usr/local/psql/lib64/libodbcci.so.11 lrwxrwxrwx 1 psql pvsw 26 sep 13 08:10 /usr/local/psql/lib64/libodbcci.so.11 -> libodbcci.so.11.30.051.000 root@dalcon-www:/usr/local/psql/etc# ls -l /usr/local/psql/lib64/libodbcci.so.11.30.051.000 -rwxrwxrwx 1 psql pvsw 662429 jan 18 2013 /usr/local/psql/lib64/libodbcci.so.11.30.051.000
Any idea why? I'm running on the root user.
P.S. The formating is bad, dunno why :S
I have a TP-Link WR1043ND with 1 wan and 1 lan cables attached. The lan cable currently have 2 ips of two different network, using an alias. The two networks share the same switch.
I'd like the router to forward between the two. Currently the routers sends ICMP redirect to the first network telling the clients to go to the second network directly, which is impossible.
Could I create a second virtual nic in the same vlan and assign it the IP on the second network?
Thanks!
I have 4 nodes to the internet:
Internet <--> Node A <--> Node B <--> Node C <--> Node D
Node A: main gateway, manage internet
Node B: gateway/tunnel to node C
Node C: gateway/tunnel to node B
Node D: FreeNAS server
Between B and C is a semi-private network. Default route on Node C is via the tunnel.
Can ping:
A: Internet, A, B, C, D
B: Internet, A, B, C, D
C: B, C, D
D: Internet, A, B, C, D
I really don't get it...
edit
traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 10.20.1.1 (10.20.1.1) 0.959 ms 0.753 ms 0.535 ms
2 10.20.200.1 (10.20.200.1) 4.993 ms 5.010 ms 4.804 ms
3 10.20.2.1 (10.20.2.1) 5.152 ms 5.218 ms 5.046 ms
4 modemcable233.11-37-24.static.videotron.ca (24.37.11.233) 5.638 ms 5.684 ms 5.645 ms
Traceroute from D to internet:
1: Node C
2: Node B (tunnel ip)
3: Node A
4: Internet
The whole setup works standalone, ex: openvpn --config /etc/openvpn/openvpn.conf, remote can ping server, and server can ping the remote
When I start the server with --daemon, the remote client can ping the server and the network behind the server, but the server cannot ping the remote.
Server: 10.20.0.1
Remote: 10.20.3.1
Intermediate network: 10.20.201.0/24
server's openvpn.conf:
mode server
tls-server
### network options
port 1194
proto udp
dev tun
### Certificate and key files
ca /etc/easy-rsa/keys/ca.crt
cert /etc/easy-rsa/keys/server.crt
key /etc/easy-rsa/keys/server.key
dh /etc/easy-rsa/keys/dh1024.pem
server 10.20.201.0 255.255.255.0
#push "redirect-gateway def1"
push "route 10.20.0.0 255.255.255.0"
push "dhcp-option DNS 10.20.0.12" # Change this to your router's LAN IP Address
client-to-client
client-config-dir ccd
route 10.20.3.0 255.255.255.0
ifconfig-pool-persist ipp.txt
### (optional) compression (Can be slow)
#comp-lzo
persist-key
persist-tun
verb 3
keepalive 10 120
The host 10.20.3.1 is learned after the client connects and shows in logs, when not running as daemon.
Thanks!
[edit]
Both hosts are on OpenWRT on a TPLink WR-1043ND. Remote host is connected via internet.
[edit]
The "daemon" doesn't learn the route to 10.20.3.x, as it does when running it directly from the commandline
[edit]
OpenVPN 2.1.4 mips-openwrt-linux [SSL] [LZO2] [EPOLL] built on Nov 14 2011
Originally developed by James Yonan
Copyright (C) 2002-2010 OpenVPN Technologies, Inc.
[edit]
I built a vm with this version:
Mon Jul 16 16:49:58 2012 OpenVPN 2.2.1 x86_64-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2 (2.2RC2)] built on Mar 30 2012
same issue :S
I have an ESXi 5 host (free) and vSphere Client. I would like to update to u1 but I cannot find the way to do it. Updates are ZIP files with modules in it; no installer. vSphere client doesn't have an update module.
Thanks!
[edit]
/vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update # esxcli software vib install -d /vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update/update-from-esxi5.0-5.0_update01.zip
[InstallationError]
[Errno 32] Broken pipe
vibs = VMware_locker_tools-light_5.0.0-1.11.623860
Please refer to the log file for more details.
/vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update # esxcli software vib install -d /vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update/update-from-esxi5.0-5.0_update01.zip
[InstallationError]
[Errno 32] Broken pipe
vibs = VMware_locker_tools-light_5.0.0-1.11.623860
Please refer to the log file for more details.
/vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update # esxcli software vib install -d /vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update/ESXi500-201205001.zip
[InstallationError]
[Errno 32] Broken pipe
vibs = VMware_locker_tools-light_5.0.0-1.12.653509
Please refer to the log file for more details.
[edit]
"install" -> "update"
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
/vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update # esxcli software vib update -d /vmfs/volumes/4f255b5c-6acfd348-d53c-00e04c68ee7a/esxi_update/update-from-esxi5.0-5.0_update01.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.500.1.11.623860, VMware_bootbank_esx-base_5.0.0-1.11.623860, VMware_bootbank_misc-drivers_5.0.0-1.11.623860, VMware_bootbank_net-e1000e_1.1.2-3vmw.500.1.11.623860, VMware_bootbank_net-nx-nic_4.0.557-3vmw.500.1.11.623860, VMware_bootbank_sata-ahci_3.0-6vmw.500.1.11.623860, VMware_bootbank_sata-ata-piix_2.12-4vmw.500.1.11.623860, VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.500.1.11.623860, VMware_bootbank_scsi-megaraid-sas_5.34-1vmw.500.1.11.623860, VMware_bootbank_scsi-mpt2sas_06.00.00.00-6vmw.500.1.11.623860
VIBs Removed: VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.500.0.0.469512, VMware_bootbank_esx-base_5.0.0-0.7.515841, VMware_bootbank_misc-drivers_5.0.0-0.7.515841, VMware_bootbank_net-e1000e_1.1.2-3vmw.500.0.7.515841, VMware_bootbank_net-nx-nic_4.0.557-3vmw.500.0.0.469512, VMware_bootbank_sata-ahci_3.0-6vmw.500.0.0.469512, VMware_bootbank_sata-ata-piix_2.12-4vmw.500.0.0.469512, VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-sas_4.32-1vmw.500.0.0.469512, VMware_bootbank_scsi-mpt2sas_06.00.00.00-5vmw.500.0.0.469512
VIBs Skipped: VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-atiixp_0.4.6-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-via_0.3.3-2vmw.500.0.0.469512, VMware_bootbank_block-cciss_3.6.14-10vmw.500.0.0.469512, VMware_bootbank_esx-tboot_5.0.0-0.0.469512, VMware_bootbank_ima-qla4xxx_2.01.07-1vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.500.0.0.469512, VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512, VMware_bootbank_net-be2net_4.0.88.0-1vmw.500.0.7.515841, VMware_bootbank_net-bnx2_2.0.15g.v50.11-5vmw.500.0.0.469512, VMware_bootbank_net-bnx2x_1.61.15.v50.1-1vmw.500.0.0.469512, VMware_bootbank_net-cnic_1.10.2j.v50.7-2vmw.500.0.0.469512, VMware_bootbank_net-e1000_8.0.3.1-2vmw.500.0.7.515841, VMware_bootbank_net-enic_1.4.2.15a-1vmw.500.0.0.469512, VMware_bootbank_net-forcedeth_0.61-2vmw.500.0.0.469512, VMware_bootbank_net-igb_2.1.11.1-3vmw.500.0.0.469512, VMware_bootbank_net-ixgbe_2.0.84.8.2-10vmw.500.0.0.469512, VMware_bootbank_net-r8168_8.013.00-3vmw.500.0.0.469512, VMware_bootbank_net-r8169_6.011.00-2vmw.500.0.0.469512, VMware_bootbank_net-s2io_2.1.4.13427-3vmw.500.0.0.469512, VMware_bootbank_net-sky2_1.20-2vmw.500.0.0.469512, VMware_bootbank_net-tg3_3.110h.v50.4-4vmw.500.0.0.469512, VMware_bootbank_ohci-usb-ohci_1.0-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-nv_3.5-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-promise_2.12-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-sil_2.3-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-svw_2.3-3vmw.500.0.0.469512, VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.500.0.0.469512, VMware_bootbank_scsi-aic79xx_3.1-5vmw.500.0.0.469512, VMware_bootbank_scsi-bnx2i_1.9.1d.v50.1-3vmw.500.0.0.469512, VMware_bootbank_scsi-fnic_1.5.0.3-1vmw.500.0.0.469512, VMware_bootbank_scsi-hpsa_5.0.0-17vmw.500.0.0.469512, VMware_bootbank_scsi-ips_7.12.05-4vmw.500.0.0.469512, VMware_bootbank_scsi-lpfc820_8.2.2.1-18vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid2_2.00.4-9vmw.500.0.0.469512, VMware_bootbank_scsi-mptsas_4.23.01.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-mptspi_4.23.01.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512, VMware_bootbank_scsi-qla4xxx_5.01.03.2-3vmw.500.0.0.469512, VMware_bootbank_scsi-rste_2.0.2.0088-1vmw.500.1.11.623860, VMware_bootbank_uhci-usb-uhci_1.0-3vmw.500.0.0.469512, VMware_locker_tools-light_5.0.0-1.11.623860
I have two private networks (A, B) that connects via another company's private network (C). Network A has internet access. I want to make a tunnel between B and A that goes through C. Then network B will use A as default route for internet access.
Network A: 10.20.0.0/24, on C: 10.10.15.3
Network B: 10.20.1.0/24, on C: 192.168.25.3
10.10.15.3 can access 192.168.25.3 and vice versa
Network A tunnel script:
ip tunnel add tunnel0 mode gre local 10.10.15.3 remote 192.168.25.3 ttl 64
ip link set tunnel0 up
ip addr add 10.20.200.1/30 peer 10.20.200.2/30 dev tunnel0
ip route add 10.20.1.0/24 via 10.20.200.2
Network B tunnel:
ip tunnel add tunnel0 mode gre local 192.168.25.3 remote 10.10.15.3 ttl 64
ip link set tunnel0 up
ip addr add 10.20.200.2/30 peer 10.20.200.1/30 dev tunnel0
ip route add 10.20.0.0/24 via 10.20.200.1
ip r d default && ip r a default via 10.20.200.1
From GW on network B:
traceroute to 10.20.0.1 (10.20.0.1), 30 hops max, 38 byte packets
1 10.20.0.1 (10.20.0.1) 4.685 ms 4.505 ms 4.478 mstraceroute to 10.20.0.14 (10.20.0.14), 30 hops max, 38 byte packets
1 10.20.200.1 (10.20.200.1) 4.643 ms 4.387 ms 4.555 ms
2 10.20.200.1 (10.20.200.1) 4.423 ms 4.473 ms 4.437 mstraceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.20.200.1 (10.20.200.1) 4.595 ms 4.461 ms 4.628 ms
2 10.20.200.1 (10.20.200.1) 4.476 ms 4.521 ms 4.536 ms
something's not right.... but why?
DALCON2 (Windows 2008R2, DC, NPS)DALCON3 (Windows 2008R2, DC)DALCON-WWW (Ubuntu server)From DALCON-WWW, using adLDAP with TLS to connect to a domain controller LDAP service
If I connect to DALCON2, I get: Server returned an error: [2] ldap_start_tls(): Unable to start TLS: Server is unavailable. If I connect do DALCON3, it works.
DALCON2 has a Network Policy Service (NPS) enabled to manage VPN connections. Nothing is specificly "denied" in the policies. The LDAP port is open and will respond if not using TLS, but it's unusable (stronger authentification required). I didn't find anything related to LDAP or TLS in NPS.
What might be wrong with DALCON2 that I can't connect to it?
edit
I got more debug infos:
Warning: ldap_start_tls(): Unable to start TLS: Server is unavailable in /var/www/dalcon-inc.com/dev/test/test_ldap.php on line 12
Error Binding to LDAP: 00002028: LdapErr: DSID-0C0901FC, comment: The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection, data 0, v1db1
edit
in the Group Policy Management Editor: Computer Configuration, Policies, Windows Settings, Security Settings, and Local Policies, and then click Security Options. In the right pane, double-click the Domain Controller: LDAP server signing requirements policy.
while setting it to "none",
DALCON2:
Plain: OK
SSL: Error Binding to LDAP: Error in the push function. / A TLS packet with unexpected length was received.
TLS: Warning: ldap_start_tls(): Unable to start TLS: Server is unavailable
DALCON3
Plain: OK
SSL: OK
TLS: OK
** edit**
DALCON3 is an exchange 2010 server with a valid SSL certificate