Ea6500 Wan side address

is there any method to find the WAN side IP address when remote? Router rebooted this afternoon and need to find its WAN address foe camera access,

If you can't find it using the Linksys Smart Wifi software, you can use a port checker like PING.EU to get your WAN IP. When you click on the link, it should show you Your IP, which is your Internet IP address.

Similar Messages

WRT54G: Static mode set on WAN side, but still sometimes pulls address via DHCP!

We've had (6) WRT54G (v5) installed in a building, for about (2) years now, with no previous problems. Now, ALL of them are doing something weird. They are all set for Static mode on the WAN side (we have static ip addresses for these), yet every now and then they will spontaneously pull an address via DHCP on their own. When they do this, the setting itself doesn't change. It will still show "STATIC" in the pull down list. But, the address will no longer be the address we assigned to the unit, and will instead appear to be an address that it pulled via DHCP.
Thanks, in advance, for any help and insight into this strange problem.
David

Ah. In that case, we're not going to put our client through the frustration of chasing a ghost in the machine. We'll just replace them with new ones. But, I'll try this on them in my spare time and let you know how it goes.
Thanks for your assistance,
David
Message Edited by ld-systems on 09-19-2007 08:01 AM

NAT port-forwarding and WAN side IP addresses

I have my Airport Extreme setup to forward port 21 to an FTP server on the LAN side of my network. The AE is connected via DSL to my ISP.
When a client from the WAN side connects to my server, the server's LOGS don't list the IP of the client, rather it says the client connected from my assigned WAN IP. For example (fake ip's):
Client ----> AE ----> FTP-SERVER
130.129.12.3 76.99.89.3 10.0.1.2
Log states client connected
from IP: 76.99.89.3
My previous Linksys router, with the same DSL modem and ISP, would report the client as connecting from 130.129.12.3.
Am I missing something in how I am configureing my AE? Or, is this how the AE manages port-forwarding and there's nothing I can do about it?
I used to use firewall rules to control access to the FTP server, i.e. rules set on the server. This can't be done anymore with the AE operating as it does.

Seems to me that the NAT translation in the Airport 802.11n is such that it does not use the incoming IP of clients connecting from the WAN side to a computer on the LAN side. The ingoing and outgoing packets reach their respective destinations, it is just that the AE uses some kind of non-standard routing (at least not that I am used to working with).
This is bad because it prevents the use of some forms of access controls on BSD and Linux servers on the LAN side, TCP Wrappers and iptables for example. This can create obvious security problems when WAN ports are set to forward to such a LAN client. We are already getting hit with robot-like script attacks on our server, this was a problem with our Linksys router, but with the above mentioned tools and scripts we were able to block abusive clients.
Perhaps an Apple can work on resolving this issue in a future firmware release, at least make it an option... Anyone from Apple out there?
jmj

"conflicts with the WAN IP address"

I just picked up a used AirPort Extreme N (Gigabit Ethernet) to replace my current non-Apple router, which has worked satisfactorily but lacks the ability to share disks--something I need. Using my G5 running 10.4.11, I downloaded AirPort Utility 5.4.2 to set up the new (to me) device, and did a factory reset just to clear everything out. I placed the AirPort in the network exactly where the old one had been--with its WAN port connected to the line supplied by my ISP (see below) and its three other ethernet ports connected to various clients. Then I ran into a problem:
Under the "Internet" icon of Airport Utility, I set it to Connect Using Ethernet, and Configure IPv4 using DHCP (My current router uses DHCP to provide IP addresss to both the wired and wireless devices on my network). The numbers below that are: IP address 192.168.1.12, subnet mask 255.255.255.0, and router address 192.168.1.1.
The first field of the line labeled "DNS Server(s)" defaults to 192.168.1.1, while the second field is empty, as are the fields Domain Name and DHCP Client ID. I left Ethernet WAN port on "Automatic" and put "Connection Sharing" on "Share a Public IP address," since I believe its combination of DHCP and NAT offer the best security.
The problem: When I click the "Update" button to confirm my settings, I get this message: "The DHCP range you have entered conflicts with the WAN IP address of your Apple wireless device."
Although I am unclear as to why the Internet Connection pane of the AirPort Utility lists "IP address" and "Router address" as two separate numbers (aren't they referring to the same device, the AirPort itself? How can it have two IP addresses?), I figured that I could play it safe and change the starting number to 192.168.1.13 to avoid the conflicts with 192.168.1.12.
But I still get the same error message when pressing "update." I tried changing the range to 192.168.1.50 - 192.168.1.60, and I still get the same error message. There seems to be no range that the utility will accept as non-conflicting with the "WAN IP address" of the Airport.
My ISP did not provide a visible modem as others in the past have done. The internet connection they left me simply comes out of a box on the back of the house that is connected by fiber optics to (presumably) a fiber optic line out in the street. However, this "supply line" has always worked fine with my non-Apple router and--after disconnecting the AirPort that had temporarily taken its place--is working right now as I throw this question to the forum.
Additional notes:
* Under the NAT tab, the box "Enable NAT Port Mapping Protocol" is checked, as it was by default) while "Enable default host at" is unchecked and blank.
* While I currently have wireless turned on in the AirPort, I haven't even tried wireless connectivity yet and want to make sure my wired connectivity is working first.
Thanks for any assistance.

The problem: When I click the "Update" button to confirm my settings, I get this message: "The DHCP range you have entered conflicts with the WAN IP address of your Apple wireless device."
This error message typically indicates that your 802.11n AirPort Extreme Base Station (AEBSn) is receiving a Private (as opposed to a Public IP address) on its WAN port. That could be because your ISP does not provide any device (computer or router), that is directly connected to their "box," with a Public IP address.
Your AEBSn is both a DHCP client (on the WAN-side) and a DHCP server (on the LAN-side). The Configure IPv4 is basically the on/off switch for the AEBSn's DHCP client. It's other option, PPPoE, would only be used if your ISP requires it.
One option would be to reconfigure the AEBSn as a bridge. This would disable both the AEBSn's NAT & DHCP services.
Although I am unclear as to why the Internet Connection pane of the AirPort Utility lists "IP address" and "Router address" as two separate numbers (aren't they referring to the same device, the AirPort itself? How can it have two IP addresses?
The IP address information on (actually the TCP/IP pane) is showing you the AEBSn's WAN port settings. Settings that with Configure IPv4 set to Using DHCP would come from the DHCP server upstream of it. If this server was providing Public IP addresses then the values in both the IP Address & Router Address fields would not be in any of the three valid Private IP Address ranges (10.x, 172.x, or 192.x)
Under the NAT tab, the box "Enable NAT Port Mapping Protocol" is checked, as it was by default) while "Enable default host at" is unchecked and blank.
This setting would not have anything to do with the error message that you are getting. Instead, this option is used as an on/off switch for the NAT-PMP protocol. This protocol is similar to non-AirPorts' UPnP protocol.
While I currently have wireless turned on in the AirPort, I haven't even tried wireless connectivity yet and want to make sure my wired connectivity is working first.
Both wired and wireless clients will be impacted by this until resolved. I again, suggest that you try reconfiguring the AEBSn as a bridge. (ref: AirPort Utility > Select the AEBSn > Manual Setup > Internet > Internet Connection > Connection Sharing = Off (Bridge Mode))

TC not routes to WAN side the website 89.97.132.131

The IP address 89.97.132.131 (corresponding to URL "www.pubblica.istruzione.it") is not available from the LAN side of TC (10.0.0.0). Same things for the POP3 mail server "pop.istruzione.it".
This address is well achievable from the WAN side of the TC router or from LAN side of all other routers.
I can surely exclude any PC, Internet Provider, ADSL modem, Op.System, Firewall, etc. problems. TC is updated to the last firmware available (7.3.2).
Ping is answering only if you use the numeric IP Address, no answer using the mnemonic URL.
I think that the TC router routes the network class "89.97.132.0" erroneously to LAN side instead of to be routed to the WAN side.
If the TC router is working as bridge, it work fine and the URL is reachable.
I contacted APPLE support and I am still waiting for answer.
Someone get similar problems ?

890306 wrote:
Can any one please help to create the tuning task... When i executed below task it encountered with below error.. dont no whats wrong in this.. please help me to resolve this error.
SQL> DECLARE
2 my_task_name varchar2(50);
3 sql_txt clob;
4
5 BEGIN
6
7 sql_txt := 'SELECT /*+ALL_ROWS*/
8 a.lcl_id AS Ora_Order, --Order_Number,
9 a.closed_date AS Closed_Date,
10 a.modified_date AS Modified_Date,
11 a.received_date AS Received_Date,
12 a.status AS Status,
13 b.seq AS Ora_Line, --Line_Number
14 b.sub_seq AS Ora_sub_line,
15 c.seq AS Unit_Number,
16 SUBSTR (c.olig_group_id, INSTR (c.olig_group_id,'.',-1, 1) + 1) AS shipment_number,leftmost single quote mark in line above terminates the string being assigned to "sql_txt" variable.
ORA-01756: quoted string not properly terminated

AEBS Loose IP on WAN side (dhcp)

Hi'
I Have an airport extreme base station, after I upgraded to 7.5.2 my WAN IP loses within a week or so, the wan side, uses dhcp
when I checks the wan ip, the address is a 169.254.x.x address, if I release/renew the interface, it still gets the 169.254 address.
after power cycle it works again, for ca. a week (I belive around the dhcp expire time)
After downgrade to 7.5.1 there are no problems, anyone got a clue ?
- I can read a-lot got LAN side problems, but it is realy a WAN side problem

Well there should not be any issues in assigning private wan ip address for BEFSR41 and WRK54G both, but you are facing issue in doing that for BEFSR41, try flashing latest available firmware on BEFSR41. You can get from www.linksys.com/download

Is there a way / app that would allow me to access my jetpack's web ui remotely from the WAN side ?

Is there a way / app that would allow me to access my jetpack's web ui remotely from the WAN side ?

netdestroy, that's a great question. I apologize that currently, we don't support any applications that allow this capability.
LasinaH_VZW
Follow us on Twitter @VZWSupport

How do I set up the port interface for the WAN side of my RVS4000 to 100T Full Duplex?

How do I set up the port interface for the WAN side of my RVS4000? The ISP says I need to set it to 100T Full Duplex, but where would I do that? In the Router's administration GUI I can't find any options to make such settings for the WAN side.

The setup of the folders in Finder is entirely up to you. Whatever suits your needs is what you should do. Lightroom will be fine no matter how you set it up.
So I'm not really sure what your question is.

RVS4000 won't get WAN DHCP address

I just tried replacing a cheap domestic router/switch with an RVS4000 V2 on our work network. This has a WAN connection to a cable modem for internet access via a dynamic IP address.
When I first connected the RVS4000 it got a WAN ip address via DHCP of 192.168.100.11. This is the type of IP address we get when there is an upstream problem with our ISPs cable network, and sure enough we had no internet access. The RVS4000 was set to use DHCP on the WAN interface. So I logged a support call with our ISP but they said there were no problems at their end.
I then swapped the RVS4000 out for the original router. This worked fine and got a WAN DHCP address of 77.xxx.yyy.zzz as it should. Swapped back to the RVS4000 and back to the same problem of getting a 192.168... address.
So, I downloaded the latest firmware from Cisco, which was V2.0.3.2 and flashed the RVS4000.
I then tried again connecting the RVS4000 to the cable modem but this time it would not get any WAN DHCP address at all. On the Status/Gateway page of the web interface it said that the WAN interface was down. However, on the front panel there was a yellow light indicating a live connection on the internet port.
Any suggestions? I am assuming there must be a fault, but thought I would check for advice before sending it back.

Hi Nick,
Connect your computer directly to the modem, obtain the right IP address. Then put the RVS4000 back to the modem connection. Go to the set up, MAC ADDRESS CLONE, Enable this feature then use the option "clone my pc mac".
Then wait 1-2 minutes and refresh the WAN.
Basically this feature puts your computer's MAC on the router WAN interface. You can also use the previous router's WAN MAC if you know it and want to manually type it in.
-Tom

Is my ISP blocking ICMP on the WAN side? Linksys E1500 on Comcast Cable

Hi-
Device: Linksys E1500 - firmware: 1.0.01
I've got a static IP setup for a small remote office and want to keep tabs on their internet connection by pinging it via a monitoring program we use. However, the router seems to not responding to ICMP.
- Filter Anonymous Internet Requests is unchecked.
- I've verified that the Static IP is correct.
- I've tried pinging from several remote locations on different connections, with no avail.
I can't seem to figure out why i can't ping this device. I just want to make sure there isn't a setting in the wireless router that is preventing echo replies.
The only other thing i can assume is that Comcast is filtering ICMP on their side of the WAN connection.
EDIT: Here's a traceroute from my PC to the WAN side of the Linksys....
Tracing route to 50-194-XXX-XXX-static.hfc.comcastbusiness.net [50.194.XXX.XXX]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms 172.25.2.1
2     6 ms    16 ms     6 ms 10.0.0.5
3     9 ms     8 ms     8 ms 10.0.0.1
4     7 ms     7 ms     7 ms 10.0.0.2
5     8 ms     7 ms     7 ms ont-static-208.57.XXX.XXX.mpowercom.net [208.57.XXX.XXX]
6     7 ms     7 ms     7 ms ont-static-208.57.XXX.XXX.mpowercom.net [208.57.XXX.XXX]
7     7 ms     7 ms     7 ms gi142.5.cr1.irvnca.telepacific.net [65.60.126.97]
8    10 ms    16 ms     9 ms so-0-1-0.ar2.sna1.gblx.net [64.214.146.65]
9     9 ms     9 ms     9 ms po3-40g.ar4.lax2.gblx.net [67.17.107.82]
10    21 ms    11 ms    12 ms te-0-0-0-7-cr01.losangeles.ca.ibone.comcast.net[66.208.233.201]
11    29 ms    27 ms    27 ms pos-0-4-0-0-cr01.santateresa.tx.ibone.comcast.net [68.86.86.18]
12    42 ms    47 ms    52 ms he-0-12-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.53]
13    54 ms    47 ms    47 ms he-0-6-0-0-ar02.denver.co.denver.comcast.net [68.86.94.158]
14    43 ms    43 ms    43 ms te-8-3-ur09.denver.co.denver.comcast.net [68.86.103.2]
15    62 ms    59 ms    54 ms te-17-10-cdn22.denver.co.denver.comcast.net [68.85.221.110]
16    56 ms    54 ms    69 ms c-174-51-179-19.hsd1.co.comcast.net [174.51.179.19]
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
Trace complete.
Any help verifying that i have the Linksys setup correctly would be greatly appreciated.
-Aaron

