Configure Network Host-Only DHCP Server segments with Parallels 11 on Mac - parallels

After upgrading from version Parallels 10 to Parallels 11, the company has removed the “Network Tab” from the preferences pane and changed my host-only network DHCP server segment to 10.32.x.x which broke all my exiting static host-only IP assignments. According to this post, configuring DHCP is now a “Pro” feature meaning we are expected to either pay more or update all my existing static IP assignments (to 20+ vms).
How can you update the DHCP server IP segment to match the pre-upgrade state?

As a manual workaround, you can modify the network.desktop.xml file which Parallels uses to assign network adapter segments. Credit for this workaround goes to Kevin01.
Shutdown/quit Parallels
Open the XML file with elevated permissions, in my case I have sublime configured in terminal, so I ran:
sudo sublime /Library/Preferences/Parallels/network.desktop.xml
Modify the adapter settings located under "Host-Only". In this example I’ve set my network segment to 10.211.55.x
<VirtualNetwork id="1" dyn_lists="VZVirtualNetwork 0">
<Uuid>{your-guid-id-here}</Uuid>
<NetworkID>Host-Only</NetworkID>
<Description>Host Only Networking</Description>
<Enabled>1</Enabled>
<NetworkType>1</NetworkType>
<BoundCardMac></BoundCardMac>
<VLANTag>65535</VLANTag>
<HostOnlyNetwork dyn_lists="">
<HostIPAddress>10.211.55.2</HostIPAddress>
<DhcpIPAddress>10.211.55.1</DhcpIPAddress>
<IPNetMask>255.255.255.0</IPNetMask>
<HostIP6Address>FDB2:2C26:F4E4:1::1</HostIP6Address>
<DhcpIP6Address>FDB2:2C26:F4E4:1::</DhcpIP6Address>
<IP6NetMask>FFFF:FFFF:FFFF:FFFF::</IP6NetMask>
<DNSUseEtcHosts>1</DNSUseEtcHosts>
<RegVmNameInEtcHosts>1</RegVmNameInEtcHosts>
<EnableDNS>1</EnableDNS>
<ParallelsAdapter dyn_lists="">
<Enabled>1</Enabled>
<Name>Parallels Host-Only #1</Name>
<PrlAdapterIndex>1</PrlAdapterIndex>
<HiddenAdapter>1</HiddenAdapter>
</ParallelsAdapter>
<DHCPServer dyn_lists="">
<Enabled>1</Enabled>
<IPScopeStart>10.211.55.1</IPScopeStart>
<IPScopeEnd>10.211.55.254</IPScopeEnd>
<IPReservations dyn_lists="IPReservation 0"/>
</DHCPServer>
<DHCPv6Server dyn_lists="">
<Enabled>1</Enabled>
<IPScopeStart>FDB2:2C26:F4E4:1::</IPScopeStart>
<IPScopeEnd>FDB2:2C26:F4E4:1:FFFF:FFFF:FFFF:FFFF</IPScopeEnd>
<IPReservations dyn_lists="IPReservation 0"/>
</DHCPv6Server>
<NATServer dyn_lists="">
<Enabled>0</Enabled>
<PortForwarding dyn_lists="">
<TCP dyn_lists="ForwardEntry 0"/>
<UDP dyn_lists="ForwardEntry 0"/>
</PortForwarding>
<IdleConnectionTimeoutSecs>7440</IdleConnectionTimeoutSecs>
<UseIPFilter>0</UseIPFilter>
<ProvideIPv6Route>-1</ProvideIPv6Route>
<NatDNSFilterIPv6Replies>-1</NatDNSFilterIPv6Replies>
<UseInterface></UseInterface>
</NATServer>
</HostOnlyNetwork>
</VirtualNetwork>

Related

Connect Retroflag GPi (Raspberry Pi Zero W) to WPA2 Enterprise

