[Q] KuyaDroidv3.2.175 static IP - XPERIA X8 Q&A, Help & Troubleshooting

is there anybody with working static IP in kuyadroid 3.2.175, i have configure mine with static IP but its using dhcp mode.

Related

ICS connects, cant ping external sites

I got Bluetooth PAN to connect to my Tilt with WM6.1
using internet connection sharing
192.168.0.1 is my gateway
192.168.0.187 is my IP
i can ping the phone
cannot ping www.yahoo.com
cannot browse
any ideas?

Wireless tether static ip?

Is this possible and if so how do I go about it?
Bump .......................

Raspberry Pi VPN Issues

Using my raspberry pi, I created a pptp vpn server, but I find myself unable to connect to it under my school's wifi (I am able to connect to other wifi via the raspberry pi). Would programs such as iprism the school is running prevent me from accessing the vpn?
Yes iprism could prevent you from connecting to your PPTP server as any other webfilter, proxy server, etc. could do as well.
You maybe get around that if you're dropping PPTP and use OpenVPN instead. This alone wouldn't help much but running your server on port 443 could do the trick .

sixaxis controller change mac adress

hum i can't seem to find the problem.. i change the ip. i disconcte the controler and ip gets back to 00:00:00:00:00:00
how come?

Chromecast Connected but unable to access internet...

