Related
I'm currently running wm5 ivan w/rd
i keep having this problem where i try to connect to a network, and it connects, but i can't do anything.
When i open up my ipconfig it shows the network ip address as 169.254.x.x where x is always something different. My router shows the mac address on the network but it's unreachable.
Does anyone have any idea where this ip is coming from? I've tried different radio versions, and it happens so far with 1.1.13 and 1.1.15 on both wm5 AND wm3.
169.254.xxx.xxx is a class of ip addresses set automatically to a device, when this can't connect the dhcp server. is a reserved network.
if your router is set as dhcp server, you must verify the link connection with pda. else you must configure the correct ip address manually to the pda.
download and run vxIPconfig and use that to release and renew a new IP from the DHCP server
Nine times out of ten this is caused by bad encryption settings. If you put in the wrong WEP key for example this is what you would see. You don't get error messages when it's wrong, which is kind-of by design and desirable for security reasons.
I'm downloading vxipconfig right now. I did a search last night and was reminded of 169.254.x.x coming up on machines when winsock is corrupt.
Another web site said something about how a pda will connect to the first computer with activesync through wifi under this ip address and try to sync, and then it will get a normal ip address. I don't know if this is true with this device.
@closer what do you mean verify the link connection? The router shows the pda's ip address in it's connection manager, but for any computer or pda i don't know a way to "verify the link" other than look at it. There's no command for this. The router is set up to correctly assign dhcp as i have 2 computers and 2 xbox's connected through lines, and 2 computers through wifi. I know i can manualy set the ip, which i often do for everything but the laptop, but this is a pain in the ass to try and find out the gateway of every single router when i'm out in town. That's a workaround, not a fix.
@Black6spdz I was using Myipconfig and it would release and renew to just a different 169.254.x.x. I'm going to try vxipconfig when this happens again.
--Well, last night i got pissed and abandoned working on it. Low and behold when i wake up today it's working fine and has the correct ip address. That sucks, because now i have no idea what was wrong.
so...
-It's time to go connect to some other networks and see if it resolves correctly.
-Then i'm going to go through the 3 different radio versions and see how they affect it.
when I had that problem it was because my settings were set up incorrectly.. If i were to use gprs, it'd work fine. But wifi would not. So i had to make a seperate setting with generic entries and not set up proxies. then wifi would work. sort of a pain. but it would work...
I've been struggling with OpenVPN on my Vario III on T-Mobile and hope someone can throw me a bit of a lifeline.
I can connect to my OpenVPN (running on my WRT54GS router) via wifi but the problem is when I try over 3G. Even when I've specified the provider and ticked "exclusive", it manages to connect to my OpenVPN server but I get no further connectivity (to webpages etc).
As said, via wifi this config on my Kaiser works perfectly...
Code:
remote xxxxxx.homeip.net
port 22
dev tap
secret "\\Program files\\OpenVPN\\config\\secret.key"
proto tcp-client
resolv-retry infinite
nobind
comp-lzo
cipher AES-256-CBC
route gateway 192.168.xxx.xxx
redirect-gateway
dhcp-option DNS 192.168.xxx.xxx
but when tried via 3G it seems to have a problem with setting the routing..
Code:
Mon Oct 22 21:58:00 2007 ROUTE: route addition failed using CreateIpForwardEntry: The parameter is incorrect.
Just wondering if there is something either with the T-Mobile network or the Vario III which is specifically stopping me from using OpenVPN
Or are my settings misconfigured?
I've also attached a full copy of the log.
Thanks for any help you can give (Give generously)
CP
Sounds suspiciously like a NAT traversal or proxy issue to me. On the HSDPA network, there's a proxy in the picture. I don't believe that's the case for the Edge network. That could easily be the cause of the problem.
Surely once the connection has been established the NAT issue shouldn't be a problem?
TBH I thought the route addition problem was due to the software being unable to update the local routing table?
NAT traversal issues often manifest themselves as connections that look like they're established, then die immediately. The VPN participants have to know the actual IP addresses of the devices involved, and understand that NAT is happening. Proxies also need to play a role in that process since they're effectively "standing in" for your device. And they may be configured not to permit IPSec traffic at all.
What you've described sounds exactly like NAT traversal issues - the negotiation appears to go just fine, but the actual connection dies on the vine. Since the end points don't have the right data from the negotiation (actual valid addresses to build the tunnel around), the route they try to build is invalid and fails.
In your log, it's impossible to tell since the IP addresses have been all translated to xxx.xxx.xxx.xxx. But I suspect that the ones up until the "TCP connection established with..." message are all displaying valid public IP addresses, and somewhere very shortly after that they start displaying private RFC 1918 addresses.
Proxies + NAT +IPSec = small nightmares. This is one of the reasons SSL VPNs have gained significantly in popularity.
Try Hamachi vpn
https://secure.logmein.com/products/hamachi/vpn.asp
Surur
PerfAlbion said:
In your log, it's impossible to tell since the IP addresses have been all translated to xxx.xxx.xxx.xxx. But I suspect that the ones up until the "TCP connection established with..." message are all displaying valid public IP addresses, and somewhere very shortly after that they start displaying private RFC 1918 addresses.
Click to expand...
Click to collapse
You have PM
Quick update:
I've just connected my Laptop to the internet via my Kaiser using 3G.
Ran OpenVPN and it connected without a problem.
Technically this would suggest that I should be able to connect with my kaiser but theres either a problem with my config or a bug in the PPC openvpn software :S
I haven't tried on UDP yet which will be my next test....
Any ideas?
Blimey, I didn't know there was a PPC client! I'll try it to see if it works with my setup.
Well I can't even get it to talk to my server so won't be able to help !
Fire up the card in your laptop and take a look at the IP address assigned to your machine. Since it's a different service, they may not be passing you through the proxy that's in place for the Kaiser. If you've received a public address, then you're on a "different network" even though both are 3G services.
PerfAlbion said:
Fire up the card in your laptop and take a look at the IP address assigned to your machine. Since it's a different service, they may not be passing you through the proxy that's in place for the Kaiser. If you've received a public address, then you're on a "different network" even though both are 3G services.
Click to expand...
Click to collapse
?? When you connect a laptop via BT to the kaiser, (using internet sharing) it creates a NAT which the traffic is passed over through the 3G service. Essentially using the same service..
Unless you mean the "service" between the windows software & the PPC/WM software is different?
Plus how'd you mean fire up the card in my laptop?
Cheers for your help on this btw.
I'm assuming that the Laptop data service and the PDA data service are treated differently within the AT&T network. While the PDA passes through a proxy, I suspect the laptop does not.
When I say "fire up the laptop card," I mean establish a connection and look at your IP address (ipconfig from a command prompt will show it). It may be a different IP address range than the PDA receives (which you could see using VxIPConfig or VxUtils). Even if it's within the same range, it may be bypassing the proxy.
So while you're using essentially the same technology, I suspect the services are implemented very differently, and that's what we're trying to sort out.
I dont believe it!!!
I downloaded VM Net Brower checked what IP addresses were being assigned and connected successfully! Loaded up www.whatismyip.org and it came up with the proxy of my PC at home.
Unfortunately, my phone was running incredibly slow and thought it best to do a soft reset... afterwards no matter what I do, I can't connect. I just cant figure out why or replicate what I did
Argh.. this is getting to me now... next on the agenda is to try changing the port number from 22 to 8080 or 80 and see what happens.
Help!
I have a Netgear DG834T router as provided by Sky. I have one wired and two wireless connections running into it (let's call them WD, WL1 and WL2 respectively).
On the connections page I can see all of them under "attached devices"...but now I want to connect using my Kaiser (actually an O2 XDA Stellar)
What happens...
On the Kaiser, I get an IP address (assigned by DHCP) as normal - but can't access the internet - or at least, can only access it very rarely - http://www.google.com can't be found, but http://www.bbc.co.uk can. No idea why.
On the router, under "attached devices", not only can I NOT see the Kaiser, but WL1 and WL2 also disappear. WD remains visible. The router cannot ping the IP address of the Kaiser (timed out). If I disable WiFi on the Kaiser, then WL1 and WL2 are immediately visible again. Internet connection on WL1 and WL2 works, even when they are not visible.
I HAVE connected to this network before without any problems.
What the hooting heck is going on, and how do I fix it?
Thanks!
Time to troubleshoot! What happens with this phone on another wireless network. We need to determine if it's the phone or the network. Do you have any friends with a phone like this? Can you use their phone on your network? Do you have any ROMs flashed, has this phone ever been on the network without problems?
If the phone works on another router try looking for firmware updates for the router. Those things really do need to be updated often and it could have something to do with that.
Only have access to one network :-(. Might be a couple of weeks before I can access a hotel one or something like that.
Think next door neighbour has similar phone, but different provider...will try if he'll let me!
No ROMS flashed.
It connected fine when I first had it. As far as I know, I've changed nothing since then.
2 out of 4 answered...with an option on three...I'll get back to you as soon as I've beaten up my neighbour and stolen his phone...
Joke!
There should be somewhere you can go to test that wireless. I can walk outside the building I'm in and find one.
ChumleyEX said:
There should be somewhere you can go to test that wireless. I can walk outside the building I'm in and find one.
Click to expand...
Click to collapse
You = US, me = UK. We still think the biro is a recent invention...
Neighbour's phone on my network gives the exact same problem. I've also noticed that when I click "Renew IP" on the Kaiser it doesn't work...it gives me 0.0.0.0, but will occasionally flash up the correct IP address. It's alomst as if the connection is being lost and remade every few seconds. The status ist gives me is "associated to network"...is that different to "connected"?
I've been trying to solve this on my router, but none of the settings seem to make any difference.
Same here
I get the same with the router from sky.
Kaiser says I have an IP address, 192.168.0.5, but the it doesn't show up on the attached devices on the router.
What I find that works is hit renew IP maybe twice until you get a really wierd IP address like
169.254.*.**, actually not sure if I'm picking up another network, but for some reason I don't think I am.
I can then browse the web and sync via wifi.
Really pisses me of that it says that it has an IP address but doesn't connect.
1) Make sure you dont have a proxy set up on your wifi connection on your device.
2) The 169. address is your device getting an unauthorised IP address as the router did not receive the correct encryption key from the device.
3) You can check if its an encryption thing by simply logging in to the router (192.168.0.1 in your web browser on pc) and changing the settings to turn wpa off and testing it. The routers username and password are on the card - its something like "sky" and "admin"
Yeah I agree, there is something up with that router.
Grey Area said:
Neighbour's phone on my network gives the exact same problem. I've also noticed that when I click "Renew IP" on the Kaiser it doesn't work...it gives me 0.0.0.0, but will occasionally flash up the correct IP address. It's alomst as if the connection is being lost and remade every few seconds. The status ist gives me is "associated to network"...is that different to "connected"?
I've been trying to solve this on my router, but none of the settings seem to make any difference.
Click to expand...
Click to collapse
with my router.....i have to set the wifi power mode on my kaiser to "best performance", any other setting and i get that "associated to network" ****. been this way every since the hermes and the wizard.
unwired4 said:
1) Make sure you dont have a proxy set up on your wifi connection on your device.
2) The 169. address is your device getting an unauthorised IP address as the router did not receive the correct encryption key from the device.
3) You can check if its an encryption thing by simply logging in to the router (192.168.0.1 in your web browser on pc) and changing the settings to turn wpa off and testing it. The routers username and password are on the card - its something like "sky" and "admin"
Click to expand...
Click to collapse
No, proxy set-up as the device was bought unbranded in US.
Because there are issues with this router, encryption and media streaming devices, I have only restricted the mac addresses with no encryption.
Still don't know about the 169. ip address beacuse doesn't seem to come up as am ISP.
Now then, how wierd is this?
After all these issues and kind of giving up on it as a bad job, I also noticed that out on the road, my GPRS wasn't working either - TomTom couldn't connect to the "plus" traffic service.
I get on the phone to O2 who told me that my phone hadn't been "provisioned". After one false start where they didn't seem to do anything about it, I have just (literally) had them tell me to go to the O2 Operator settings and tell it to update the "O2 UK Post Pay_GPRS" and reboot.
GPRS now works. And magically, so does my WiFi - IP address negotiated and full access to internet and my router's setup page granted. Working like a charm again.
So - seems to me it's an account setting, and nothing to do with either me poor ol' router or me nice new phone.
For completeness, I was occasionally getting the 169 IP address too, so it sounds like we have EXACTLY the same problem - suggest you get onto your service provider ASAP.
Hi this is my first time on a site and I just wonder if anybody can solve my problem!
I,ve read a few posts and set my xda llI so that in connections my network card connects to work!Also have done all the rest and set it to internet just in case as well
My Isp in connections window is on the advanced tab and select networks on the network Management is set to My Isp.
my Wirles Lan Manager is status connected to network
My ssid is the one that all the house computors are set to,my mode is Infratructure and Tx is Auto.My channel is 6
my bssid is 00-18-2D etc etc.
My Mac is 00-09- etc ,etc.
My IP.169.254.168.73
signal quality is good
I,ve been onto the 192.168.0.1 website and added the mac address of the xda lli but when I try to get the internet on the xdalli to connect it justs says default page. I cannot seem to connect. is this normal or do I have to go through O2 to pay for another internet connection besides my home address one.Have I missed something out!Help would be greatly appreciated! thanks
Nilocsss
Hi,
Your IP of 169.x.x.x means that you are trying to use DHCP to get an ip address but haven't been supplied one by your router..
The ip addres of your router is 192.168.0.1, so it may be sensible to setup your router to allow a dynamic address range of 192.168.0.100 to 192.168.0.110 (say) - when anyone tries to connect using a dynamic address (using dhcp), they'll be given an address in this range.
So, initially check if DHCP is enabled.
Do you have a laptop that connects using a dynamic ip address (ie not static - ie not implicitly defined) - if so then DHCP _is_ already working and there's another problem.
If this is the case, I'd initially disable any kind of mac-filtering or security until you get a simple connection going..
Sorry, if this isn't too clear - I'm tired - what router are you using?
Kev
First hand it can depend on your router
I have had problems connecting with Virgin broadband routers for instance.
Have you tried connecting elsewhere?
Also what type of security do you have on your router?
One more thing to try
Check under the "Network Cards" settings when disconnected and select "the internet" from the drop down menu.
Hope this helps
clearing the way so that I understand correctly!
kevcal said:
Hi,
Your IP of 169.x.x.x means that you are trying to use DHCP to get an ip address but haven't been supplied one by your router..
The ip addres of your router is 192.168.0.1, so it may be sensible to setup your router to allow a dynamic address range of 192.168.0.100 to 192.168.0.110 (say) - when anyone tries to connect using a dynamic address (using dhcp), they'll be given an address in this range.
So, initially check if DHCP is enabled.
Do you have a laptop that connects using a dynamic ip address (ie not static - ie not implicitly defined) - if so then DHCP _is_ already working and there's another problem.
If this is the case, I'd initially disable any kind of mac-filtering or security until you get a simple connection going..
Sorry, if this isn't too clear - I'm tired - what router are you using?
Kev
Click to expand...
Click to collapse
Thanks Kev!
My router is a netgear dg834GT.I,ve looked at the range and the range for 192.168.0.1 actually goes from 192.168.0.2 upto 192.168.0.254 so the range should be there. how would I know if the router is DHCP, is there a way of seeing this? The filter would be set up where for the mac address?Is there a way of changing the isp on the phone so that its range is within the 192.168.0.1 range?the only security that I have is the routers own and the avg antivirus.would disabling the avg help!
thanks for your response!
voxshots said:
First hand it can depend on your router
I have had problems connecting with Virgin broadband routers for instance.
Have you tried connecting elsewhere?
Also what type of security do you have on your router?
One more thing to try
Check under the "Network Cards" settings when disconnected and select "the internet" from the drop down menu.
Hope this helps
Click to expand...
Click to collapse
thanks for replying ,my router is a netgear and the security is a wep key which I have disabled and i also tried the drop down menu "the internet" but still nothing! how would I find out on the phone what ethernet card it is running so that I can connect to that .
nilocsss said:
Thanks Kev!
My router is a netgear dg834GT.I,ve looked at the range and the range for 192.168.0.1 actually goes from 192.168.0.2 upto 192.168.0.254 so the range should be there. how would I know if the router is DHCP, is there a way of seeing this? The filter would be set up where for the mac address?Is there a way of changing the isp on the phone so that its range is within the 192.168.0.1 range?the only security that I have is the routers own and the avg antivirus.would disabling the avg help!
Click to expand...
Click to collapse
If you haven't set up mac filtering, then it won't be a problem.. if you have, then there should be an option to disable/remove any you've input - build security up from a working setup.
Have you (can you borrow) a laptop that you can setup wireless with a dynamic ip address and check that connects; if that's okay then the router is setup correctly.
So I the Alpine comes up with "connected to network" but the ip address is 169.x.x.x ..
This means that the Alpine has not been allocated a usable ip-address by the router for some reason and you'll get nowhere until this happens.
Your other PCs.. are they set to dynamic ip addresses - I guess so as you have no room for static addresses. You should probably check they're all dynamic as if (say) you've allocated a static ip address of 192.168.0.2 to one of them and then DHCP tries auto-allocating addresses, I guess there could be a conflict (don't know how clever dhcp is). Usually I would set the DHCP range to 192.168.0.100 -> 192.168.0.200 (allowing 100 different dynamic addresses).
Have you checked that authentication is set top 'Open' and Data Encryption 'Disabled' on the Alpine; and ensure you've disabled (temporarily) all router security..?
Kev
kevcal said:
If you haven't set up mac filtering, then it won't be a problem.. if you have, then there should be an option to disable/remove any you've input - build security up from a working setup.
Have you (can you borrow) a laptop that you can setup wireless with a dynamic ip address and check that connects; if that's okay then the router is setup correctly.
So I the Alpine comes up with "connected to network" but the ip address is 169.x.x.x ..
This means that the Alpine has not been allocated a usable ip-address by the router for some reason and you'll get nowhere until this happens.
Your other PCs.. are they set to dynamic ip addresses - I guess so as you have no room for static addresses. You should probably check they're all dynamic as if (say) you've allocated a static ip address of 192.168.0.2 to one of them and then DHCP tries auto-allocating addresses, I guess there could be a conflict (don't know how clever dhcp is). Usually I would set the DHCP range to 192.168.0.100 -> 192.168.0.200 (allowing 100 different dynamic addresses).
Have you checked that authentication is set top 'Open' and Data Encryption 'Disabled' on the Alpine; and ensure you've disabled (temporarily) all router security..?
Kev
Click to expand...
Click to collapse
Thanks kev for replying.
I have a hard wired lead to the router for one computor and 3 laptops connected by wifi and another computor connected by wifi.
the range or should I say the ip addresses are 192.168.0.3,192.168.0.4
upto 192.168.07.I,m at work at the moment but as soon as I get home tonight I'll set the wep key to disabled is there any other thing on the router that I need to do?
Can't think of anything else...
But at least you know DHCP is working if the other PCs are getting ip addresses okay.
And you know the wireless is working...
So it does look likely that it will be something to do with WEP/WPA encryption... (I guess you've got it setup at home), hence why the router isn't allocating you an ip-address.
If you can't get it going, it may be worthwhile doing some sceenshots of the router configuration pages (or config files)...
What I can tell you is that what you are doing looks correct and you have everything setup so you can go on the internet whilst at home using the Alpine. Mine uses the router whilst at home and GPRS whilst out.
nilocsss said:
Thanks Kev!
My router is a netgear dg834GT.I,ve looked at the range and the range for 192.168.0.1 actually goes from 192.168.0.2 upto 192.168.0.254 so the range should be there. how would I know if the router is DHCP, is there a way of seeing this? The filter would be set up where for the mac address?Is there a way of changing the isp on the phone so that its range is within the 192.168.0.1 range?the only security that I have is the routers own and the avg antivirus.would disabling the avg help!
Click to expand...
Click to collapse
The dg834GT is pretty much the one that Virgin use, like I said in my earlier post.
I have found these particular routers to be a problem (sometimes) with my Alpine.
You should try to update the firmware.
kevcal said:
Can't think of anything else...
But at least you know DHCP is working if the other PCs are getting ip addresses okay.
And you know the wireless is working...
So it does look likely that it will be something to do with WEP/WPA encryption... (I guess you've got it setup at home), hence why the router isn't allocating you an ip-address.
If you can't get it going, it may be worthwhile doing some sceenshots of the router configuration pages (or config files)...
What I can tell you is that what you are doing looks correct and you have everything setup so you can go on the internet whilst at home using the Alpine. Mine uses the router whilst at home and GPRS whilst out.
Click to expand...
Click to collapse
Well Done Kev!
It was the "open"on the phone and putting "open" on the router.I had to intiallely disable the wep key.then when I got connected,I reactivated the WEP key and I could not connect.So on the phone I unticked the automatically connect to my name of my router name and reput in my encryption key again and I was in and On line.Thanks to both of you(Kevcal and Voxshots) for helping me.Definately could not have done it without you Pair.I like the idea of using the screenshots so I,ll post a screenshot of all the settings on the phone and computor so that anybody else will be able to resolve there problems with all credits going to you people on the bottom!
Very happy to have helped and glad you sorted it out
Hey peeps. I'm on Andromeda 3 and I have been plagued lately by a very odd wireless issue that I cannot seem to fix. My symptoms will replicate no matter which wireless network that I connect to.
First off, I am an IT guy so I am very savvy. Secondly, I have been developing a theme on this phone so that may be related, but unlikely.
Some information on my setup:
In my home I have a Cisco Aironet 1200 802.11g access point that I am using for wifi behind a Cisco PIX 501 router.
At work we use Extreme Networks (enterprise grade) wireless access points with Juniper firewalls/routers/switches. I do not recall model numbers (irrelevant).
The problem:
Issue #1 - When I turn on wifi my signal bounces between 0 and 1 bar, and occasionally if the sun and moon are in the perfect positions in orbit, I will get 2 bars (wifi, not cell signal).
Issue #2 - I cannot for the life of me get a new IP address from DHCP on either network! My IP address on eth0 is stuck at 10.x.x.x but my home IP scheme is 192.168.0.x
My phone is set on DHCP, not static so I have no clue why it's binding to that address.
I have tried terminal emulator to release and renew but it doesnt work and I just end up getting an error that says DHCP timed out. Im not sure how far Android commands differ from Debian but I have tried (without success),
ifconfig eth0 down & up
netcfg eth0 down & up
dhclient (not recognized)
Other than that my host file is clogged up with a bunch of crap that I'm guessing by the ROM dev for disabling ad's.
I have even reflashed the ROM but that didn't help.
Can anyone suggest other things I can try to get that IP to unbind? The eth0 settings have to be stored away on some conf file somewhere right? I just dont where to look.
Thanks way in advance!
I have had issues with wi-fi connectivity with Andromeda 3 as well. I have found that for me, either rebooting the phone or using the power button menu to switch to airplane mode for a minute or so and then turning airplane mode off again fixes it for me - until the next time. Otherwise, I am sorry that I do not have better suggestions.