I just got my retroflag gpi case working and set up. I have one small problem though. I can't connect my Pi to my WPA2-Enterprise network. I've tried a bunch of settings in wpa_supplicant.conf but can't get it to work.
Pi Model or other hardware: Raspberry Pi Zero W & Retroflag GPi Case
Power Supply used: Retroflag GPi's inbuilt.
RetroPie Version Used: 4.6.1
Built From: https://github.com/RetroPie/RetroPie-Setup/releases/download/4.6/retropie-buster-4.6-rpi1_zero.img.gz
USB Devices connected: Retroflag GPi
Controller used: Retroflag GPi
Error messages received:
Can't see any error messages. Don't know where they appear. It just says IP-address Unkown in show ip.
Guide used: Several on Google. This one among others: https://gist.github.com/elec3647/1e223c02ef2a9a3f836db7984011b53b.
This one for documentation: https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf
File: /etc/wpa_supplicant/wpa_supplicant.conf
Attachment of config files: (wpa_supplicant.conf)
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=SE
ap_scan=1
network={
ssid="Wifi-Name"
scan_ssid=1
identity="myusername"
password="mypassword"
key_mgmt=WPA-EAP
eap=TTLS
phase1="peapver=0 peaplabel=1"
phase2="autheap=MSCHAPV2"
}
I actually solved it just now.
For anyone wondering I managed to connect to the network on another machine (Ubuntu) and used Network Manager. I then checked the log (according to this link) with the command:
journalctl -u NetworkManager
This gave me this config for wpa_supplicant.conf:
country=SE
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
ap_scan=1
network={
ssid="Wifi-Name"
scan_ssid=1
bgscan="simple:30:-65:300"
key_mgmt=WPA-EAP WPA-EAP-SHA256
password="password"
eap=PEAP
fragment_size=1266
phase2="auth=MSCHAPV2"
identity="username"
proactive_key_caching=1
}
This might not work for everyone else since the configs are always different for every network. So be sure to do the same steps as I did if you can't get it to work.
So glad I finally got this, haha.

Failed to infer CIDR network for mon ip

I follow the instructions to bootstrap a new Ceph (I'm new to Ceph) cluster.
I got the following error:
sudo cephadm bootstrap --mon-ip <mon-ip>
INFO:cephadm:Verifying podman|docker is present...
INFO:cephadm:Verifying lvm2 is present...
INFO:cephadm:Verifying time synchronization is in place...
INFO:cephadm:Unit systemd-timesyncd.service is enabled and running
INFO:cephadm:Repeating the final host check...
INFO:cephadm:podman|docker (/usr/bin/podman) is present
INFO:cephadm:systemctl is present
INFO:cephadm:lvcreate is present
INFO:cephadm:Unit systemd-timesyncd.service is enabled and running
INFO:cephadm:Host looks OK
INFO:root:Cluster fsid: e08484be-72c1-11ea-a13e-0050563f093a
INFO:cephadm:Verifying IP *<mon-ip>* port 3300 ...
INFO:cephadm:Verifying IP *<mon-ip>* port 6789 ...
ERROR: Failed to infer CIDR network for mon ip *<mon-ip>*; pass --skip-mon-network to configure it later
What does it mean ? How to fix it ?
cephadm is still fairly new. I've tracked a few days ago in:
https://tracker.ceph.com/issues/44828
Please run
ceph config set mon public_network <mon_network>
after bootstrap finished.
Is this the exact command you ran?
sudo cephadm bootstrap --mon-ip *<mon-ip>*
If so you actually need to replace *<mon-ip>* with the actual IP address that you want the monitor daemon to listen on.
For future reference, on that page, any command you see that has a variable surrounded by asterisks is something you would need to replace with an address/host/hostname etc. that applies to your environment.

honeyd: ip-open: operation not permitted

I want to Use honeyd to setup a virtual host with the following specification:
• Operating System: Linux
• Ethernet MAC Address: 00:00:24:22:8c:14
• IP Address: 10.10.10.2
• Open Ports: 22
so I instlled honeyd on ubuntu 1204 vm; then changed etc/honeypot/honeyd.conf as below:
create default
set default default tcp action block
set default default udp action block
set default default icmp action block
create linux
set linux personality "Linux 2.4.20"
set linux default tcp action reset
add linux tcp port 22 open
set linux ethernet "00:00:24:22:8c:14"
bind 10.10.10.2 linux
and the file honeyd.conf in etc/default/ like below:
RUN="yes"
INTERFACE= "eth0"
NETWORK= 10.10.10.2
OPTIONS="--disable-webserver"
when i run the honeyd using command : 'honeyd start'
sometimes it shows this error:
honeyd: ip-open: operation not permitted
and other times it shows this one:
honeyd: interface_expandips: Invalid network range: start
what should i do?
Thanks
If you run honeyd without sudo you will receive the first error message. The second one occurs when running it with sudo.
Looks like you didn't specify a network range in the config file at /etc/default. 10.10.10.2 is an IP address. Not a range. You probably want something like:
NETWORK= 10.10.10.0/24
in your config file,
my error removed after i changed my vmware nat dhcp setting. it is in tab edit>virtual network editor.. > nat> dhcp setting.
the range must include the ip address i want to use.
:)