Actually, as I understand it
Since he is seeing the following, I'd say its working fine
1    <1 ms    <1 ms    <1 ms 172.25.2.1
2     6 ms    16 ms     6 ms 10.0.0.5
3     9 ms     8 ms     8 ms 10.0.0.1
4     7 ms     7 ms     7 ms 10.0.0.2
5     8 ms     7 ms     7 ms ont-static-208.57.XXX.XXX.mpowercom.net [208.57.XXX.XXX]
6     7 ms     7 ms     7 ms ont-static-208.57.XXX.XXX.mpowercom.net [208.57.XXX.XXX]
7     7 ms     7 ms     7 ms gi142.5.cr1.irvnca.telepacific.net [65.60.126.97]
8    10 ms    16 ms     9 ms so-0-1-0.ar2.sna1.gblx.net [64.214.146.65]
9     9 ms     9 ms     9 ms po3-40g.ar4.lax2.gblx.net [67.17.107.82]
10    21 ms    11 ms    12 ms te-0-0-0-7-cr01.losangeles.ca.ibone.comcast.net[66.208.233.201]
11    29 ms    27 ms    27 ms pos-0-4-0-0-cr01.santateresa.tx.ibone.comcast.net [68.86.86.18]
12    42 ms    47 ms    52 ms he-0-12-0-0-cr01.denverqwest.co.ibone.comcast.net [68.86.89.53]
13    54 ms    47 ms    47 ms he-0-6-0-0-ar02.denver.co.denver.comcast.net [68.86.94.158]
14    43 ms    43 ms    43 ms te-8-3-ur09.denver.co.denver.comcast.net [68.86.103.2]
15    62 ms    59 ms    54 ms te-17-10-cdn22.denver.co.denver.comcast.net [68.85.221.110]
16    56 ms    54 ms    69 ms c-174-51-179-19.hsd1.co.comcast.net [174.51.179.19]
As I understand it the following
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
Is actually the networks there are not allowing the trace data to be returned
which is normal for a number of reasons

