wpa_supplicant.conf - adding a mixed WPA2+WPA3 network - embedded-linux

I have successfully connected an embedded Linux board running wpa_supplicant 2.9 to a Fritz!Box router using this wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
# Connect via WPA2 to a WPA2+WPA3 network
ssid="my_network"
psk="password"
key_mgmt=WPA-PSK
}
This connection, on the Fritz!Box router, shows up as a WPA2 connection. The router shows other devices connected via WPA3 which is what I'm trying to achieve with the Linux board. I've tried:
network={
# Connect via WPA3 to a WPA2+WPA3 network
ssid="my_network"
psk="password"
key_mgmt=SAE
ieee80211w=1
}
I've tried a few variation but without success.
wpa_supplicant was built with:
CONFIG_SAE=y
Anyone have any pointers please?

Related

Kubernetes on Windows Error: Unable to connect to the server: dial tcp some ip

I have downloaded Docker and then enabled Kubernetes on the Desktop. When I execute 'Kubectl version' command on the PowerShell it says:
kubectl : Unable to connect to the server: dial tcp : connectex:
A connection attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because connected host has
failed to respond.
At line:1 char:1
kubectl version
The same issue started to occur today when I run anything related to kubectl on Windows. However, it previously worked fine. Maybe there are some recent updates in Windows/Docker.
UPD
Actually, my network sharing options were reset for some reasons. Please try the solution described below (works for me)
SOLUTION:
Check your Network and Sharing settings:
Control Panel > Network and Sharing > [YOUR_NETWORK] (For me it's my Wi-Fi connection) > Properties > Sharing
On the Sharing tab make sure that you have all checkboxes checked and that you selected the correct virtual network in the "Home network connection" field. If not, please use the correct one.

Can't connect remotely to WAS 8.5 full profile installed on Ubuntu 14.04 from RAD 9.5 installed on OSX

WAS 8.5 full profile isn't officially supported on OSX by IBM so the only option to perform development from OSX is to install stub runtime and connect to WAS installed remotely. I'm trying to install such scenario but something done wrong and can't connect to my WAS.
There's my installation:
On OSX El Capitan Installed:
RAD 9.5 with WAS 8.5 stub runtime (WebSphere Application Server traditional V8.5 stub)
Installed Virtual Box with Ubuntu Desktop edition 14.04
Ubuntu's hostname: anatoly-ubuntu-vm and it's accessible from host, i.e. ping anatoly-ubuntu-vm works fine
On Ubuntu installed:
WAS 8.5 full profile at /opt/IBM/WebSphere
Created AppSrv01 profile at /opt/IBM/WebSphere/AppServer/profiles
WAS installed with root user, IBM Installation Manager required root permission when was started
My connection settings in RAD:
server name: WebSphere Application Server traditional V8.5 stub at anatoly-ubuntu-vm
hostname: anatoly-ubuntu-vm
Runtime environment: WebSphere Application Server traditional V8.5 stub
Connection type:
I've tried RMI 2809 and SOAP 8880 both options didn't work
Enable the server to start remotely is checked and Select the operating system running the remote server: checked Linux option with my username and password. I've tried my regular Ubuntu account and root, both option didn't work.
Server profile path defined as /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
When I try to start server I get the following exception:
The following problems has occurred when starting the server.
CTGRI0001E The application could not establish a connection to
anatoly-ubuntu-vm .
What am I doing wrong?
UPDATE 1:
After I've written this post I've figured out that SSH server isn't installed and configured at all as described here: Requirements for using Remote Execution and Access (RXA) Now, I've installed and it seems like connecting but stuck at 23% at stage Preparing launch delegate, after a while it throw the following error:
The following problems has occurred when starting the server. The
server may not be started in the correct mode. You can restart the
server to desired mode if it is started. CTGRI0075E A file transfer to
or from the system named [anatoly-ubuntu-vm] timed out before the
transfer could complete. The current timeout interval is set to 240000
milliseconds, and might need to be increased.
UPDATE 2:
As I can see despite error message server is started and I even can connect to web console anatoly-ubuntu-vm:9060/console/ibm but it looks that not SOAP connection, neither RMI connection don't work. When I run Test Connection from Settings overview page in RAD, I get the following error:
The connection failed after trying to use all the available connection
types.
Verify the port values are correct and the server has been started. If
the security of the server is enabled, verify the "Security is enabled
on this server" check box is selected, and the user ID and password
are provided. You can specify this in the server editor or when
creating a new server.
For a Technote with details on the most common server connection
problem, see http://www.ibm.com/support/docview.wss?uid=swg21266028.
The last connection attempt failed with the following exception:
ADMC0016E: The system cannot create a SOAP connector to connect to
host anatoly-ubuntu-vm at port 8880.
UPDATE 3
As #DanielBarbarian guessed I tried to run ./wsadmin.sh -port 8880 and it worked and returned
Connected to process "server1" on node anatoly-ubuntu-vmNode01 using SOAP connector; The type of process is: UnManagedProcess`
This is settings of my ports:
UPDATE 4
When I trying to run telnet anatoly-ubuntu-vm 8880 from OSX host I get the following response (ip address changed to non real due to privacy issue):
anatoly-mac:~ anatoly$ telnet anatoly-ubuntu-vm 8880
Trying 192.168.10.10...
Connected to anatoly-ubuntu-vm
Escape character is '^]'.
HTTP/1.1 408 Request Timeout
Content-Type: text/html
Content-Length: 117
Connection: close
<HTML><TITLE>408 - Request Timeout</TITLE><BODY>
<h1>408 Connection timed out while reading request</h1></BODY>
</HTML>Connection closed by foreign host

Unable to Retrieve Directory Using ProFTPD(WHM)

Well, after looking for many solutions. I came here now.
I am setting up WHM/cPanel for hosting website. Everything was going smooth but I am stuck on FTP connection (Server sent passive reply with unroutable address. Using server address instead.)
Server Details:
CentOS Linux release 7.2.1511 (Core)
WHM/cPanel Version 11.58.0.13
FTP Server: PureFTPD
Acutal error while connecting
To fix this issue and get FTP working you need to open up more numbered ports so FTP can connect. I assume you are using CSF.
Login to WHM then go to CSF >> Firewall Configuration >>
allow TCP_In 30000:50000 and TCP_Out 30000:50000
Once you made the changes Restart the firewall
Now you need to make changes in FTP config file to use these ports, you will find this file to this location /etc/pure-ftpd.conf
Now you will see a line as follows and you will need to uncomment it
# Port range for passive connections replies. - for firewalling.
PassivePortRange 30000 50000
Restart FTP Service and should work.

"Connection refused" trying to connect to Heroku DB from one computer, but not the other, same network

I opened up a new account with Heroku and installed the dev Postgresql add-on. I'm using a 2010 Mac Pro with OSX 10.8.5 with firewall disabled, directly connected to my RCN/Cisco cable modem, and I installed Postgresql 9.3 on my local machine from http://postgresapp.com/. I could connect to the Heroku postgresql fine from a Macbook Air, but not the Macbook Pro. So from both machines, I tested connecting to port 5432 with telnet. Connects fine on the Macbook Air, but not the Mac Pro. I can browse the web fine from both machines, and also connect to a telnet site (one I had available) on port 4000 on both.
I get this error:
Trying 54.235.194.252...
telnet: connect to address 54.235.194.252: Connection refused
telnet: Unable to connect to remote host
Using Wireshark, I tried viewing the tcp packets on port 5432 when trying to telnet. Just the Connection refused, and nothing showed up on the packet log. But I saw plenty when telnetting on port 4000.
Other things I tried on the Mac Pro:
I did an nslookup ec2-54-235-194-252.compute-1.amazonaws.com
and it returns 54.235.194.252 as expected.
traceroute on the IP address gives a No route to host and mtr shows
nothing too.
sudo ipfw list shows 65535 allow ip from any to any, which is the same as the Macbook Air
tcpdump and Wireshark for that host on the active interface showed nothing when telneting. Seems to have gotten dumped even before getting to the interface.
I then tried running the telnet command through dtruss and saw this:
write_nocancel(0x1, "Trying 54.235.194.252...\n\0", 0x19) = 25 0
socket(0x2, 0x1, 0x6) = 3 0
getuid(0x2, 0x1, 0x0) = 0 0
setuid(0x0, 0x1, 0x0) = 0 0
setsockopt(0x3, 0x0, 0x3) = 0 0
connect(0x3, 0x7F8F20C0DAD0, 0x10) = -1 Err#61
write_nocancel(0x2, "telnet: \0", 0x8) = 8 0
write_nocancel(0x2, "connect to address 54.235.194.252\0", 0x21) = 33 0
write_nocancel(0x2, ": \0", 0x2) = 2 0
write_nocancel(0x2, "Connection refused\n\0", 0x13) = 19 0
write_nocancel(0x2, "telnet: \0", 0x8) = 8 0
write_nocancel(0x2, "Unable to connect to remote host\0", 0x20) = 32 0
write_nocancel(0x2, "\n\0", 0x1) = 1 0
close(0x3) = 0 0
Err#61 is the BSD error code for ECONNREFUSED, which makes sense. I think the socket options is setting the IP "Type of Service", but I'm not sure. It looks like setsockopt has 5 arguments, but I only see three. I have a feeling it's not relevant. I have no idea what could be getting in the way other than ipfw and the firewall in System Preferences. I also tried with the newly installed postgresql running and not running.
Any insights?
Figured out what was wrong with my Mac Pro. Discovered you could safe boot in OSX... hold down "Shift" after the startup tone, then let go when you see the gray apple icon. Could connect no problem in safe mode. Noticed another game I was running via Wine, Subspace/Continuum, also started working. So I compared the "ps aux" in safe and normal mode. A couple of lines, only in normal mode, referred to a program, "Peer Guardian" that was silently blocking random ports from being used. Looked up and realized there was a tiny "PG" mixed in with other symbols on my menu bar, just waiting to make me feel embarrassed. Had to uninstall it using a tool I got off CNET called "AppDelete". Ugh.

Postgresql is not allowed to be connected remotely

Could someone help take a look this weird problem? I'm still not able to connect remotely to my Postgresql.
My Steps:
Download and install the latest Postgresql to my local machine
Setup postgresql
Create a DB
Modify "pg_hba", add row "host all all 0.0.0.0/0 md5"
Modify "postgresql.conf", make sure "listen_addresses = '*'"
Restart postgresql service
Open local PgAdmin, and connect to DB <-- Success!
From Remote desktop, do the same thing as #7 <-- Failed!
Error Message:
"Server doesn't listen"
"Could not connect to server......accepting TCP/IP connections on port 5432?"
I found "TCP 0.0.0.0:5432 Listening" when I type "netstat -a"
I checked firewall, it's not enabled
......
Can someone please help? Does anyone encounter this situation?
P.S, my os is Winserver 2008
Thanks in advance~
If you're connecting to the local machine via RDP then you'll be connecting via localhost and no firewall or LAN/WAN/NAT settings should affect pgadmin.
When you edit the pg_hba and postgresql.conf files Server 2008 doesn't usually let you edit them directly where they are. I usually copy them out edit them and then paste them back in. You'll need to authorise the paste from an Admin account.
I usually have a separate rule in "pg_hba" with "host all all 127.0.0.1/32 md5" for local connections. Also ensure when you restart the service that it is running under the user "postgres" and not as some other user.

Resources