2Wire 1000HG - help using internal static address as port forwarding destintation

I am trying to help a client. Basic problem is that with the SBC
provided 2wire ADSL/router he has, I seem unable to use a static
assigned IP address as a port forwarding destination, as it does not
"appear" on the device list the "Home network" page, as opposed to
devices that are DHCP (dynamically) assigned an address.

2Wire quickly responsed to my email, but frankly, their answer sounds a
bit odd. I've requested followup, but haven't had any (yet.) This is
an important client who is a distance from my home, and I can't afford
to be "experimenting" as I don't wan't to errode his confidence in me.
Unfortunately, I don't have the same equipment to test.

Below is my conversation to date with 2Wire -- is there a kind soul who
can help me verify their "solution"?

Thanks,

d.

===================

{MY ORIGINAL MESSAGE}

I'm having trouble configuring my 1800HG to use a device using a static
address as a port forwarding destination.

Internally, I can reach the static address device without a problem.

THe problem seems to get the device to appear in the list of devices on
the "Home Network" page. Without this, the device doesn't appear in the
list of devices "Choose the computer that will host applications" on
the "Edit firwall setttings" page.


Is there a way to get a static address device to appear on this list,
so I can complete the port forwading instructions?

THank you

d.
===================

{REPLY}

Dear D,

Thank you for contacting 2Wire Customer Support. The following is
intended to answer your inquiry:

Try these steps.

Assign the device an IP address between 192.168.1.33 and 192.168.1.62.
Turn the device off then back on to renew its address with your Home
Gateway. You should be now able to see that device in the Home Network
list to configure it.


If this response has not answered your question or resolved your issue
you may visit our support Website at http://support.2wire.com or reply
to this email.

Thank You,
John C.
2Wire Customer Support
http://www.2Wire.com


=======================

{{My followup}}

Thank you for your prompt response.

Because this setup is not near my home (this is for a client), I'd
appreciate if you would explain the special significance of the address
range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
documentation. Is there a special (undoumented) error or
limitation requireing the use of that range only?

Thank you.

d.

Maybe this will help
http://www.portforward.com/english/r...hg/default.htm

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
>I am trying to help a client. Basic problem is that with the SBC
> provided 2wire ADSL/router he has, I seem unable to use a static
> assigned IP address as a port forwarding destination, as it does not
> "appear" on the device list the "Home network" page, as opposed to
> devices that are DHCP (dynamically) assigned an address.
>
> 2Wire quickly responsed to my email, but frankly, their answer sounds a
> bit odd. I've requested followup, but haven't had any (yet.) This is
> an important client who is a distance from my home, and I can't afford
> to be "experimenting" as I don't wan't to errode his confidence in me.
> Unfortunately, I don't have the same equipment to test.
>
> Below is my conversation to date with 2Wire -- is there a kind soul who
> can help me verify their "solution"?
>
> Thanks,
>
> d.
>
> ===================
>
> {MY ORIGINAL MESSAGE}
>
> I'm having trouble configuring my 1800HG to use a device using a static
> address as a port forwarding destination.
>
> Internally, I can reach the static address device without a problem.
>
> THe problem seems to get the device to appear in the list of devices on
> the "Home Network" page. Without this, the device doesn't appear in the
> list of devices "Choose the computer that will host applications" on
> the "Edit firwall setttings" page.
>
>
> Is there a way to get a static address device to appear on this list,
> so I can complete the port forwading instructions?
>
> THank you
>
> d.
> ===================
>
> {REPLY}
>
> Dear D,
>
> Thank you for contacting 2Wire Customer Support. The following is
> intended to answer your inquiry:
>
> Try these steps.
>
> Assign the device an IP address between 192.168.1.33 and 192.168.1.62.
> Turn the device off then back on to renew its address with your Home
> Gateway. You should be now able to see that device in the Home Network
> list to configure it.
>
>
> If this response has not answered your question or resolved your issue
> you may visit our support Website at http://support.2wire.com or reply
> to this email.
>
> Thank You,
> John C.
> 2Wire Customer Support
> http://www.2Wire.com
>
>
> =======================
>
> {{My followup}}
>
> Thank you for your prompt response.
>
> Because this setup is not near my home (this is for a client), I'd
> appreciate if you would explain the special significance of the address
> range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
> documentation. Is there a special (undoumented) error or
> limitation requireing the use of that range only?
>
> Thank you.
>
> d.
>

Thanks, but I add already had that info, and it doesn't address how to
get a static device recognized, so port fortwarding to the device can
be set up.

After i sent a second message to the tech support questioning the
accuracy of the first response, I got a message back stating that
"Sorry, its not possible to port forward to a static address."

I'm still betting there is a "hidden" method, but oh well.


Darn!


