[Q] Issue with PDP connection Android - Networking

My device is Asus transformer with 3g. I send sequence AT commands into /dev/ttyACM0 and received IP, GW, DNS from operator. Them I used ioctl codes for assign IP, GW and bringing up interface. But I dont pinging gw: destination host unreachable. What I need to do more?

Related

Is it possible to give my Hermes a static IP?

I connect to a WiFi network where each component has a static IP, the problem being that my Hermes will take the earliest free IP address that it can find causing the PC which has that IP address to start spouting errors?
How can I remedy this?
If you have access to the router or buzz the (lousy ) administrator, configure the DHCP to a range that noone has a static IP in (for example x.x.x.250 and up)
After playing around with the router I think that I might have struck gold. Thanks for the speedy reply. I'll post an update in a day or two.
You can set fixed IP addresses on the device as follows:
Start>Settings>connections>Network cards>network adapters (tab)
Here you can then tap each type of connection on the list and choose either server assigned address or enter a specific address.
Mike

[Q] DHCP with Gingerbread issue

Here is the shakedown
Have a full Windows 2003 Native domain environment. DNS, DHCP etc. Verizon Fios ISP with Actiontek Wireless router. DHCP has been disabled on the router. While Evo was running on “Froyo” WIFI was working fine. It would obtain a lease from the WIN2003 DHCP server and access local and Internet resources. After applying the “gingerbread” update external access is not available, (google, msn etc), Local works fine. The IP obtained is from the production scope (192.168.1.XX). If I statically assign an IP from that scope it will work. Any thoughts??
anyone? bump

[Q] Connect to External IP from inside local network?

Where I work we use a software program that we connect to using our smartphones (some android, some windows mobile). To access the site we type the external (static) IP address and port into the phone's browser. However we do not get a very good cell signal in our building, so indoors we will use the wifi usually. This means instead of connecting to the external IP address, I have to use the internal IP to connect. Does anyone know of a way that I can connect using the external IP even when connected to the local wifi network so I don't need to change the IP I'm connecting to every time i go in and out of the building?
Have you tried using the external IP while on WiFi at work. It's simply a public IP and NAT should redirect it to the private IP address. Essentially data will travel out to the Internet and back to the Intranet.
Do you have the FQDN of the server? Ask your IT department, I'm sure they'd tell you the FQDN. You should be able to use that internally & externally. If you are connected to WiFi then internal DNS servers should resolve it to the local address and if you are external then public DNS records should help you find your way to the public IP.
+1 on what michaelkahl said. You will need to have your network dept to add DNS records if they don't already exist. Externally the FQDN (i.e. server.yourcompany.com) would resolve to the external public IP while internal DNS servers would resolve to the internal private IP.
We do this at my company for users connecting to a terminal server. No matter if they are at home or in the office they can use ts.ourcompany.com to connect to the server.

Problem with ethernet in Samsung Galaxy Tab 4 8' (SM-T330), android 5.1.1