Hi Guys,
I've got a rather unusual setup for my home-internet where by I have a main router (192.168.1.1) which provides Wi-Fi to one part of the house and a second router turned into an access point (192.168.1.1) by running an ethernet cable from router 1 to router 2.
I've connected my Chromecast successfully to the TV near the 192.168.1.1 router but when I try to use it on the TV near the 192.168.1.2 router if it connects to the 192.168.1.1 router it's extremely laggy as it only has 1 bar of signal.
However, if it connects to the 192.168.1.2 router and then use my phone to try to cast to the TV it works nicely; however the TV has no internet access so it can't stream via YouTube... etc as you can see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've given the Chromecast a static IP in both routers so that it has the IP of 192.168.1.115, it's rather confusing because the Chromecast shows that it has the right IP as you can see: http://i.imgur.com/7L2RxUj.png and other wireless devices work like my phone does when it's got a static IP connected to the second router.
Here are some side by sides of each router's settings.
WAN Connection Settings: http://i.imgur.com/TtfrgLZ.png
WAN Bridge Connection Settings: http://i.imgur.com/5iEijHk.png
LAN DHCP/Static IP Settings: http://i.imgur.com/YF4V7Mw.png
WLAN Settings: http://i.imgur.com/4k4Pveu.png
ADSL Settings: http://i.imgur.com/ZGDLL0W.png
Routing (RIP) Settings: http://i.imgur.com/WuNWmUQ.png
Firewall Settings: http://i.imgur.com/hSIWSL0.png
NAT Settings: http://i.imgur.com/jFGzmcd.png
IGMP Settings: http://i.imgur.com/bFz5jkr.png
UPnP Settings: http://i.imgur.com/nvsxBjA.png
Power Savings: http://i.imgur.com/fjUz9Tj.png
DLNA Settings: http://i.imgur.com/lQE4hgc.png
Connection Mode: http://i.imgur.com/2181vSs.png
Does anyone know what settings should be changed / are incorrect?
Any help would be much much appreciated!
I just messed around some more and it's because the Chromecast auto-detects gateway information.... if it detects gateway as 192.168.1.2 it wont work because of something to do with the router...
If the gateway was 192.168.1.1 but connected to the 192.168.1.2 router it would function correctly..
How do I get round this?
Would I have to do something with the below:
DSL Access types:
http://i.imgur.com/5lLoimL.png
http://i.imgur.com/2WT6wY7.png
http://i.imgur.com/F4lESv6.png
http://i.imgur.com/7qvkFiW.png
Ethernet Access types:
http://i.imgur.com/EsjOskJ.png
http://i.imgur.com/op9nF3Y.png
http://i.imgur.com/43Azjo5.png
UMTS Access types:
http://i.imgur.com/BPQg1Oz.png
Where do you have the ethernet connection from router 1 connected into router 2?
If it's connected into the WAN port, the problem probably is that your WAN and LAN network interfaces both have the same subnet, which just plain won't work. Even if it did, your NAT firewall on router 2 would probably interfere with proper communication between your Chromecast and your phone/browser.
If it's connected to your LAN port (which is how I'd suggest connecting them), you shouldn't have DHCP enabled on router 2.
Good luck!
muchtall said:
Where do you have the ethernet connection from router 1 connected into router 2?
If it's connected into the WAN port, the problem probably is that your WAN and LAN network interfaces both have the same subnet, which just plain won't work. Even if it did, your NAT firewall on router 2 would probably interfere with proper communication between your Chromecast and your phone/browser.
If it's connected to your LAN port (which is how I'd suggest connecting them), you shouldn't have DHCP enabled on router 2.
Good luck!
Click to expand...
Click to collapse
Hi,
I have the ethernet connected to the LAN1 port on router 2, I've tried connecting it into the fiber port but don't know how to set it up to allow networking via the fibre port.
So your suggestion is to disable DHCP?
It's weird because if I'm connected to Router 2 on my phone I can still control my Samsung TV via the SammyGo app and also my Sky+ Box that are both connected to Router 1.
Yes. My guess is that the DHCP server on the second router is serving up leases with the wrong gateway (.2). Leaving DHCP enabled on router 2 would allow all of your LAN devices to communicate with each other, but any device that gets the .2 gateway lease won't see the internet.
You should only have one DHCP server on a network anyway, unless you know what you're doing and have some sort of redundant server config set up. But in that case you wouldn't be here talking to me
Exactly what muchtall said.
Connect the two routers LAN-LAN, but set the secondary AP's gateway to the first router's LAN address and turn off the secondary AP's DHCP server.
That way everything should get DHCP from the primary AP/router and Internet traffic will route correctly.
Have had to do this many times to get around silly ISP router/modem combos and use my own router.
muchtall said:
Yes. My guess is that the DHCP server on the second router is serving up leases with the wrong gateway (.2). Leaving DHCP enabled on router 2 would allow all of your LAN devices to communicate with each other, but any device that gets the .2 gateway lease won't see the internet.
You should only have one DHCP server on a network anyway, unless you know what you're doing and have some sort of redundant server config set up. But in that case you wouldn't be here talking to me
Click to expand...
Click to collapse
I disabled the DHCP on the second router and it did nothing even with devices and routers rebooted, I then tried to set the LAN Host on the second router to .1 even though I was sure it would just cause a conflict and as soon as I did this the entire network became unstable internet was up then down, up then down... over and over.
I had it set like this: http://i.imgur.com/5Zq8fk6.png
bhiga said:
Exactly what muchtall said.
Connect the two routers LAN-LAN, but set the secondary AP's gateway to the first router's LAN address and turn off the secondary AP's DHCP server.
That way everything should get DHCP from the primary AP/router and Internet traffic will route correctly.
Have had to do this many times to get around silly ISP router/modem combos and use my own router.
Click to expand...
Click to collapse
Either I'm understanding something wrong or I'm doing something wrong...
I tried the following: http://i.imgur.com/5Zq8fk6.png but as I said to muchtall, it just made the network incredibly unstable because of an ip conflict I guess?
EDIT #1, To both...
Do I need to do something in static routing: http://i.imgur.com/mBUeYFQ.png
EDIT #2
I think I've got it working... I disabled DHCP, kept it on .2 and changed the WAN settings to the following:
http://i.imgur.com/axPP5tv.png
The LAN cable is connected in LAN1 and I'm using SSID1 (it appears to be working on my phone and chromecast atm)
I might be getting lost with what you are trying, so let's just lay out the ground rules of what you must have configured to make a double wireless "router" network work:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2
Router 1 should be connected via the WAN port to the internet
Router 1 should have an IP address of 192.168.1.1
Router 1 should have DHCP enabled
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1)
Router 2 should have DHCP disabled
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network.
If you are still having problems, try a few tests when connected to Router 2 with a computer:
Can you ping 192.168.1.1?
Can you ping 8.8.8.8?
Can you open http://google.com?
(Assuming you are on Windows) Post the output of "ipconfig /all" here (which you can run in a "cmd" window).
Once we know the results of those tests, and the network config of your computer connected to Router 2, we might be able to determine what's wrong.
Edit: Glad to hear you got it working. Looks like your router supports WAN/LAN bridging. That's nice. Not all routers do. It also got me to thinking that one of the problems you can encounter when doing and LAN port to LAN port conection is htat hte ports may not support auto-MDIX (auto-crossover). Basically the RX pairs need to connect to the TX pairs on the RJ45 connectors. If your router's built-in hub didn't support it, you would have had to have made an ethernet crossover cable. Anyhow, hope everything works out in your testing. Good luck!
Maybe I'm wrong here....
But wouldn't it be better to connect the second router using it's WAN port (connected to LAN Port on main router) and then shutting off DHCP and putting the second router into Bridge mode with the same SSID?
Then it should just act as a repeater and would even stop from having interruptions when switching from one router to another?
muchtall said:
I might be getting lost with what you are trying, so let's just lay out the ground rules of what you must have configured to make a double wireless "router" network work:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2
Router 1 should be connected via the WAN port to the internet
Router 1 should have an IP address of 192.168.1.1
Router 1 should have DHCP enabled
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1)
Router 2 should have DHCP disabled
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network.
If you are still having problems, try a few tests when connected to Router 2 with a computer:
Can you ping 192.168.1.1?
Can you ping 8.8.8.8?
Can you open http://google.com?
(Assuming you are on Windows) Post the output of "ipconfig /all" here (which you can run in a "cmd" window).
Once we know the results of those tests, and the network config of your computer connected to Router 2, we might be able to determine what's wrong.
Edit: Glad to hear you got it working. Looks like your router supports WAN/LAN bridging. That's nice. Not all routers do. It also got me to thinking that one of the problems you can encounter when doing and LAN port to LAN port conection is htat hte ports may not support auto-MDIX (auto-crossover). Basically the RX pairs need to connect to the TX pairs on the RJ45 connectors. If your router's built-in hub didn't support it, you would have had to have made an ethernet crossover cable. Anyhow, hope everything works out in your testing. Good luck!
Click to expand...
Click to collapse
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2 Check
Router 1 should be connected via the WAN port to the internet Check
Router 1 should have an IP address of 192.168.1.1 Check
Router 1 should have DHCP enabled Check
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1) Check
Router 2 should have DHCP disabled Check
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network. Check
I tried this on my third router which is a D-Link DSL-3780; not a Huawei HG533 and when I try to connect my phone to this router it sits there trying to allocate an IP address but sits there trying over and over and constantly failing. I've tried to use the "DHCP Relay" option too but it does seem to solve the issue either.
If I then connect the third router to the computer and set the TCP/IPv4 settings like http://i.imgur.com/n77Gz3R.png then it connects fine, however if I make it obtain automatically like the Chromecast would then it fails to connect.
Pinging the Router
Code:
Pinging 192.168.1.1 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Pinging Google DNS
Code:
Pinging 8.8.8.8 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Obviously unable to access google.
Finally ethernet details (I've changed some addresses & ID's so nothing could potentially be done to my PC...)
Code:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
Physical Address. . . . . . . . . : 00-24-8C-29-A1-00
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::96x0:df12:e3s2:cb39%11(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.202.137(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : fe80::1%11
DHCPv6 IAID . . . . . . . . . . . : 236180380
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-89-45-44-00-24-9P-48-A1-DB
DNS Servers . . . . . . . . . . . : 8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Asphyx said:
Maybe I'm wrong here....
But wouldn't it be better to connect the second router using it's WAN port (connected to LAN Port on main router) and then shutting off DHCP and putting the second router into Bridge mode with the same SSID?
Then it should just act as a repeater and would even stop from having interruptions when switching from one router to another?
Click to expand...
Click to collapse
That's what I've done for the secondary router, it works now but my third router doesn't have that. Although not as important.
Hyflex said:
Both routers must be connected together via a LAN port on Router 1 to a LAN port on Router 2 Check
Router 1 should be connected via the WAN port to the internet Check
Router 1 should have an IP address of 192.168.1.1 Check
Router 1 should have DHCP enabled Check
Router 2 should have an IP address of 192.168.1.2 (or any other free address, just NOT .1) Check
Router 2 should have DHCP disabled Check
Router 2 does not need any routes configured (default or otherwise) since it is on the same broadcast segment as Router 1, and Router 1 handles routing for the network. Check
Click to expand...
Click to collapse
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
bhiga said:
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
Click to expand...
Click to collapse
Hmm, I can't find anywhere to setup a "LAN Gateway", I would of though the DHCP relay would have done the same thing but it doesn't do anything :/
Internet Setup: http://i.imgur.com/KufkUd5.png
Wireless Setup: http://i.imgur.com/Vqj8x2z.png
LAN Setup: http://i.imgur.com/1mm55I5.png
WLAN Performance: http://i.imgur.com/ATGL7dy.png
Virtual Server: http://i.imgur.com/3i6sJBb.png
Applications: http://i.imgur.com/7hkfG2k.png
Filter: http://i.imgur.com/0UXk2F7.png
Advancaed ADSL: http://i.imgur.com/redgNCY.png and http://i.imgur.com/AQHlo1v.png
Firewall: http://i.imgur.com/km0iXeZ.png
DNS: http://i.imgur.com/YfQ90OO.png
IGMP: http://i.imgur.com/PIuDGgR.png
QOS: http://i.imgur.com/7yBo8yE.png
UPnP & DLNA: http://i.imgur.com/bp2XJ5L.png
Samba: http://i.imgur.com/KXNJgLL.png
Static Routing: http://i.imgur.com/HtR73zu.png
RIP: http://i.imgur.com/F2pVJ5v.png
Hyflex said:
Hmm, I can't find anywhere to setup a "LAN Gateway", I would of though the DHCP relay would have done the same thing but it doesn't do anything :/
Click to expand...
Click to collapse
It would if the wireless clients are getting the primary router LAN address as the gateway, as outbound traffic will go there for the router to determine where to send it.
If the wireless clients are getting a different address, then that device needs to know to send the traffic to the primary router.
Wired clients on the secondary router will have the same issue.
But if your secondary router is connected from its WAN port to the primary router's LAN port in Bridge mode as pictured, no gateway needs to be specified because unknown traffic should route "out and up" through the WAN port.
bhiga said:
Make sure the second router's LAN gateway is set to the LAN address of the first router (192.168.1.1) otherwise it won't know where to send packets for its wireless clients and everything will end up in going nowhere.
Click to expand...
Click to collapse
That's not going to be of any use when the routers are connected LAN port to LAN port. DHCP handles that, and since the networks should be on the same broadcast segment, normal ARP discover handles the rest.
@Hyflex: DHCP Relay isn't going to be applicable either (since both routers should be on the same broadcast domain of the network), and in fact could interfere with proper operation. What is the current state of things? Is your Chromecast working, or no? If it's not working, do your applicable LAN ports show a link when the two routers are connected?
---------- Post added at 06:11 PM ---------- Previous post was at 06:04 PM ----------
bhiga said:
But if your secondary router is connected from its WAN port to the primary router's LAN port in Bridge mode as pictured
Click to expand...
Click to collapse
That alone would break the Chromecast functionality. The Chromecast has to be on the same subnet as the phone, unseparated by NAT.
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
Nevermind. Missed the bridge part.

Categories

Resources