xyz wrote:
> Maybe this will help
> http://www.portforward.com/english/r...hg/default.htm
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> >I am trying to help a client. Basic problem is that with the SBC
> > provided 2wire ADSL/router he has, I seem unable to use a static
> > assigned IP address as a port forwarding destination, as it does not
> > "appear" on the device list the "Home network" page, as opposed to
> > devices that are DHCP (dynamically) assigned an address.
> >
> > 2Wire quickly responsed to my email, but frankly, their answer sounds a
> > bit odd. I've requested followup, but haven't had any (yet.) This is
> > an important client who is a distance from my home, and I can't afford
> > to be "experimenting" as I don't wan't to errode his confidence in me.
> > Unfortunately, I don't have the same equipment to test.
> >
> > Below is my conversation to date with 2Wire -- is there a kind soul who
> > can help me verify their "solution"?
> >
> > Thanks,
> >
> > d.
> >
> > ===================
> >
> > {MY ORIGINAL MESSAGE}
> >
> > I'm having trouble configuring my 1800HG to use a device using a static
> > address as a port forwarding destination.
> >
> > Internally, I can reach the static address device without a problem.
> >
> > THe problem seems to get the device to appear in the list of devices on
> > the "Home Network" page. Without this, the device doesn't appear in the
> > list of devices "Choose the computer that will host applications" on
> > the "Edit firwall setttings" page.
> >
> >
> > Is there a way to get a static address device to appear on this list,
> > so I can complete the port forwading instructions?
> >
> > THank you
> >
> > d.
> > ===================
> >
> > {REPLY}
> >
> > Dear D,
> >
> > Thank you for contacting 2Wire Customer Support. The following is
> > intended to answer your inquiry:
> >
> > Try these steps.
> >
> > Assign the device an IP address between 192.168.1.33 and 192.168.1.62.
> > Turn the device off then back on to renew its address with your Home
> > Gateway. You should be now able to see that device in the Home Network
> > list to configure it.
> >
> >
> > If this response has not answered your question or resolved your issue
> > you may visit our support Website at http://support.2wire.com or reply
> > to this email.
> >
> > Thank You,
> > John C.
> > 2Wire Customer Support
> > http://www.2Wire.com
> >
> >
> > =======================
> >
> > {{My followup}}
> >
> > Thank you for your prompt response.
> >
> > Because this setup is not near my home (this is for a client), I'd
> > appreciate if you would explain the special significance of the address
> > range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
> > documentation. Is there a special (undoumented) error or
> > limitation requireing the use of that range only?
> >
> > Thank you.
> >
> > d.
> >

On 15 Aug 2006 13:34:52 -0700, (E-Mail Removed) <(E-Mail Removed)> wrote:
> Thanks, but I add already had that info, and it doesn't address how to
> get a static device recognized, so port fortwarding to the device can
> be set up.
>
> After i sent a second message to the tech support questioning the
> accuracy of the first response, I got a message back stating that
> "Sorry, its not possible to port forward to a static address."
>
> I'm still betting there is a "hidden" method, but oh well.
>
>
> Darn!

I have the newer 2700HG-B and seems to automatically recognize static IPs
on its LAN. For example with a DHCP assigned range of .64-.253 and 2Wire
LAN IP of .254 it recognized my Linux box with a static .1 IP. Although,
Linux does not have samba running for a netbios (Windows networking) name,
so I manually assigned its hostname in the 2Wire's Home Network summary.
But for security through obscurity I am running a 172.16.0.0/255.255.255.0
LAN, so the 2Wire is 172.16.0.254. I had no trouble setting the 2Wire to
forward SSH and Web Server ports to it.

Is your box with static IP able to access the internet (proper gateway and
DNS manually set)?

However, if you have static IP plan from your DSL provider and are trying
to do something with multiple public IP's, that is completely different.

On 08/13/06 13:51, (E-Mail Removed) wrote:
> I am trying to help a client. Basic problem is that with the SBC
> provided 2wire ADSL/router he has, I seem unable to use a static
> assigned IP address as a port forwarding destination, as it does not
> "appear" on the device list the "Home network" page, as opposed to
> devices that are DHCP (dynamically) assigned an address.
>
> 2Wire quickly responsed to my email, but frankly, their answer sounds a
> bit odd. I've requested followup, but haven't had any (yet.) This is
> an important client who is a distance from my home, and I can't afford
> to be "experimenting" as I don't wan't to errode his confidence in me.
> Unfortunately, I don't have the same equipment to test.
>
> Below is my conversation to date with 2Wire -- is there a kind soul who
> can help me verify their "solution"?

To start with, you will be making a core dump / coughing up a fur ball over
this one.

