Okay i have usb tethered my phone with my LInux box..
My Comp's IP: 192.168.42.129
My phone's IP: 192.168.42.206
I m able to ping both the "machines" ...However when i open a listening program on port 1234 (nc)
My linux box is unable to discover the freshly opened port..
I wud like to Establish a socket connection on any port of my choice...HOW CAN I DO???
ALSO instead of wifi ..can i use remote droid over this "ETHERNET OVER USB" network?????
Any inputs are welcome...BTW ANDROid is fascinating....Never thought one day my phone wud fake an ethernet hardware,Act as a DHCP and DNS server...Ridiculous..
Related
what naming convention does vnc want for the server to connect to
if i simply type in my servers ip address (like i do on normal VNC) i get a "invalid vnc server specified, server should be of the form host:display" error, then i try ip address followed by port ie xxx.xx.xx.xxx:5900 .. and still no luck,
tks in advance
cheers
C
Found this info on PocketPCCity:
Just for you people. server_name:display, means ip address:display number. The port 5800 relates to display 0, 5801 to 1, 5802 to 2, etc. I'm running serveral x-server, with rfb on linux, and can succesfully access these port. Just a handy tip to work with...
still no Joy
Thanks, digger but that didn't work either,
just to recap.
I have the VNC server app installed and running on my pc (i can connect to it from othe vnc viewers on other PC's
but on my XDA i cannot
i try to connect to my server by typing in the server address as
nnn.nn.nn.nnn:5800
have also tried all of the following
nnn.nn.nn.nnn:5801
nnn.nn.nn.nnn:5900
nnn.nn.nn.nnn:5802
were nnn.nn.nn.nnn = the ip address of my pc running the VNC server app
is my naming convention correct ? if so then i can continue to troubleshoot in other areas
tks again
cheers
C
how do you connect ?
from a cattle ?
from a usb cable ?
from a seriel cable ?
using IR ?
Rudegar said:
how do you connect ?
from a cattle ?
Click to expand...
Click to collapse
Yeah, PDA-phones are great: Even when sitting on top of my livestock I can still control my PC back at the ranch.
tried dial up and cradle
Hi Rudegar
I tried over a dial up connection
and the usb cradle,
no luck
Peter Poelman
yeah the new greenhorn which is to replace bluetooth make things like that possible and comfortable
I cannot connect to the CalDAV / CardDAV port of my server from my CM11 device.
telnet to server port from (non-Android Linux) laptop over wifi/LAN works fine
telnet to server port from (Linux) laptop connected to net via a USB 3G tether provided by the exact same phone/provider I'm having my issue with - fine
telnet from pretty much anywhere on the internet to my server port on a non-Android platform - all seems fine
telnet from my Android (CM) terminal (Terminal IDE is my fave but I've tried this with various terminal emulators) as root to my server - not fine. Why?
I know the issue isn't with my server, router or my 3G connection/ service provider - this has to be an Android / Android networking issue.
Note I'm not actually trying to telnet, I just use telnet to ping ports.
Any tips?
Device Info: Motorola Moto X Play, stock Marshmallow ROM (rooted)
Hiya!
I've been fiddling with this problem for a few days and even after lots of googling I have not found a solution.
I have a Plugable USB OTG Ethernet adapter based on the ASIX AX88772A chipset which works fine when connected to a router, as in I can use it as a main data connection.
When I connect it directly to the ethernet port on my laptop is when things start to break down.
Since there is no default network control for ethernet I drop down to a terminal on the phone and manually bring up eth0 and on my laptop set it's address appropriately.
Ping works fine from Android->Laptop provided I specify the interface to use ("ping -I eth0"), however the laptop cannot ping the Android at all and will just time out.
I've tried multiple IP configurations and even completely cleared out iptables just in case but my laptop is still just not receiving ICMP echo replies from the Android.
Does anyone have any ideas as to why it's doing this?
My end goal is to have my laptop tethered via ethernet to my phone and because it's an old laptop (iBook G3) this is one of the few options that doesn't require a tonne of extra pieces.
Thank you
Hi,
I've been trying for some time to share an internet connection between an android phone (tried with several phones) and an android Tablet (Samsung Active Tab 2).
Rooted the tablet (after some very long research) and tried the following methods:
1. Connect two devices with OTG connector, turned on RNDIS and configured both rndis0 interfaces to be on the same network (different IP addresses ofc) - no ping, nor udp messages (using a UDP Sender\Receiver app) go through.
2. Tried creating a VPN server on the host device (the one providing internet) which creates a tun0 interface that listens to the rndis0 interface - Could not connect to server.
3. Used "Easy Tether Lite" on both devices and managed to share internet, but limited to the Lite version which allowed the use of HTTP only - This shows that it can actually be done using only a USB cable and OTG adapter.
Would appreciate some help with this matter.
Thank you all,
EDIT: Was thinking this may be done using a different Ethernet interface instead of RNDIS. Any ideas?
Shedaim said:
Hi,
I've been trying for some time to share an internet connection between an android phone (tried with several phones) and an android Tablet (Samsung Active Tab 2).
Rooted the tablet (after some very long research) and tried the following methods:
1. Connect two devices with OTG connector, turned on RNDIS and configured both rndis0 interfaces to be on the same network (different IP addresses ofc) - no ping, nor udp messages (using a UDP Sender\Receiver app) go through.
2. Tried creating a VPN server on the host device (the one providing internet) which creates a tun0 interface that listens to the rndis0 interface - Could not connect to server.
3. Used "Easy Tether Lite" on both devices and managed to share internet, but limited to the Lite version which allowed the use of HTTP only - This shows that it can actually be done using only a USB cable and OTG adapter.
Would appreciate some help with this matter.
Thank you all,
EDIT: Was thinking this may be done using a different Ethernet interface instead of RNDIS. Any ideas?
Click to expand...
Click to collapse
hello,
I'm facing the same situation. I had the idea that option 1 should be easy but not.
The phone detect the tablet device and let me to activate the function "USB tethering" but nothing change on the tablet, impossible to navigate or ping.
Hello,
I am attempting to create an application that displays the IP address that a phone obtains when using a wired OTG Ethernet Adapter.
I have at my disposal a rooted Verizon S7 (SM-G930V ) running Android 8.0 (G930VVRS8CRK2).
The way I initially envisioned accomplishing this was via writing a shell script that brought the OTG adapter up and then grabbed an IP address via DHCP. Then I figured I could write an app to run that script, and grab the IP address and display it.
To start testing and planning this out, I just loaded a terminal emulator app so I could go through the steps manually to see how everything works first. However, I cannot figure out how to get the OTG adapter to grab a DHCP lease, and I think I must be missing something obvious; that doesn't seem like it should be that hard..
From what I have read, all I should have to do is
-ifconfig eth0 up
-dhcpcd eth0
Well, ifconfig works-I can bring the OTG adapter up, and I can give it a static IP and ping my gateway so I know the phone sees the adapter and it is working. However, I can't run dhcpcd-the terminal emulator says that the command isn't found..
So that brings me to my next question-how do I initiate DHCP on the eth0 OTG adapter? Can I do it via the shell/a shell sctipt, or is there some other way to do it via the Android SDK/methods exposed through normal app development procedures? I'm kind of baffled why I can't directly access dhcpcd-there has to be SOME way to get DHCP to works seeing as you can connect via wireless, etc and grab a DHCP address with no issues.
Thanks for the help!