Trying to set up Directv GenieGO using Airport Extreme. Getting error message: DHCP range entered conflicts with the WAN IP Address of your base station. How do I resolve the conflict.

Trying to configure an Airport Extreme manually. After I enter the IP Address of the GenieGo along with the rest of information required I am getting the following error message when I click update:
DHCP range entered conflicts with the WAN IP address of your base station.
How do I resolve the conflict?

You cannot use the same range on LAN and WAN if you are routing.. it must be different.. and you should not be routing at all.
The AE should be in bridge mode. NO DHCP settings at all.

VLANs On WAN Side

I'm looking for a security device that can handle VLANs on the WAN side.
Like virtual WAN interfaces; one for each VLAN
I'm hoping something like the SA540 can do it.
Any suggestions?

Hi,
SA500 today supports only vlan on LAN ports. vlan/sub-interfaces over WAN is not supported.
You may want to check out Cisco IOS 800 router or ASA that should support what you are looking for.
On the other hand, I am interested in understanding what you are trying to accomplish with subinterface support over WAN?
i.e. sub-interface based application service provided by local ISP? or? Feel free to send me through private message if preferred.
Regards,
Richard

RV180 managing VLAN on WAN side

Hi,
i have a question:
Does the RV180 supports managing vlans on the WAN side?
i would like to use PPPoE over a certain VLAN, and i do not get it working.
see https://supportforums.cisco.com/thread/2242943 for more information.
if the RV180 does support it, how can i manage this?
if the RV180 does not support this feature, which entry level router does support this feature?
Message was edited by: Mad Cat: added link to other question