> ===================
>
> {MY ORIGINAL MESSAGE}
>
> I'm having trouble configuring my 1800HG to use a device using a static
> address as a port forwarding destination.
>
> Internally, I can reach the static address device without a problem.
>
> THe problem seems to get the device to appear in the list of devices on
> the "Home Network" page. Without this, the device doesn't appear in the
> list of devices "Choose the computer that will host applications" on
> the "Edit firwall setttings" page.
>
>
> Is there a way to get a static address device to appear on this list,
> so I can complete the port forwading instructions?
>
> THank you
>
> d.
> ===================

This seems reasonable enough.

> ===================
>
> {REPLY}
>
> Dear D,
>
> Thank you for contacting 2Wire Customer Support. The following is
> intended to answer your inquiry:
>
> Try these steps.
>
> Assign the device an IP address between 192.168.1.33 and 192.168.1.62.
> Turn the device off then back on to renew its address with your Home
> Gateway. You should be now able to see that device in the Home Network
> list to configure it.
>
>
> If this response has not answered your question or resolved your issue
> you may visit our support Website at http://support.2wire.com or reply
> to this email.
>
> Thank You,
> John C.
> 2Wire Customer Support
> http://www.2Wire.com
>
>
> =======================

Here's what they did not tell you. Your ""Static Device"" needs to be
DHCP. Rather your static device needs to be a "STICKY" device that the
2Wire assigns the ""Static IP"" to via MAC address. This way, when your
device DHCPs, it will get the ""Static IP"" from the DHCP server. Seeing
as how your device will be DHCPing, it will show up in the "Home Network
List". Once you have your device showing up in the "Home Network List" you
can easily port forward the traffic in to it.

Go core dump / cough up that hair ball. I know that I did when I heard
this. I will also say that this is not based on my experience, but rather
the experience of friend of mine who works for Sprint (now Embarq) who was
evaluating 2Wire devices for deployment to subscribers. She and I had a
LONG conversation regarding this as I could not believe it when she told
me. Suffice it to say an argument ensued, I RDPed to her system to prove
her wrong and was my self proved wrong.

> =======================
>
> {{My followup}}
>
> Thank you for your prompt response.
>
> Because this setup is not near my home (this is for a client), I'd
> appreciate if you would explain the special significance of the address
> range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
> documentation. Is there a special (undoumented) error or
> limitation requireing the use of that range only?
>
> =======================

I don't think there is any thing ""special about .33 - .62 other than those
addresses are not assigned to the normal DHCP pool, thus it is safe to use
them as ""static"" on your network.



Grant. . . .

Frant:

Thanks for your reply, but unfortunately, the device is not a PC, but
is a customers HVAC /alarm system, which does not support DHCP, it
only allows you to set an static IP and netmask from the keypad.



SO, Im stuck, right? Or am I missing the point here complely?




> > =======================
>
> Here's what they did not tell you. Your ""Static Device"" needs to be
> DHCP. Rather your static device needs to be a "STICKY" device that the
> 2Wire assigns the ""Static IP"" to via MAC address. This way, when your
> device DHCPs, it will get the ""Static IP"" from the DHCP server. Seeing
> as how your device will be DHCPing, it will show up in the "Home Network
> List". Once you have your device showing up in the "Home Network List" you
> can easily port forward the traffic in to it.
>
> Go core dump / cough up that hair ball. I know that I did when I heard
> this. I will also say that this is not based on my experience, but rather
> the experience of friend of mine who works for Sprint (now Embarq) who was
> evaluating 2Wire devices for deployment to subscribers. She and I had a
> LONG conversation regarding this as I could not believe it when she told
> me. Suffice it to say an argument ensued, I RDPed to her system to prove
> her wrong and was my self proved wrong.
>
> > =======================
> >
> > {{My followup}}
> >
> > Thank you for your prompt response.
> >
> > Because this setup is not near my home (this is for a client), I'd
> > appreciate if you would explain the special significance of the address
> > range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
> > documentation. Is there a special (undoumented) error or
> > limitation requireing the use of that range only?
> >
> > =======================
>
> I don't think there is any thing ""special about .33 - .62 other than those
> addresses are not assigned to the normal DHCP pool, thus it is safe to use
> them as ""static"" on your network.
>
>
>
> Grant. . . .

Frant:

Thanks for your reply, but unfortunately, the device is not a PC, but
is a customers HVAC /alarm system, which does not support DHCP, it
only allows you to set an static IP and netmask from the keypad.



SO, Im stuck, right? Or am I missing the point here complely?




