Alternative to modprobe serial port [closed] - command-line

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am working with a display that runs with a linux kernel.
I am trying to connect a device using serial communication to my display through a USB port.
To do this I am using a USB-serial converter.
When I am using the command lsusb I can see that my device is connected.
Bus 002 Device 002: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port
The problem is that when my USB-serial converter is plugged I can't find my /dev/ttyUSB0 path.
I tried the command : modprobe serialport vendor=0x0557 product=0x2008 but it seems that the serialport module is not available on my display according to the answer I am receiving :
modprobe: FATAL: Module serialport not found in directory /lib/modules/4.19.135-
Does anyone knows an alternative to modprobe serialport to get my converter recognized as a serial device ?
nb : My USB-Serial converter is a pl2303 converter and I am working with a 4.19.135 linux kernel.
Thank you,
Emmanuel

Related

Port Forward Raspberry Pi's Shared Internet Connection [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I currently have a setup where I got a raspberry pi connected WIRELESSLY to a router and a WIRED desktop connected to the raspberry pi (via Ethernet) and receiving internet from the pi. On the Desktop I want to run a Minecraft server on port 2000, however, I believe that because of my setup this port can only be seen by the PI alone and any not the router and anything else connected to the router. I currently have the PI ITSELF port-forwarded on the router for port 4300, I just need some way to link the pi's wireless connection of port 192.168.1.55:4300 to the shared Ethernet connection of port 192.168.220.78:2000.
I've looked into messing around with the IPTABLES in Rasbian Linux but I don't fully understand them.
My ultimate goal is to let this server be accessible to anyone outside of my home.
I found the problem, apparently, I needed to accept the incoming connections on the server's computer. So on the same computer as the minecraft server I ran: sudo iptables -A INPUT -p tcp --dport 2000 -j ACCEPT

GPS Module blinking but not receiving any data with RPi 3 [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am using a Neo-7M-0-000 GPS Module and the on-board LED is blinking, meaning it has a fix. But when I try to get the readings either through
sudo cat /dev/ttyAMA0
or through
cgps -s
It says "NO FIX".
I have connected VCC to 3.3V, GND to GND, TX to RX and RX to TX on a Raspberry Pi 3B.
Any suggestions would be greatly appreciated!
Point it to /dev/ttyS0 instead, AMA0 only on Pi 1 & 2.
Make sure serial is enabled
sudo raspi-config
P6 Interfacing Options
No to enabling login shell
Yes to enable serial port hardware
Then run
sudo gpsd /dev/ttyS0 -F /var/run/gpsd.sock
Test with cgps -s

system library:connect:No route to host [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Improve this question
I have a small sample application which send some data to the server and close the connection afterwards. I ran it on my localhost as server & client and it worked.
When I ran the same code after changing the IP to another host(running Cent OS in VM) as server and my client (Ubuntu), I get the following error from client binary.
client.c : 47 Error connection to remote machine
139915881411416:error:02002071:system library:connect:No route to host:bss_conn.c:246:host=192.168.56.101:6001
139915881411416:error:20073067:BIO routines:CONN_STATE:connect error:bss_conn.c:249:
I am able to ping the remote server from my terminal. Any suggestions or solutions are welcome :) .
Actually the problem was because of firewall running on server(Cent OS). After stopping the firewall using command,
service iptables stop
the client was able to make a connection with the server.
Better Solution (without stopping firewall):
Add your client's IP address in the iptables so that it will allow the client to connect to your server without stopping firewall.
iptables -I INPUT -s <client_ip_address> -j ACCEPT

What's the simplest way to make a local address socket publicly available? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have a HTTP enabled device on my local network that listens at let's say 192.168.1.32:9427. What's the simplest way to make public access to that socket?
you need to port forward from public ip address to private ip-address on port no. 9427
example:
public ip : 20.20.20.20
private ip : 192.168.1.32
Now when someone try to access your local http server should access via 20.20.20.20:9427
to do that :
you need to enable that on your adsl modem or on your router device
to do that for your adsl modem from here
How to Port Forward Your Router
check open ports to see if port no. 9427 is opened or not
Open Port Check Tool
you need to allow your iptables if you are using linux machine and allow port no. 9427
to do that :
iptables -I INPUT 1 -p --dport 9427 -s -j ACCEPT
echo 1 > /proc/sys/net/ipv4/ip_forward

Remote desktop connection to Raspberry Pi without specifying a port [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have a Raspberry Pi running Debian 7 (Wheezy) connected on "Site A", where the network is managed by a third-party company and where all ports are closed to the Internet (for security reasons). So, there is no way for me to do any port forwarding to VNC, nor SSH or anything else. That means I just can't access it in any way other than locally, on-site.
However, I need to connect to that device on the X Desktop session (graphical interface) to do some maintenance, and I am located in let's say "Site B", which is nearly 300 miles away from site A.
I know you can do such tasks on Windows or x86 Linux computers with TeamViewer (we use it for our other hardware in the same location and it works like a charm), but since the Raspberry Pi is based on an ARM architecture, it isn't supported by TeamViewer yet.
If anyone has ever achieved this, I would be glad to hear how to do it!
Since you have no ssh access, I can safe you from going on site A once.
I would setup a reverse ssh tunnel for ssh and VNC to a computer on the raspberry:
nohup ssh -N -R 3000:localhost:22 you#site-b &
nohup ssh -N -R 3001:localhost:5900 you#site-b &
You might implement some "watchog" which reconnects the tunnels if they should get disconnected for some reason. I assume that a VNC server is already running on the raspberry.
On site B you can now use:
ssh -p 3000 localhost # ssh to raspberry.
or VNC to the raspberry using localhost:3001