TE
I must crunch
join:2006-05-07
Brea, CA
clubs:
| Internal IP Detected
George, FYI |
|
solstice
join:2003-03-05
Berkeley, CA | What's the issue?
Is DSLX able to detect addresses on the downstream side of a router? That seems wrong. |
|
Zak_D_H
Premium,VIP
join:2007-01-04
Salt Lake City, UT
 ·Qwest.net
| solstice,
The website should be checking the WAN Ip to see if it is the customer accessing the account or a DSLX employee. It should only say internal ip detected when a DSLExtreme employee such as myself is logged into a customers account but since its showing that for TE something is wrong. I am not sure who to send that to for a fix so I am going to let George take care of it. |
|
solstice
join:2003-03-05
Berkeley, CA | got it. Thanks. |
|
wb457
join:2000-02-07
Los Angeles, CA | Zak, fyi... I get the same thing when logging out out my account, but never worried about it.
--
If it ain't broke, pray it never will. |
|
OmagicQ
join:2003-10-23
Bakersfield, CA | reply to TE
Its happened to me a few times. I've posted about it here before. |
|
TE
I must crunch
join:2006-05-07
Brea, CA
clubs: | Yeah, I've seen either yours or others posts about it and I thought George should know it's still happening. I don't think it's a problem for us customers but if the system thinks we're employees, then it might be a problem for DSLX. |
|
WiFiguru
Formerly jnethostman
Premium
join:2005-06-21
Lodi, CA | reply to TE
Possibly the customer is using the same subnet, that a DSLeX employee is using?
Such as, my router is 192.168.6.1
Maybe the employee is using 192.168.6.100 or something.
Get what I am saying? |
|
TE
I must crunch
join:2006-05-07
Brea, CA
clubs:
1 edit | I don't think that is the case. The DSLX web server would see my WAN IP not my internal IP.
That is assuming NAT is working properly. 
Edit: My internal network is not on the 192.168.8.x |
|
