Related
Greetings...I'm trying to determine the MAC address of my HTC TP2's 3G radio. I am setting up a firewall rule to only alow a specific MAC address to pass for specific services. Any ideas as to how to determine the MAC address of the internal radio?
Thanks,
Chris
chrisb009 said:
Greetings...I'm trying to determine the MAC address of my HTC TP2's 3G radio. I am setting up a firewall rule to only alow a specific MAC address to pass for specific services. Any ideas as to how to determine the MAC address of the internal radio?
Thanks,
Chris
Click to expand...
Click to collapse
MAC of the 3g radio...? Certainly you mean the wlan radio.
When I enable wifi in WinMo, there's an "advanced" button at the bottom. Then choose wi-fi info, IP and MAC.
Response....
Not the WiFi radio...the 3g radio as I need access outside my network through a UTM. I guess the first question should have been, is there a MAC associated with the 3g radio?
Thanks,
Chris
chrisb009 said:
Not the WiFi radio...the 3g radio as I need access outside my network through a UTM. I guess the first question should have been, is there a MAC associated with the 3g radio?
Thanks,
Chris
Click to expand...
Click to collapse
Odd.
I'd guess there is, but I've never heard of anyone caring about it lol. IP probably wouldn't work so well either, what about hostname or smth else?
What if you lose your phone?
I'll see what I can dig up.
Edit - wait... if your packets are going thru a layer-3 router (which undoubtedly they are at some point) the MAC will be lost. So this won't work at all, even if you did find the MAC of your phone.
Response...
I couldn't find anything through searches....The IP would be of a dynamic nature so I couldn't use it however the thought about a host name is an idea. I'll have to inspect the packets to determine if a host name is present. On my inital inspection I captured a MAC however that MAC seems to be dynamic and did change a few times using one of two MAC'S thoughout the capture. Also...during the capture I captured IPv6 MAC's....not IPv4. I'm just wondering if the CDMA network assigns a dynamic MAC instead of using a hardware based MAC? I would find this highly unlikely however it could be a possibility.
Thanks,
Chris
chrisb009 said:
I couldn't find anything through searches....The IP would be of a dynamic nature so I couldn't use it however the thought about a host name is an idea. I'll have to inspect the packets to determine if a host name is present. On my inital inspection I captured a MAC however that MAC seems to be dynamic and did change a few times using one of two MAC'S thoughout the capture. Also...during the capture I captured IPv6 MAC's....not IPv4. I'm just wondering if the CDMA network assigns a dynamic MAC instead of using a hardware based MAC? I would find this highly unlikely however it could be a possibility.
Thanks,
Chris
Click to expand...
Click to collapse
Please read my edit about layer-3 routers. I'm having this same problem at work, in relation to sniffing VoIP RTP streams passively. When crossing a layer-3 router/switch, the MAC is lost in transit.
Response...
I believe I finally nailed down the actual MAC address. My packet monitor was set for the monitoring a different port on the switch.....should have been set for X1 instead of X0. I'll make the changes to the firewall and all should be good. This exercise is for a handheld utilizing a SIP client tied into my VoIP server....I only allow specific SIP clients to access my VoIP server....helps prevent hacking and unauthorized phone use.
Thanks,
Chris
Response...
I'll report back my findings after I make the configuration changes.....I am assuming this will work as I already have this in place for all SIP providers currently in use.
Thanks,
Chris
Findings....
Ok...one small detail I forgot.....is that MAC addresses change with each hop. With that being said.....the only way to "filter" incoming packets is to filter by IP address. I currently filter all SIP related protocols by carrier/provider IP address. Now this creates an issue due to the fact handhelds outside of the network will have dynamic IP's assigned by the cellular carrier. I'll have to continue to research this....I believe the only work around might be a VPN tunnel originating from the handheld into the network.
Thanks,
Chris
chrisb009 said:
Ok...one small detail I forgot.....is that MAC addresses change with each hop. With that being said.....the only way to "filter" incoming packets is to filter by IP address. I currently filter all SIP related protocols by carrier/provider IP address. Now this creates an issue due to the fact handhelds outside of the network will have dynamic IP's assigned by the cellular carrier. I'll have to continue to research this....I believe the only work around might be a VPN tunnel originating from the handheld into the network.
Thanks,
Chris
Click to expand...
Click to collapse
That's what I told you, twice now...
Actually..
You mentioned loosing the MAC address across a layer 3 router....the MAC address is lost across any router regardless of it's layer capability thus I will implement a different solution.
Chris
chrisb009 said:
You mentioned loosing the MAC address across a layer 3 router....the MAC address is lost across any router regardless of it's layer capability thus I will implement a different solution.
Chris
Click to expand...
Click to collapse
What router operates only at the layer-2 level? lol.
Guys I am in over my head here, I've watched way too many YouTube videos and guides and I still cant get this.
I have 2 galaxy nexus phones and I am trying to leave one at home running the app IP webcam and taking video. That phone will be connected to my WiFi network at home. Then I am trying to use my other nexus phone running Tinycam Monitor and connected to Verizon's 4g network, to connect to that phone and stream me live video from home.
Now basically I am looking for someone who has set this up correctly or who could help talk me through this.
I have set up a static ip address
I went to my linksys routers web address and tried to port-forward ports 8080 and 80 which are the ones I need
Its not working though and it keeps saying failed connection on the phone. I think I am just typing in something wrong or missing a step.
Can anyone try and help me through this?
Use your IP address and 100 instead of 80
Sent from my Galaxy Nexus using Tapatalk 2
vhgomez36 said:
Use your IP address and 100 instead of 80
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where are you talking about? You mean when I am forwarding the port on the linksys web interface? It asks me for the internal and external port (which I am typing in 8080) and then it asks for the "to ip address"
I am really unsure of what to put in the "To IP address" field. It shows my ip address but leaves blank the last few digits. Am I supposed to get that information from the phone from which I will be viewing the video?
bhawks23 said:
Where are you talking about? You mean when I am forwarding the port on the linksys web interface? It asks me for the internal and external port (which I am typing in 8080) and then it asks for the "to ip address"
Click to expand...
Click to collapse
Example.
vhgomez36 said:
Example.
Click to expand...
Click to collapse
Thanks for the reply, but I am still a little confused on what you are trying to say.
When I start up IP webcam it begins the video and it gives me an ip address and port number to connect to it. (this phone is on home wifi)
When I type those detail in tinycam monitor on my other phone (connected to verizon network), I add a new camera, set it to IP webcam for android, type the the previous ip hostname and port but it always fails to connect
I understand I need to portforward the port I am using to allow it to connect but I dont think I am doing that correctly
Make sure you port forward on your router to allow the connection.
Sent from my PG86100 using xda app-developers app
bhawks23 said:
Thanks for the reply, but I am still a little confused on what you are trying to say.
When I start up IP webcam it begins the video and it gives my an ip address and port number to connect to it. (this phone is on home wifi)
When I type those detail in tinycam monitor on my other phone (connected to verizon network), I add a new camera, set it to IP webcam for android, type the the previous ip hostname and port but it always fails to connect
I understand I need to portforward the port I am using to allow it to connect but I dont think I am doing that correctly
Click to expand...
Click to collapse
What happens if you turn on Wifi on your phone? Does it work then? You need the public domain IP address where your DVR is connected. I have the info. at home. I'll grab it tomorrow in case you still need the info.
handle223 said:
Make sure you port forward on your router to allow the connection.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yeah handle223 that is the step where I believe that I am messing up at. I followed a guide that said I need to port forward 8080 and 80 ports so I tried to do that. I'm just not sure what to enter into the "to ip address" field on linksys website. Am I supposed to put my computers ip or something from either of the phones?
vhgomez36 said:
What happens if you turn on Wifi on your phone? Does it work then? You need the public domain IP address where your DVR is connected. I have the info. at home. I'll grab it tomorrow in case you still need the info.
Click to expand...
Click to collapse
Yes it works fine when the phone is connected to wifi so I'm trying to get it to work while away from home on a mobile network. Yeah if you could help me out tomorrow that would be great. Thanks for the help already
bhawks23 said:
Yes it works fine when the phone is connected to wifi so I'm trying to get it to work while away from home on a mobile network. Yeah if you could help me out tomorrow that would be great. Thanks for the help already
Click to expand...
Click to collapse
There your problem...wrong IP address. I can help you more tomorrow when I get home.
vhgomez36 said:
There your problem...wrong IP address. I can help you more tomorrow when I get home.
Click to expand...
Click to collapse
Sounds good man thanks
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
To the OP, This is what you have to do. Everything is set up correctly on the phone is what it seems like but without a static IP from your internet service provider you're going to run into issues again the minute it changes it's IP address.
You'll have to connect to your router from the outside world (The internet) via the address that shows up in your router page under status. from there you connect to the port you specified with port forwarding and it'll connect to your phone from anywhere you're located outside of your home wifi.
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
Yes! That was extremely helpful and thanks for describing it in detail.
It took me about 20 minutes but now it is working perfectly and I am able to stream live video from wherever I wish. (It is working better than I thought on 4g also)
I had to create a static id for my home mobile phone and that was under DHCP settings like you said. That allowed me to properly open up the ports
Thanks for the help everyone and I'm glad I didn't give up because this is pretty sweet, and also I do understand the risks.
On a side note, what kind of strain would this put on my extra nexus if I was running IP webcam 24/7? (while plugged in of course) Guess I will find out
Deleted
Sent from my GT-I9000
mobile
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
Hi..
is it possible to do this with two mobile phones and without a static ip using mobile network only? somehow sending video signal to some free host using mobile internet?
like one phone stays at home connected to mobile internet as ip camera.. and with second I can watch the video from anywhere???
because when i create a local network with one and connect to it with other then all this works great...
OLD post i know but i figured id post in here just in case you guys are still around.
I have a S4 ( i don't think this matters)
But just like the OP. I have these 2 apps . The stream works fine in house (both on my wifi) but i cannot figure out how to get it connected off of wifi. the monitoring phone i am trying to use i turned the wifi off to use the 4glte but it just wont connect. I do have ports 8080 and 80 forwarded.
But what IP and port do i use the the connecting phones settings? the 192..... one is internal and works in the wifi but i tried that one and the external ip.... any ideas?
(the external IP i am using is the one from googling "whats my ip" inside the cams phone web browser so its the ip from the phone not pc)
cant find a way to change my ip address (wifi)
when you use a repeater that connects to your gateway, you cant connect through the default ip. I need to assign one
any way?
Using AOKP jb
Are you sure you've got your wifi network configured properly? Ive got a similar setup (main router upstairs that hands out IP addys, another router acting as repeater downstairs that I connect to) and I dont have any issues...
blackangst said:
Are you sure you've got your wifi network configured properly? Ive got a similar setup (main router upstairs that hands out IP addys, another router acting as repeater downstairs that I connect to) and I dont have any issues...
Click to expand...
Click to collapse
Well mine is the modem connected to a switch. An access point connectec to that and a repeater afterwards xD so yeah the ip address that the windows/android generates cannot connect to the gateway
There.might be a way to optimize this but am also curious about changing the ip address of my phone
Sent from my SGH-T989 using XDA Premium HD app
nabilbek said:
Well mine is the modem connected to a switch. An access point connectec to that and a repeater afterwards xD so yeah the ip address that the windows/android generates cannot connect to the gateway
There.might be a way to optimize this but am also curious about changing the ip address of my phone
Sent from my SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
Your modem is the DHCP server, so that is what should be assigning an IP, not windows or andriod. If you cant hit your gateway (which should be your modem BTW), changing your IP wont fix your issue. Youve got a disconnect somewhere.
That said, first you need the subnet of your DHCP pool. Something like 192.168.1.100-200. That info is in your router/modem. Then, just manually change the IP of your phone to an IP in that subnet.
blackangst said:
Your modem is the DHCP server, so that is what should be assigning an IP, not windows or andriod. If you cant hit your gateway (which should be your modem BTW), changing your IP wont fix your issue. Youve got a disconnect somewhere.
Click to expand...
Click to collapse
You are absolutely right. but I can hit my gateway. I mostly have a problem with the dhcp assigning wrong IPs and I still cant sort it out. But am assigning the clients manually to different IP in my subnet and everything works fine
That said, first you need the subnet of your DHCP pool. Something like 192.168.1.100-200. That info is in your router/modem. Then, just manually change the IP of your phone to an IP in that subnet.[/QUOTE]
THIS !! exactly xD how?
nabilbek said:
You are absolutely right. but I can hit my gateway. I mostly have a problem with the dhcp assigning wrong IPs and I still cant sort it out. But am assigning the clients manually to different IP in my subnet and everything works fine
That said, first you need the subnet of your DHCP pool. Something like 192.168.1.100-200. That info is in your router/modem. Then, just manually change the IP of your phone to an IP in that subnet.
Click to expand...
Click to collapse
THIS !! exactly xD how?[/QUOTE]
I would suspect that the repeater is handing out IP's as well. I believe what you are looking for is a repeater bridge which would connects wireless a to wireless a but b doesn't do any routing just passes it along to a. Here's a picture.
http://www.dd-wrt.com/wiki/index.php/Image:Repeater_Bridge.jpg
jrosetto said:
THIS !! exactly xD how?
Click to expand...
Click to collapse
I would suspect that the repeater is handing out IP's as well. I believe what you are looking for is a repeater bridge which would connects wireless a to wireless a but b doesn't do any routing just passes it along to a. Here's a picture.
http://www.dd-wrt.com/wiki/index.php/Image:Repeater_Bridge.jpg[/QUOTE]
Thanks jrosetto you saved me posting the same link
Sent from my SGH-T989 using xda app-developers app
Reserve a IP on your first router
Sent from my LG-LS855 using xda app-developers app
what I cant understand is, after I made adjustments. Any pc connects normally with an appropriate IP (DHCP)
Just my phone (havent tried another), although he gets a correct IP and connects but I never get access to the internet.
Bump !!
a sad one
long press the wifi SSID and modify ... glad I got all the help here -_-
I've just bought a used HTC Desire on eBay. I've tried to connect it to all of the three (!) wireless access points in my house, and it won't connect to any of them. It gets as far as trying to obtain an IP address, but then gives up after a couple of minutes and disconnects.
The routers/access points are:
- Draytek Vigor 2920n
- Buffalo WHR-G54S (running Tomato)
- Belkin Play Max N600 F7D4401
I've tried a factory reset on the phone and it made no difference. It's running stock (as far as I know) Android v2.2.2, and is locked to the Three network.
Can anyone suggest anything?
itm said:
I've just bought a used HTC Desire on eBay. I've tried to connect it to all of the three (!) wireless access points in my house, and it won't connect to any of them. It gets as far as trying to obtain an IP address, but then gives up after a couple of minutes and disconnects.
The routers/access points are:
- Draytek Vigor 2920n
- Buffalo WHR-G54S (running Tomato)
- Belkin Play Max N600 F7D4401
I've tried a factory reset on the phone and it made no difference. It's running stock (as far as I know) Android v2.2.2, and is locked to the Three network.
Can anyone suggest anything?
Click to expand...
Click to collapse
Myn does that sometimes, switch the wifi box off and on that works for me
Sent from my HTC Desire using xda app-developers app
sywats said:
Myn does that sometimes, switch the wifi box off and on that works for me
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
What, you mean all 3 of them??
sywats said:
Myn does that sometimes, switch the wifi box off and on that works for me
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Ok I just rebooted the Belkin router and it made no difference. Does anyone have any other ideas??
Maybe you should try to change the channel in router settings...example for channel 4 or 5.I have the same problem few months ago and for mw it works
terpi74 said:
Maybe you should try to change the channel in router settings...example for channel 4 or 5.I have the same problem few months ago and for mw it works
Click to expand...
Click to collapse
I already have a spread of channels - the 3 routers are on Channels 4,6 and 10. If the channel were the problem presumably the phone wouldn't see the access point in the first place??
itm said:
I already have a spread of channels - the 3 routers are on Channels 4,6 and 10. If the channel were the problem presumably the phone wouldn't see the access point in the first place??
Click to expand...
Click to collapse
Might b a problem with the phone,try connecting to a wifi hot spot c if that works
Sent from my HTC Desire using xda app-developers app
Hi itm,
Can you provide details such as what ROM, Recovery and Radio you are currently using on your HTC Desire? The post is framed around networking so I will be focusing on that. However, it is possible that the issue is with the smartphone. Can other wireless devices on your network connect to the router? Some ROMs may be missing critical drivers or perhaps it simply does not support the configuration you have on your router/wireless access point (WAP).
Also, being able to detect the wireless SSIDs being broadcast does not mean that the problem does not reside with the smartphone. If it cannot perform a handshake with the WAP then the problem could be because the HTC Desire does not support the configuration of the router.
Suggestions from most likely to most unlikely and the decision to change.
1. Human error when inputting passphase
Check your wireless passphrase is correct when inputting it in your smartphone or temporarily set it to a passphrase that you can easily type in to rule this out.
2. Passphrase is too long or uses unsupported characters.
Try using an alphanumeric passphrase and make sure it is only 63 characters or less.
3. Using a supported wireless encryption (router side).
Try setting the wireless authentication algorithm to WPA2, WPA and WEP and unencrypted (last resort).
As you are running the Tomato firmware, only set it to WPA2 and not with TKIP (unsupported in official build).
4. Problems with DHCP settings
Sometimes the smartphone may be unable to obtain an IP address from the DHCP Server, so setting a static IP addresses is a workaround.
Try setting a static IP address by going to the WIFI screen in Settings and long-press on your Wifi SSID (name), select modify and setup a static IP address. It should be within the IP Address subnet on your WAP, e.g. if your wlan0 is broadcasting on 192.168.12.0/255.255.255.255, setting a static IP Address 192.168.12.5 will work, but 192.168.1.5 will fail.
If there is no 'modify' option, press the Menu button and select Advanced. If that option does not exist, select Other Network and manually input your wireless settings.
5. Check the signal strength on your smartphone. A reasonably acceptable range is an RSSI of around 60 for wireless. Are you moving to areas with poor reception or where there is interference? For example, a running microwave or other electronic equipment running within the same wireless frequency will cause problems; 2.4GHz, 5 GHz.
6. If you are using wireless-N, that is 802.11n (full or draft), try using 802.11g or 802.11b instead.
7. Try disabling mobile data and attempt to connect via WIFI again.
8. If all else fails, I would be flashing another ROM. I ran into a similar problem once, and flashing another ROM allowed me to connect to my WAP. Turns out it was an issue with the kernel, though.
On a possibly related note, why not upgrade to Gingerbread? It has better power management and there is an official release by HTC if you are wary of developer ROMs.
So no to long ago I decided I would check the my phone's ip address and came across some questionable stuff. Here's my question:
1) How is it that my phone's ip address can change from being registered to tmobil on a 100.x.x.x address to sporadically being registered on DoD 30.x.x.x address?
2) How can it still happen even after I installed android firewall?
Conditions are always the same. I don't download any shady anything's. I pay for my rhapsody account and that's as far as my file sharing goes. I never have my WiFi enabled.
Any ideas or let me know what info you'd need to better access the situation. Thanks.
Without knowing what the allocated ip address really was, there it's really no way of knowing who the current owner of the block is, many blocks are relocated and may no longer be with who they used to be with, especially ipv4 blocks.
Not sure what android firewall would have to due with what the remote ip you are being allocated to with your dhcp network connection.
You should have no real control over what your network connection is given when you connect, other than possible controlling ipv6 vs ipv4.
krelvinaz said:
Without knowing what the allocated ip address really was, there it's really no way of knowing who the current owner of the block is, many blocks are relocated and may no longer be with who they used to be with, especially ipv4 blocks.
Not sure what android firewall would have to due with what the remote ip you are being allocated to with your dhcp network connection.
You should have no real control over what your network connection is given when you connect, other than possible controlling ipv6 vs ipv4.
Click to expand...
Click to collapse
So does this help? the firewall lets me know that even though I have set it up to refuse the block of addresses in which in resides, they're still connection to my phone.
Not sure I'm understanding you anyway. You telling me they temporarily relocate my up because they re no longer with.... yet after a few minutes , sometimes hours, I'm right back to the same ip?
What he was saying I believe is that the IPv4 allocations have been changing do to the available IP address blocks running thin. Companies were encouraged to give up IP blocks that they weren't actually using. In simple terms, a company might have originally owned a block of 100,000 IPs but never actually used more than 50,000. So they gave back a block of 50,000 so another company(s) could use them instead.
I don't believe the IP address' are static on a carrier. I'm not sure but each time you connect to the carrier network (no signal or airplane mode) you could be giving a fresh IP address. Also that is certainly the case if you are on a WiFi network. Unless you phone was set up as a static connection, you would likely receive a new lease on an IP address.
Found this which sounds similar to what you are seeing.
https://blog.wireshark.org/2010/04/t-mobile-clever-or-insane/
chipworkz said:
Found this which sounds similar to what you are seeing.
https://blog.wireshark.org/2010/04/t-mobile-clever-or-insane/
Click to expand...
Click to collapse
Exactly. Internal allocate IP's are normally Natt'd and not actuall the IP you show up on the Internet as.
When you connect to your provider for Network (not using WiFi), the provider (most likely T-Mobile) will allocate an IP to you via DHCP. That IP is what your phone uses to talk to the provider. It most likely is NOT what you look like when you hit the Internet though, that will most likely be a different IP because TMobile is most likely not providing you with an Internet routable IP.
So, right now, I turned off WiFi and I got the IP 100.143.28.84. When my phone touches the Internet though, it shows up as 206.29.182.169.
So at that point in time, my phone is using 100.143.28.84 to get to T-Mobile's network and the Internet sees my phone as 206.29.182.169. the outside IP is in TMobiles published block. And why the internal IP is also, it really doesn't matter what it is because that is not what your phone looks like when it gets to the Internet.
It is possible in your area there are different networks available internally that are given to you when you connect depending on where you physically are and what towers you are closest to. At some times you get the 100.x network and you might even get the same IP as before because of a lease of that IP to your device, but then you move to a slightly different area which is handing out 30.x addresses. All perfectly normal. and the internal IP's really don't matter much.
You can use a search of Whats My IP to see what the Internet thinks your IP is when you get there.
With some providers (Verizon for example) if you are using ipv6, you will always get a non-routable IP, meaning that if you figure out your Internet IP, an outside connection may not get back to you unless your device initiated the connection, but if you use ipv4, they gave you a temp IP that would end up with a routable IP back. You could then use that to connect to your phone using something like VNC or other service. Now days, that is much more likely not the case unless you are paying for that special IP service. I don't know if Tmobile offers that type of service, but Verizon did at least a year or two ago.
In anycase, you firewall shouldn't matter unless you don't want to access your providers network.
In lamens terms I think he's talking about an internel subnet mask
chipworkz said:
Found this which sounds similar to what you are seeing.
https://blog.wireshark.org/2010/04/t-mobile-clever-or-insane/
Click to expand...
Click to collapse
That was a very interesting article. If the author's theory is correct, T-mobile was playing some cute and dangerous IP games in 2010.