Wildfly 9 - mod_cluster on TCP

We are currently testing to move from Wildfly 8.2.0 to Wildfly 9.0.0.CR1 (or CR2 built from snapshot). The system is a cluster using mod_cluster and is running on VPS what in fact prevents it from using multicast.
On 8.2.0 we have been using the following configuration of the modcluster that works well:
<mod-cluster-config proxy-list="1.2.3.4:10001,1.2.3.5:10001" advertise="false" connector="ajp">
<dynamic-load-provider>
<load-metric type="cpu"/>
</dynamic-load-provider>
</mod-cluster-config>
Unfortunately, on 9.0.0 proxy-list was deprecated and the start of the server will finish with an error. There is a terrible lack of documentation, however after a couple of tries I have discovered that proxy-list was replaced with proxies that are a list of outbound-socket-bindings. Hence, the configuration looks like the following:
<mod-cluster-config proxies="mc-prox1 mc-prox2" advertise="false" connector="ajp">
<dynamic-load-provider>
<load-metric type="cpu"/>
</dynamic-load-provider>
</mod-cluster-config>
And the following should be added into the appropriate socket-binding-group (full-ha in my case):
<outbound-socket-binding name="mc-prox1">
<remote-destination host="1.2.3.4" port="10001"/>
</outbound-socket-binding>
<outbound-socket-binding name="mc-prox2">
<remote-destination host="1.2.3.5" port="10001"/>
</outbound-socket-binding>
So far so good. After this, the httpd cluster starts registering the nodes. However I am getting errors from load balancer. When I look into /mod_cluster-manager, I see a couple of Node REMOVED lines and there are also many many errors like:
ERROR [org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000042: Error MEM sending STATUS command to node1/1.2.3.4:10001, configuration will be reset: MEM: Can't read node
In the log of mod_cluster there are the equivalent warnings:
manager_handler STATUS error: MEM: Can't read node
As far as I understand, the problem is that although wildfly/modcluster is able to connect to httpd/mod_cluster, it does not work the other way. Unfortunately, even after an extensive effort I am stuck.
Could someone help with setting mod_cluster for Wildfly 9.0.0 without advertising? Thanks a lot.
I ran into the Node Removed issue to.
I managed to solve it by using the following as instance-id
<subsystem xmlns="urn:jboss:domain:undertow:2.0" instance-id="${jboss.server.name}">
I hope this will help someone else to ;)
There is no need for any unnecessary effort or uneasiness about static proxy configuration. Each WildFly distribution comes with xsd sheets that describe xml subsystem configuration. For instance, with WildFly 9x, it's:
WILDFLY_DIRECTORY/docs/schema/jboss-as-mod-cluster_2_0.xsd
It says:
<xs:attribute name="proxies" use="optional">
<xs:annotation>
<xs:documentation>List of proxies for mod_cluster to register with defined by outbound-socket-binding in socket-binding-group.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:list itemType="xs:string"/>
</xs:simpleType>
</xs:attribute>
The following setup works out of box
Download wildfly-9.0.0.CR1.zip or build with ./build.sh from sources
Let's assume you have 2 boxes, Apache HTTP Server with mod_cluster acting as a load balancing proxy and your WildFly server acting as a worker. Make sure botch servers can access each other on both MCMP enabled VirtualHost's address and port (Apache HTTP Server side) and on WildFly AJP and HTTP connector side. The common mistake is to binf WildFLy to localhost; it then reports its addess as localhost to the Apache HTTP Server residing on a dofferent box, which makes it impossible for it to contact WildFly server back. The communication is bidirectional.
This is my configuration diff from the default wildfly-9.0.0.CR1.zip.
328c328
< <mod-cluster-config advertise-socket="modcluster" connector="ajp" advertise="false" proxies="my-proxy-one">
---
> <mod-cluster-config advertise-socket="modcluster" connector="ajp">
384c384
< <subsystem xmlns="urn:jboss:domain:undertow:2.0" instance-id="worker-1">
---
> <subsystem xmlns="urn:jboss:domain:undertow:2.0">
435c435
< <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:102}">
---
> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
452,454d451
< <outbound-socket-binding name="my-proxy-one">
< <remote-destination host="10.10.2.4" port="6666"/>
< </outbound-socket-binding>
456c453
< </server>
---
> </server>
Changes explanation
proxies="my-proxy-one", outbound socket binding name; could be more of them here.
instance-id="worker-1", the name of the worker, a.k.a. JVMRoute.
offset -- you could ignore, it's just for my test setup. Offset does not apply to outbound socket bindings.
<outbound-socket-binding name="my-proxy-one"> - IP and port of the VirtualHost in Apache HTTP Server containing EnableMCPMReceive directive.
Conclusion
Generally, these MEM read / node error messages are related to network problems, e.g. WildFly can contact Apache, but Apache cannot contact WildFly back. Last but not least, it could happen that the Apache HTTP Server's configuration uses PersistSlots directive and some substantial enviroment conf change took place, e.g. switch from mpm_prefork to mpm_worker. In this case, MEM Read error messages are not realted to WildFly, but to the cached slotmem files in HTTPD/cache/mod_custer that need to be deleted.
I'm certain it's network in your case though.
After a couple of weeks I got back to the problem and found the solution. The problem was - of course - in configuration and had nothing in common with the particular version of Wildfly. Mode specifically:
There were three nodes in the domain and three servers in each node. All nodes were launched with the following property:
-Djboss.node.name=nodeX
...where nodeX is the name of a particular node. However, it meant that all three servers in the node get the same name, which is exactly what confused the load balancer.
As soon as I have removed this property, everything started to work.

