| Author |
Message |
GS
Guest
|
 Posted:
Thu Oct 06, 2005 4:12 pm Post subject:
we have private IP address on WAN port, no connection throug |
|
|
We got leased line (RJ45 cable directly to home), we have 2 PC's,
connected through Router, the WAM IP address is: 192.168.25.234 and LAN
side it is using 192.168.1 subnet (192.168.1.2 and 192.168.1.3), once
enter all WAN port details, th esetup wizard not finishing, and we are
not getting internet through Router. If we connect the cable directly
to PC and configure that WAN IP address (192.168.25.234), it works, but
one PC at a time, I tried both PC's, it works individually, if we
connect through Router, nope. Any suggestions, thanks in advance. |
|
| Back to top |
|
 |
$Bill
Guest
|
| Posted:
Thu Oct 06, 2005 4:20 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
GS wrote:
| Quote: | We got leased line (RJ45 cable directly to home), we have 2 PC's,
connected through Router, the WAM IP address is: 192.168.25.234 and LAN
side it is using 192.168.1 subnet (192.168.1.2 and 192.168.1.3), once
enter all WAN port details, th esetup wizard not finishing, and we are
not getting internet through Router. If we connect the cable directly
to PC and configure that WAN IP address (192.168.25.234), it works, but
one PC at a time, I tried both PC's, it works individually, if we
connect through Router, nope. Any suggestions, thanks in advance.
|
You're going to have to post your router type and whether you can address
it's config/status pages or not. Did you follow the router setup instructions ?
In most cases just plugging it in and powering everything down and powering
everything back up starting at the modem end and waiting for each device to
come all the way up should get you going. |
|
| Back to top |
|
|
Tom Stiller
Guest
|
| Posted:
Thu Oct 06, 2005 4:20 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
In article <1128597158.022835.182060@z14g2000cwz.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
| Quote: | We got leased line (RJ45 cable directly to home), we have 2 PC's,
connected through Router, the WAM IP address is: 192.168.25.234 and LAN
side it is using 192.168.1 subnet (192.168.1.2 and 192.168.1.3), once
enter all WAN port details, th esetup wizard not finishing, and we are
not getting internet through Router. If we connect the cable directly
to PC and configure that WAN IP address (192.168.25.234), it works, but
one PC at a time, I tried both PC's, it works individually, if we
connect through Router, nope. Any suggestions, thanks in advance.
|
Judging from the WAN IP address, 192.168.25.234, your line is already
connected to a NAT router. Normally, additional IP addresses would be
available from such a router and one would attach a switch or, less
preferably, a hub to such a line to distribute additional IP addresses
assigned by it.
Who supplies this "leased line" and what are their terms and conditions
regarding multiple computers connected to it?
--
Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF |
|
| Back to top |
|
|
riggor99999
Guest
|
| Posted:
Thu Oct 06, 2005 4:20 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
"Tom Stiller" <tomstiller@comcast.net> wrote in message
news:tomstiller-DC1E19.08094006102005@comcast.dca.giganews.com...
| Quote: | In article <1128597158.022835.182060@z14g2000cwz.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
Judging from the WAN IP address, 192.168.25.234, your line is already
connected to a NAT router. Normally, additional IP addresses would be
available from such a router and one would attach a switch or, less
preferably, a hub to such a line to distribute additional IP addresses
assigned by it.
Who supplies this "leased line" and what are their terms and conditions
regarding multiple computers connected to it?
|
I agree - you may have to put the router in router mode versus gateway mode |
|
| Back to top |
|
|
GS
Guest
|
| Posted:
Thu Oct 06, 2005 4:20 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
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?. |
|
| Back to top |
|
|
Walter Roberson
Guest
|
| Posted:
Thu Oct 06, 2005 8:56 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
In article <9JydncsWxrd2FtjeRVn-vQ@comcast.com>,
Warren <wholzem@hotmail.com> wrote:
| Quote: | Tom Stiller wrote:
are set aside for use as private IP addresses and are not routed.
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.
|
Small amendment:
According to the RFCs, the border routers "must not"
route traffic in the reserved ranges off of the private network.
However, in practice, a number of them do permit the traffic.
Also common is that networks which are not intended to use one of the
RFC1918 private ranges internally might not filter out traffic
sourced from that range... which is fine until someone starts forging
traffic in the range... or until some NT system learns a remote private
IP through WINS and starts trying to send it it...
--
When Love is gone, there's always Justice.
When Justice is gone, there's always Force.
When Force is gone, there's always Mom. -- Laurie Anderson |
|
| Back to top |
|
|
David H. Lipman
Guest
|
| Posted:
Thu Oct 06, 2005 9:58 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
From: "GS" <globalswamy@hotmail.com>
| We got leased line (RJ45 cable directly to home), we have 2 PC's,
| connected through Router, the WAM IP address is: 192.168.25.234 and LAN
| side it is using 192.168.1 subnet (192.168.1.2 and 192.168.1.3), once
| enter all WAN port details, th esetup wizard not finishing, and we are
| not getting internet through Router. If we connect the cable directly
| to PC and configure that WAN IP address (192.168.25.234), it works, but
| one PC at a time, I tried both PC's, it works individually, if we
| connect through Router, nope. Any suggestions, thanks in advance.
You posted something similar 5 days ago.
I'm still trying to figure out why thiese were posted to a Cable Modem News Group if you are
NOT subscribing or getting a subscription for Cable Internet access. Such a post as this is
Off Topic and one should always post On Topic.
I suggest; alt.comp.networking.routers
--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm |
|
| Back to top |
|
|
Tom Stiller
Guest
|
| Posted:
Thu Oct 06, 2005 10:55 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
In article <1128614679.664238.268350@g14g2000cwa.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
| Quote: | 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.
--
Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3
7BDA 71ED 6496 99C0 C7CF |
|
| Back to top |
|
|
Bill M.
Guest
|
| Posted:
Thu Oct 06, 2005 11:53 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller
<tomstiller@comcast.net> wrote:
| Quote: | In article <1128614679.664238.268350@g14g2000cwa.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
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 |
|
| Back to top |
|
|
$Bill
Guest
|
| Posted:
Thu Oct 06, 2005 11:58 pm Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
Bill M. wrote:
| Quote: | On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller
tomstiller@comcast.net> wrote:
In article <1128614679.664238.268350@g14g2000cwa.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
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. |
|
| Back to top |
|
|
Tom Stiller
Guest
|
| Posted:
Fri Oct 07, 2005 1:13 am Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
In article <2ksak15a81lkk64ll38gfdn0g6tl244cul@4ax.com>,
Bill M. <wbillups@hotmail.com> wrote:
| Quote: | On Thu, 06 Oct 2005 13:55:15 -0400, Tom Stiller
tomstiller@comcast.net> wrote:
In article <1128614679.664238.268350@g14g2000cwa.googlegroups.com>,
"GS" <globalswamy@hotmail.com> wrote:
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 |
|
| Back to top |
|
|
Warren
Guest
|
| Posted:
Fri Oct 07, 2005 1:41 am Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
Tom Stiller wrote:
| Quote: | 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 |
|
| Back to top |
|
|
Tom Stiller
Guest
|
| Posted:
Fri Oct 07, 2005 1:53 am Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
In article <9JydncsWxrd2FtjeRVn-vQ@comcast.com>,
"Warren" <wholzem@hotmail.com> wrote:
| Quote: | 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 |
|
| Back to top |
|
|
David Ross
Guest
|
| Posted:
Fri Oct 07, 2005 4:32 am Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
Walter Roberson wrote:
| Quote: | In article <9JydncsWxrd2FtjeRVn-vQ@comcast.com>,
Warren <wholzem@hotmail.com> wrote:
Tom Stiller wrote:
are set aside for use as private IP addresses and are not routed.
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.
Small amendment:
According to the RFCs, the border routers "must not"
route traffic in the reserved ranges off of the private network.
However, in practice, a number of them do permit the traffic.
|
Yes but that's really a configuration issue not a hardware one. I setup
routers all the time inside larger companies where I have a
192.168.x.zzz handing out addresses with a WAN on THAT router set to
192.168.y.zzz. Nothing wrong with this. But some (many?) older (maybe
still) consumer routers will not handle this. Netgear does. I think
current Linksys units do.
As to why I do this. :) Various reasons. |
|
| Back to top |
|
|
James Knott
Guest
|
| Posted:
Fri Oct 07, 2005 6:13 am Post subject:
Re: we have private IP address on WAN port, no connection th |
|
|
David Ross wrote:
| Quote: |
Yes but that's really a configuration issue not a hardware one. I setup
routers all the time inside larger companies where I have a
192.168.x.zzz handing out addresses with a WAN on THAT router set to
192.168.y.zzz. Nothing wrong with this. But some (many?) older (maybe
still) consumer routers will not handle this. Netgear does. I think
current Linksys units do.
As to why I do this. :) Various reasons.
|
FWIW, my Linux firewall has no problem routing 10.x.x.x and 192.168.x.x
addresses via VPN. In fact, it has two 192.168.x.x NICs as well as the
10.x.x.x VPN, in addition to my "real" IP address, assigned by my ISP. The
computer at the other end of the VPN is on yet a third 192.168.x.x subnet. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in