we have private IP address on WAN port, no connection through Router?

we have private IP address on WAN port, no connection through Router?
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
we have private IP address on WAN port, no connection through Router? GS 10-06-2005
Posted by Bill M. on October 6, 2005, 6:53 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller

>
>> This is ISP giving service to home, they come home and hardcode this
>> static IP address into PC (192.168.25.234), instaed of hardcode into
>> PC, we asked them to configure Router WAN port, so that we can connect
>> two PC's to Internet, both PC's connected to Router LAN ports, this is
>> available in Asia, they won't give public IP addres to home, instaed
>> they run RJ45 cable to home and hardcode this private IP address to PC,
>> if we want both PC's, then they are suggesting us to take 2 cables for
>> both PC's. I bought this router and connected, will it work in private
>> IP address case?.
>
>No.

Just curious, Tom. Why wouldn't it work?

--
Bill


Pure Networks
Posted by $Bill on October 6, 2005, 11:58 am
If you were  Registered and logged in, you could reply and use other advanced thread options


Bill M. wrote:
> On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller
>
>>
>>> This is ISP giving service to home, they come home and hardcode this
>>> static IP address into PC (192.168.25.234), instaed of hardcode into
>>> PC, we asked them to configure Router WAN port, so that we can connect
>>> two PC's to Internet, both PC's connected to Router LAN ports, this is
>>> available in Asia, they won't give public IP addres to home, instaed
>>> they run RJ45 cable to home and hardcode this private IP address to PC,
>>> if we want both PC's, then they are suggesting us to take 2 cables for
>>> both PC's. I bought this router and connected, will it work in private
>>> IP address case?.
>> No.
>
> Just curious, Tom. Why wouldn't it work?

Especially since we don't even know what kind of router it is.



Posted by Tom Stiller on October 6, 2005, 4:13 pm
If you were  Registered and logged in, you could reply and use other advanced thread options



> On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller
>
> >
> >> This is ISP giving service to home, they come home and hardcode this
> >> static IP address into PC (192.168.25.234), instaed of hardcode into
> >> PC, we asked them to configure Router WAN port, so that we can connect
> >> two PC's to Internet, both PC's connected to Router LAN ports, this is
> >> available in Asia, they won't give public IP addres to home, instaed
> >> they run RJ45 cable to home and hardcode this private IP address to PC,
> >> if we want both PC's, then they are suggesting us to take 2 cables for
> >> both PC's. I bought this router and connected, will it work in private
> >> IP address case?.
> >
> >No.
>
> Just curious, Tom. Why wouldn't it work?

IP addresses in the ranges:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
are set aside for use as private IP addresses and are not routed. They
are assigned by small routers providing Network Address Translation
(NAT) functions.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF


Posted by Warren on October 6, 2005, 1:41 pm
If you were  Registered and logged in, you could reply and use other advanced thread options


Tom Stiller wrote:
>> Just curious, Tom. Why wouldn't it work?
>
> IP addresses in the ranges:
> 10.0.0.0 - 10.255.255.255 (10/8 prefix)
> 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
> 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
> are set aside for use as private IP addresses and are not routed. They
> are assigned by small routers providing Network Address Translation
> (NAT) functions.

Actually, they *are* just as routable as any valid IP address. However, they
are not used for Internet purposes. The border routers on any private
network will not route traffic for these ranges off the private network.
Routers within the network can route traffic for these addresses.

For example, most cable ISP's use Class A private addresses (10.x.x.x) for
DOCSIS cable modems on their network. AT&T used Class B private addressed
(172.16.x.x) on their private portion of the backbone, as do many other
private networks of considerable size. It's not unusual to see addresses in
that range as the last few hops on traceroutes once the traffic reaches the
server's ISP's private network.

And they aren't just "assigned by small routers". IP addresses are either
manually assigned or assigned by DHCP servers. Most home "broadband routers"
are NAT routers, switches and DHCP servers packaged in one box, but it's the
DHCP server -- not the router -- that assigns the IP address.

And while we're at it, the fact that they're set aside for private range
address is irrelevant. The OP is trying to set-up a private LAN, which is
exactly the purpose that these addresses were meant to serve.

I would, however, suggest not using the Class C range if the ISP is already
using the Class C private IP address range. If the router being used on the
home LAN permits, I would try setting it to the Class B private IP address
range.

However, as someone else pointed out, this discussion is actually off-topic
as it does not involve a cablemodem or cablemodem service. It would be
better addressed in a networking group.

--
Warren H.

==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.
Shop for gifts for fans of "The Simpsons":
http://www.holzemville.com/mall/simpsons






Posted by Tom Stiller on October 6, 2005, 4:53 pm
If you were  Registered and logged in, you could reply and use other advanced thread options

> Tom Stiller wrote:
> >> Just curious, Tom. Why wouldn't it work?
> >
> > IP addresses in the ranges:
> > 10.0.0.0 - 10.255.255.255 (10/8 prefix)
> > 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
> > 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
> > are set aside for use as private IP addresses and are not routed. They
> > are assigned by small routers providing Network Address Translation
> > (NAT) functions.
>
> Actually, they *are* just as routable as any valid IP address. However, they
> are not used for Internet purposes. The border routers on any private
> network will not route traffic for these ranges off the private network.
> Routers within the network can route traffic for these addresses.
>
> For example, most cable ISP's use Class A private addresses (10.x.x.x) for
> DOCSIS cable modems on their network. AT&T used Class B private addressed
> (172.16.x.x) on their private portion of the backbone, as do many other
> private networks of considerable size. It's not unusual to see addresses in
> that range as the last few hops on traceroutes once the traffic reaches the
> server's ISP's private network.
>
> And they aren't just "assigned by small routers". IP addresses are either
> manually assigned or assigned by DHCP servers. Most home "broadband routers"
> are NAT routers, switches and DHCP servers packaged in one box, but it's the
> DHCP server -- not the router -- that assigns the IP address.
>
> And while we're at it, the fact that they're set aside for private range
> address is irrelevant. The OP is trying to set-up a private LAN, which is
> exactly the purpose that these addresses were meant to serve.
>
> I would, however, suggest not using the Class C range if the ISP is already
> using the Class C private IP address range. If the router being used on the
> home LAN permits, I would try setting it to the Class B private IP address
> range.
>
> However, as someone else pointed out, this discussion is actually off-topic
> as it does not involve a cablemodem or cablemodem service. It would be
> better addressed in a networking group.

Thanks for the correction.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF

Similar ThreadsPosted
How can I access my Router which is on private ip address from ISP October 29, 2005, 9:09 am
Router port light is always on February 15, 2005, 3:50 pm
Router Timed port access? May 2, 2005, 3:13 pm
The ISP giving leased line to home(cat5), wants to configure static private IP addr, can I use Router?. October 1, 2005, 5:14 am
5-port switch had Auto-uplink and Auto-detection, can I connect any port on N/W side? February 12, 2005, 10:13 pm
Linksys Router - No IP Address from Adelphia July 10, 2005, 5:50 am
Can I connect switch port of Router to uplink on another switch to add more PC's May 21, 2005, 9:55 pm
ID IP Address of Cable Modem Hooked to Linksys Router September 24, 2006, 10:54 am
No Internet Connection Between Router and Modem August 21, 2007, 6:44 pm
My router is causing my cable connection to drop April 23, 2006, 1:48 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map