Error with "Get Started" on Oracle Express 11g

this is my first post so I will try to be as descriptive as possible. Please let me know if there is anything missing:
So I am trying to install Oracle Express 11g, after I download the zip file "OracleXE112_Win32" - I unzip it, and open Disk 1 then setup. I go through the entire installation process without any problems. However when I go to open "Get Started" I come across the following error:
"Windows cannot find 'http:/.127.0.0.1:%HTTPPORT%/apex/f?p=4950'. Make sure you typed the name correctly, and then try again. -- After googling this, I was told to change %HTTPPORT% to 8080.
If I do this when I click on "Get Started" the following error shows up:
"Firefox can' establish a connection to the server at 127.0.0.1:8080."
I need this to work, so that I can sooner or later connect this to my eclipse, so that I can start doing my homework for my Java Programming class. Any help is greatly appreciated, thank you so much!
I have found one solution for this problem. In order to explain my solution, I have used some aliases referring to my real parameters. These are:
[ME] = my user name
[MYHOST] = my current workstation hostname (netbios name as well)
[MYHOST.mycompany.com] = my worksation's fully qualified domain name
At the beginning I had the same situation as mentioned above: I was unable to connect to the apex service even after successful installation.
First I have used the tnsping oracle utility:
C:\Users\ME>tnsping MYHOST
This was the answer:
TNS Ping Utility for 32-bit Windows: Version 11.2.0.2.0 - Production
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
C:\oraclexe\app\oracle\product\11.2.0\server\network\admin\sqlnet.ora
Used HOSTNAME adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=
(PROTOCOL=TCP)(HOST=fe80::5d34:78a:5862:64%20)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=fe80::c27:54a4:1600:86a4%26)(PORT=1521))(ADDRESS=
(PROTOCOL=TCP)(HOST=fe80::38ab:cdb4:dd77:7ed9%12)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
(HOST=10.9.32.208)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.1)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.106)(PORT=1521)))
TNS-12541: TNS:no listener
You see above a lot of currently active different IP addresses. Only the most important 127.0.0.1 is missing. I work on notebook so the network is "almost always" changing (WLAN, 3G, HSDPA, Ethernet etc.) only the localhost is fixed. And that was the real case of the trouble. (When I was working at the office environment connected to the office network it was also working.)
When I was in this situation I also started to use the lsnrctl oracle utility.
I have seen the following:
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.2.0 - Production
Default Service XE
Listener Parameter File /oraclexe/app/oracle/product/11.2.0/server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\diag\tnslsnr\MYHOST\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
You can see that the service for the apex at 8080 port is missing !!!
I have tried also the normal ping which worked perfectly:
C:\Users\ME>ping MYHOST.mycompany.com
The result was:
MYHOST.mycompany.com [fe80::c27:54a4:1600:86a4%26] ping
response fe80::c27:54a4:1600:86a4%26: time<10 ms
...
You can realize the IPv6 address also exists in my tnsping trial as well.
So I have decided to define MYHOST in my local hosts file directly:
127.0.0.1 localhost MYHOST MYHOST.mycompany.com
Testing now with ping:
C:\Users\ME>ping MYHOST
And the answer:
MYHOST.mycompany.com [127.0.0.1] ping:
response 127.0.0.1: byte=32 time<10 ms. TTL=128
...
At this point I have restarted (stopped and started again) the both running Oracle services (just for sure):
OracleServiceXE
OracleXETNSListener
And look the miracle:
C:\Users\ME>lsnrctl
LSNRCTL for 32-bit Windows: Version 11.2.0.2.0 - Production
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 11.2.0.2.0 - Production
Default Service XE
Listener Parameter File /oraclexe/app/oracle/product/11.2.0/server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\diag\tnslsnr\MYHOST\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MYHOST.mycompany.com)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL>
You can see the important line with PORT=8080 and service XE instance.
So I am happy the getting started URL is working again.
What browser are you using? I experienced the same issue with Chrome. Download firefox, Right click the "Get Started With Oracle Database 11g Express Edition" icon and change the "opens with" option to firefox.
Simple solution:
You need to directly tell where your http port is. To do so; open up the folder where your Oracle is stored and navigate to server folder( in my case C:\Oracle\oraclexe\app\oracle\product\11.2.0\server) in that folder right click to Get_Started file and choose properties. There you can hand type your http port which is usually 8080 in my case: ....127.0.0.1:8080/apex/f?p=4950
The problem should be solved.
Hope this helps you get through it..
Pinar U.S.
Right Click on the "Get Started" icon and click on the properties and select General tab. Click on change button and select other browser installed in your system other than the current one . after setting this up, you'll be able to open the panel.
I also experienced the same problem for this go to start-> all programs -> Oracle Database 11g Express Edition and right click on get started and click open file location and drag and drop the "Get_Started" to your browser
Ok, I found the solution. Right click on icon of "Get Started With Oracle Database 11g Express Edition", then "properties". Then click "General tab" and then you will see option "change", click on that and then select your browser, click "apply" and "ok". And then start the Database again.
Drag and drop get started link into browser address bar worked great for me, I tried EVERYTHING else, adding port to hosts, changing port in properties etc. nothing worked, until I dragged and dropped... So damn simple, wish I did that hours ago
Your solution is partially correct buddy. You need to match the entries in the file:
C:\oraclexe\app\oracle\product\11.2.0\server\network\ADMIN\listener.ora
(the entries with the --> mark)
:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
--> (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
--> (ADDRESS = (PROTOCOL = TCP)(HOST = myserver.company.com)(PORT = 1521))
)
)
:
With the entries in the file:
C:\Windows\System32\drivers\etc\hosts
(the entries with the --> mark)
:
--> 127.0.0.1 localhost
--> 1.2.3.4 myserver myserver.company.com
:
Finally, under Administrator account do:
C:> lsnrctl stop
C:> lsnrctl start
Solved. No need for changing name, no drag & drop either.