> > =======================
>
> Here's what they did not tell you. Your ""Static Device"" needs to be
> DHCP. Rather your static device needs to be a "STICKY" device that the
> 2Wire assigns the ""Static IP"" to via MAC address. This way, when your
> device DHCPs, it will get the ""Static IP"" from the DHCP server. Seeing
> as how your device will be DHCPing, it will show up in the "Home Network
> List". Once you have your device showing up in the "Home Network List" you
> can easily port forward the traffic in to it.
>
> Go core dump / cough up that hair ball. I know that I did when I heard
> this. I will also say that this is not based on my experience, but rather
> the experience of friend of mine who works for Sprint (now Embarq) who was
> evaluating 2Wire devices for deployment to subscribers. She and I had a
> LONG conversation regarding this as I could not believe it when she told
> me. Suffice it to say an argument ensued, I RDPed to her system to prove
> her wrong and was my self proved wrong.
>
> > =======================
> >
> > {{My followup}}
> >
> > Thank you for your prompt response.
> >
> > Because this setup is not near my home (this is for a client), I'd
> > appreciate if you would explain the special significance of the address
> > range 192.168.1.33 thru 192.168.1.62, as I couldn't find any in the
> > documentation. Is there a special (undoumented) error or
> > limitation requireing the use of that range only?
> >
> > =======================
>
> I don't think there is any thing ""special about .33 - .62 other than those
> addresses are not assigned to the normal DHCP pool, thus it is safe to use
> them as ""static"" on your network.
>
>
>
> Grant. . . .

Thanks for the response David. My comments are inline.


David Efflandt wrote:

>
> I have the newer 2700HG-B and seems to automatically recognize static IPs
> on its LAN. For example with a DHCP assigned range of .64-.253 and 2Wire
> LAN IP of .254 it recognized my Linux box with a static .1 IP. Although,
> Linux does not have samba running for a netbios (Windows networking) name,
> so I manually assigned its hostname in the 2Wire's Home Network summary.
> But for security through obscurity I am running a 172.16.0.0/255.255.255.0
> LAN, so the 2Wire is 172.16.0.254. I had no trouble setting the 2Wire to
> forward SSH and Web Server ports to it.
>

Just curious, dd you purchase the 2700 directly, or was it provided by
your ISP? (If so, who is your ISP?)


> Is your box with static IP able to access the internet (proper gateway and
> DNS manually set)?
>

The device is an HVAC / Alarm controller. I cant really do anything
from it, but it was "pingable" via the static address from another PC
on the LAN once I set its static address.


> However, if you have static IP plan from your DSL provider and are trying
> to do something with multiple public IP's, that is completely different.


RIght now it is a dyanamic address on the WAN side, but I plan on
having the client request a static address from the ISP (AT&T
California (SBC)), soon.

d.

On 19 Aug 2006 01:11:52 -0700, (E-Mail Removed) <(E-Mail Removed)> wrote:
> Thanks for the response David. My comments are inline.
>
>
> David Efflandt wrote:
>
>>
>> I have the newer 2700HG-B and seems to automatically recognize static IPs
>> on its LAN. For example with a DHCP assigned range of .64-.253 and 2Wire
>> LAN IP of .254 it recognized my Linux box with a static .1 IP. Although,
>> Linux does not have samba running for a netbios (Windows networking) name,
>> so I manually assigned its hostname in the 2Wire's Home Network summary.
>> But for security through obscurity I am running a 172.16.0.0/255.255.255.0
>> LAN, so the 2Wire is 172.16.0.254. I had no trouble setting the 2Wire to
>> forward SSH and Web Server ports to it.
>>
>
> Just curious, dd you purchase the 2700 directly, or was it provided by
> your ISP? (If so, who is your ISP?)

The 2700 was provided by ATT/Yahoo (formerly SBC).

>> Is your box with static IP able to access the internet (proper gateway and
>> DNS manually set)?
>>
>
> The device is an HVAC / Alarm controller. I cant really do anything
> from it, but it was "pingable" via the static address from another PC
> on the LAN once I set its static address.

I was going to say maybe it has to generate some network traffic to be
seen.

>> However, if you have static IP plan from your DSL provider and are trying
>> to do something with multiple public IP's, that is completely different.
>
>
> RIght now it is a dyanamic address on the WAN side, but I plan on
> having the client request a static address from the ISP (AT&T
> California (SBC)), soon.

When I upgraded my dynamic DSL (faster speed) I ordered the 2700 for only
$30 (actually $79.99 w/$49.99 rebate). It has a setting to simply bridge
through the 5 static IP's (which come in through single PPPoE connection).
Then you would not have to worry about port forwarding, by may also need a
NAT router for private LAN.

On 08/18/06 18:57, (E-Mail Removed) wrote:
> Thanks for your reply, but unfortunately, the device is not a PC, but
> is a customers HVAC /alarm system, which does not support DHCP, it
> only allows you to set an static IP and netmask from the keypad.

*sigh*

> SO, Im stuck, right? Or am I missing the point here complely?

I do believe that the 2wire device is getting the better of you with this
one. Sorry. I'll see if I can't get a hold of my colleague that old me
what I told you and see if she ever found any different solutions.



Grant. . . .