Hi everybody,
I have a problem with the ethernet connection in the Samsung Galaxy Tab 4 8' WiFi (SM-T330).
I need to connect the tablet to a embedded system through ethernet with a static IP address, and in order to achieve this I use a MicroUSB-RJ45 adapter that in android 4.4.2 works perfectly fine, but when I upgraded to android 5.1.1 the ethernet connection stopped working.
A key requirement I have is that the IP address must be static. This is important because making some research I've connected the tablet to a LAN and with ethernet configured as DHCP and I have internet connection, but when I change the configuration of the connection to a static IP I can't even make ping to the gateway. If I execute in a terminal emulator the command 'netcfg' I can see the interface eth0 up with the correct IP assigned (192.168.1.98). If I run the command 'ip route show' I can see the following in the output:
default via 192.168.1.1 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.98
Which is apparently correct IMO, but the fact is that if I ping the 192.168.1.1 address I get "Network is unreachable" error.
Just to compare, the output of 'netcfg' and 'ip route show' in case of DHCP configuration is pretty much the same:
default via 192.168.1.1 dev eth0 metric 238
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.179 metric 238
But this time everything works fine.
I have no clue why it doesn't work with a static IP. Can anybody help me with this issue? I'm doing something wrong, or this is an android 5.1.1 bug?
Thanks in advance.
pazonks said:
Hi everybody,
I have a problem with the ethernet connection in the Samsung Galaxy Tab 4 8' WiFi (SM-T330).
I need to connect the tablet to a embedded system through ethernet with a static IP address, and in order to achieve this I use a MicroUSB-RJ45 adapter that in android 4.4.2 works perfectly fine, but when I upgraded to android 5.1.1 the ethernet connection stopped working.
A key requirement I have is that the IP address must be static. This is important because making some research I've connected the tablet to a LAN and with ethernet configured as DHCP and I have internet connection, but when I change the configuration of the connection to a static IP I can't even make ping to the gateway. If I execute in a terminal emulator the command 'netcfg' I can see the interface eth0 up with the correct IP assigned (192.168.1.98). If I run the command 'ip route show' I can see the following in the output:
default via 192.168.1.1 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.98
Which is apparently correct IMO, but the fact is that if I ping the 192.168.1.1 address I get "Network is unreachable" error.
Just to compare, the output of 'netcfg' and 'ip route show' in case of DHCP configuration is pretty much the same:
default via 192.168.1.1 dev eth0 metric 238
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.179 metric 238
But this time everything works fine.
I have no clue why it doesn't work with a static IP. Can anybody help me with this issue? I'm doing something wrong, or this is an android 5.1.1 bug?
Thanks in advance.
Click to expand...
Click to collapse
how to you connect tablet with LAN cable?
thelous said:
how to you connect tablet with LAN cable?
Click to expand...
Click to collapse
They said (and I quote):
in order to achieve this I use a MicroUSB-RJ45 adapter that in android 4.4.2 works perfectly fine, but when I upgraded to android 5.1.1 the ethernet connection stopped working.
Click to expand...
Click to collapse
thisisapoorusernamechoice said:
They said (and I quote):
Click to expand...
Click to collapse
Ohh i thought he mean tab 4 8.0 had ethernet port LOL., but why use LAN cable whek you can get same speed with wifi? Atleast i am getting same speed on tablet as i have on desktop computer....
I believe I am having the same problem. Any word on what is going on?
I was able to get UDP messages out to work intermittently by finding a network that it would connect with and then connecting it back into the network I wanted it to work with. I could not get the initial connection consistently, though.
I was able to get everything working again by flashing 4.4.2 onto the tablet, factory resetting, not letting anything update, and setting up my Ethernet network.

Android-device as an ethernet-router

The scenario: I have a rooted lollipop-TV-Box (S905) with Wifi, Ethernet (RJ45) and USB. The box is connected to internet via a wifi-router. Nearby I have a orange pi running with armbian (a debian-derivate for arm) with ethernet and USB but not wifi. I want to connect the orangepi via TVBOX-ethernet to the router to internet. This is my prefered solution. Alternativly I could also use a USB-connection between box and orangepi, but thats not prefered due to speed-reasons and the need for an additional client on the orangepi that are required for most usb-tethering solutions, and the box has no usb-tehering capabilities
I tried it the Linux-way on a linux-Machine with a shell-script. The wlan-net is 192.168.0.x the lan is 192.168.1.x. The wlan-ip in the Android/Linux router is 192.168.0.13 the lan in the same device is 192.168.1.2, the connected lan-client-ip is 192.168.2.4
the routing is Internet-(Wifi)-Gateway 192.168.0.1->Android/Linux-Box 192.168.0.13/192.168.1.2->192.168.2.4 and vice-versa
on lan-client:
ip route:
default via 192.168.1.2 dev eth0 proto static metric 1024
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.4
on Android/Linux-Router
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.13 metric 600
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100
I also enabled forwarding and set the forward-tables with iptables
With the Linux-Box as a router everything works like a charm, with Android not, when I ping the lan-ip of the client from the Android box (ping 192.168.1.4) the reply is network unreachable from the external internet-server
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
From 84.116.198.82: icmp_seq=7 Destination Net Unreachable
From 84.116.198.82: icmp_seq=8 Destination Net Unreachable
From 84.116.198.82: icmp_seq=17 Destination Net Unreachable
I have to specify the interface with ping -I eth0 192.168.1.4, then it works, although this should already be specified by the local routes, like if the local request is routed over the public gateway. Looks like in Android the local routing is overriden by a hidden route to the default gateway

Categories

Resources