I have this problem also with the RV180. The Fibre internet in New Zealand requires a PPPoE login in on VLAN 10. This is not unusual as I understand it. Is this something that could be implemented in a future firmware update? Happy to test a beta firmware.

AirPort Extreme with PPPoE Static WAN IP Address

I am going to be installing an AirPort Extreme in a business that has PPPoE DSL and they have a static WAN IP address and I have a few questions.
1) Going through the AirPort Utility when I change the Connect Using (under Internet tab) to PPPoE I am not given the option to fill in my static IP supplied by ATT. Am I missing something here or is it impossible to have a static public IP and PPPoE on an AirPort Extreme?
2) If the above is possible can I have my modem do PPPoE but leave DHCP and NAT to the AirPort Extreme? From what I have seen DSL modems / routers allow you to do bridge mode (PPPOE, DHCP, NAT is all done in seperate router) or you can have DSL modem do PPPoE but then DSL modem also has to do DHCP and NAT. Again am I missing someting here?

Sorry, but if the Netgear modem is configured in pure bridge mode....which would mean that the AirPort Extreme must provide the PPPoE credentials.....you are still stuck since the AirPort will not support a static IP for a PPPoE connection.
Otherwise, you will likely need to configure the modem to provide DHCP and NAT....which would mean that AirPort Extreme would need to be configured in Bridge Mode to operate correctly.
If you wanted to risk a Double NAT situation on the network, you could set up the AirPort Extreme to Connect Using a static IP address and act as a router also providing DHCP and NAT services. I am not recommending that you do this, only mentioning that you can try if you want.
Devices on the "main" network will of course not be able to "see" devices on the AirPort Extreme network.
This may....or may not... even work. No way to know unless you try.

WAN Side DHCP Renewal

My existing router (not the Actiontec) allows me to view all activity going on with my network. I just noticed that the WAN DHCP renews every hour. When I look at the lease time it shows the next renewal is coming up at 12:17pm.
Why is Verizon doing this?

jumpin68ny wrote:
fortigate 3.0. The WAN side is connected to the Ethernet Port of Verizon Fios service.
Since this is FIOS, directly to the ONT (optical network terminal)?
Google Image search for fios ont
Because if not: that first router that is handling the public IP, is giving you a one hour lease.
^^
In Verizon DHCP areas, I hear/read that the lease time is two hours.
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Ea6500 Wan side address

Similar Messages

Maybe you are looking for