dick white
Premium
join:2000-03-24
Annandale, VA
 ·Verizon FIOS
| reply to RobNyc
Re: [modem/router] Static IP ?
No. MyIP.com will tell you the public address Verizon has assigned to you at this moment. If you are paying them business rates for a static IP, then MyIP will confirm that the static IP you think you have is indeed the one your router is using to requesting web pages. You should not plug your router configuration to use a static IP unless you own the permanent rights to that public IP.
Verizon residential service uses dynamic IPs. They will issue you what you need when you need it. You have only temporary rights to it for only as long as you are actually using it. If you permanently plug your router with an address that is only temporarily yours, all hell will break loose when that address is reassigned to another user and now you are trying to convince the internet that both of you are the proper recipients of web page requests that are to be sent to that particular address.
The 192.168.x.x set of addresses is a completely unrelated set of addresses that apply only between your router and your computer system(s). Normally, your router will use an internal DHCP server to allocate those internal addresses as client systems turn on and off. It reserves 192.168.1.1 for itself, and then starts giving out addresses in sequence as needed, keeping them unique to each separate inside system, and recirculating the list as inside systems turn off.
The router performs what is called Network Address Translation (NAT) to translate the page request from internal system 192.168.1.101 (let's say) to the public address of aaa.bbb.ccc.ddd that was temporarily issued by Verizon to you. That packet goes out to where ever and the web page comes back to aaa.bbb.ccc.ddd and your router, knowing that inside system 192.168.1.101 has a pending request for something from that web page, it sends the page out through the network jack that it knows has inside system 192.168.1.101 on the other end of the cable.
If somebody on the outside sends an unsolicited request to aaa.bbb.ccc.ddd (your public address), your router will ignore it because it knows nobody inside asked for it. That's what a firewall is.
If you want to expose any particular inside system to outside requests, you have to assign it a static inside address in the 192.168.1.x range in a manner that will not conflict with any addresses that the router will be attempting to assign to other inside systems through its DHCP server. Typically that is done by configuring the router to 192.168.1.1 for itself and then setting the DHCP range to 192.168.1.100 and up. Thus inside addresses of 192.168.1.2 through 192.168.1.99 will never be assigned automatically by the router and you can manually assign anything you want to those addresses. For discussion, let's now say you have plugged your computer's network properties to use static internal address 192.168.1.75. In order for it to be exposed to the internet with unrestricted translation and pass-through of unsolicited external requests, you will need to configure your router with address 192.168.1.75 in the DMZ. Now anything coming in to aaa.bbb.ccc.ddd public address that was not previously asked for by a known inside system will be sent to ...75 without question. Now your friend should be able to SSH into that system - assuming that Verizon is not blocking the specific inbound ports that your friend's session might use.
dw |
|
mc_365
join:2004-07-29
Brooklyn, NY | Some areas of Verizons network do not use dynamic IP addresses. In some parts of the ex-GTE areas the IPs assinged are static. But Verizon is coverting to all poppe. |
|
JohnA
Premium
join:2003-09-16
Pittsburgh, PA
| said by mc_365  :Some areas of Verizons network do not use dynamic IP addresses. In some parts of the ex-GTE areas the IPs assinged are static. But Verizon is coverting to all poppe. You've got your terminology mixed up. All residential accounts use dynamic IPs, wether they are DHCP or PPPoE. Only business accounts use static IPs. |
|
