Gateway WAN interface has no IP, private address

I am trying to set up a gateway on a new install of OS X 10.6. I have the WAN connected to the first ethernet port on my XSERVE which connects to my cable modem. The second ethernet port connects to a DIR655 wireless router (I have it set up to only fuction as a switch and wireless, no DHCP or firewall). The internal network us working fine, and the XSERVE is routing and doing DHCP. However, the WAN connection cannot get an IP address from the modem... It has an automatic private address. The connection is working, I tried it directly into a computer. But it will not work on the xserve. I have powered off all equipment and still no luck. I have tried both stright thru and crossover ethernet cables. Please help!

It could be a firmware related issue. Reset the router and perform a firmware upgrade. If you are using the latest firmware already, re-flash the firmware. Once done with the firmware re-flash/upgrade, reset and reconfigure the gateway.

Similar Messages

Does the RV042 have IP Aliases for WAN interface?

Hi All
We have a Small Business RV042 router, and have many Internet servers in our Internal and DMZ networks behind the router.
In our old GTA firewall, we were able to add IP aliases to our external (WAN) interface.   That is, our WAN interface can have many IP addresses besides the main IP address, e.g., 209.118.52.226, 209.118.52.227, 209.118.52.228, 209.118.52.229, etc.
209.118.52.226 is the main IP for the WAN interface.
209.118.52.227 is for our web server 1, e.g., www.example.com
209.118.52.228 is for our web server 2, e.g. support.example.com
209.118.52.229 is for our sftp server, e.g. sftp.example.com
And then we create 'tunnels' to forward incoming traffic for 209.118.52.227 to our www.example.com residing in our DMZ or Internal network, etc.
Now, is this possible with the RV042 router?    The only thing we found in RV042 is Forwarding (port range forward) but that does allow us to have IP aliases for the WAN interface.   It seems that we can only route service defined traffic or port defined traffic meant for only 1 WAN IP to our internal servers behind the router.
Actually, we had bought the RVS4000 earlier and then upgraded to the RV042 hoping that it will have what we want.
If the RV042 does not have IP alias for WAN interface, what is the lowest Cisco router model that has it?
Thank you very much in anticipation.
cmgui

Thank you tekliu
Yes, 1-to-NAT can do most of what we want.   But it is not able to direct only certain port traffic from the external WAN IP to the internal LAN IP?
For example, if we create a 1-to-1 NAT 192.168.41.50 =>
209.118.52.227, it basically opens all the traffic allowed in the Firewall to go from
209.118.52.227 to 192.168.168.41.50.
If we only want to allow say https, ie. tcp port 443, traffic to go from
209.118.52.227 to 192.168.41.50, it is not possible. Or is it?

Add Additional IP Addresses to WAN Interface on SRP527W

Hi,
Can anyone tell me how to add an additional IP addresses to the WAN interface on a SRP527W.
We are connecting to an ISP which assigns us a static IP address with our ADSL account. We also have another 2 additional WAN IP addresses that we have purchased from out ISP and wish to add them as Aliases to the WAN interface and use for other services. I would also like to use those additional IP addresses to create port forwards to our internal network.
I cannot find how to do this in the manual any where and any help would be much appreciated.
Regards
Craig

Hi Craig,
Unfortunately, this is not possible with the SRP520.
[For others reading this thread, this is possible with the SRP540]
Regards,
Andy

Cisco RV180 VLAN tagging WAN interface

Is there by any chance in the future firmware update that this product (RV180) will be able to support VLAN tagging on WAN interface like the Cisco's RV315W router? ISP in Singapore (Singtel) and Malaysia(Unifi) (http://klseet.com/index.php/mikrotik/mikrotik-rb750-750g/setup-for-unifi) requires certain type of vlan tagging on the WAN interface for it to work.
Is there any workaround to this?

I tried with only two vlans and set the DHCP active only for the office "vlan2". Computers receive the correct ip but some of them won't register on the network, i tried to set the ip manualy on the computers but that computer will still be isolated.
Ex: computer A receives ip 192.168.10.25, Subnet 255.255.255.0, Gateway 192.168.10.1, for 2-3 minutes i can access the router on 192.168.10.1 and the internet, after a random time interval the gateway won't even respond to ping.It's not from firewall related issues as i set to accept all both incoming and outgoing. If i set a manual ip corresponding to vlan1 "default" everything works.It's like that computer is isolated so i believe it has to do with the asignment of Tagged, untagged and Excluded settings on the vlans.

Multiple DMVPN Instances on Same WAN Interface

Hi Folks,
Is it possible to run Multiple DMVPN Instances on a single WAN Interface ? Can we for example configure 3 Tunnels on a Router using one same WAN Interface but running separate EIGRP Instances for each Tunnel ? Kindly let me know , Alioune

Hi Alioune,
Yes you can create DMVPN as you said with one WAN interface that is possible..... you can have multiple tunnel interfaces pointed to a WAN interface as the source interface which resides in public zone..... with different public ip's as the destination tunnel...
interface Tunnel1
description ** A-VPN Tunnel **
bandwidth 100000
ip vrf forwarding red
ip address 10.0.252.2 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1500
load-interval 60
tunnel source GigabitEthernet0/0 (WAN Interface)
tunnel destination 1.1.1.1
tunnel protection ipsec profile dmvpn
interface Tunnel1
description ** B-VPN Tunnel **
bandwidth 100000
ip vrf forwarding red
ip address 10.0.252.5 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1500
load-interval 60
tunnel source GigabitEthernet0/0 (WAN Interface)
tunnel destination 2.1.1.1
tunnel protection ipsec profile dmvpn
like the above..... shown sample...
Please rate if the given information helps!!!

Macbook Air has the same IP address as another device on my network

I recently connected airport extreme to my network, and now I cannot connect to the Intenet from my MacBook Air. The error message I get is that another device on the network is using the same IP address (192.168.1.64) I also have a mcbook pro, which is working fine, and whose IP address is 108.66.128.91, so I don't know which device has the duplicate IP address.
Furthemore, I can't connect to the new WiFi signal from my iPhone. What do I need to do to fix these errors?

I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
If the above steps do not solve the problem, start over with step 1 above, but then perform the next steps between steps 1 & 2. above.
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Continue with step 2 in the first set of steps.
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

I see another unsecured wifi network on my list. As I have recently changed routers etc. I just want to make sure it's not attached to me. It has a different IP address than the secured wifi network I have now set up.

I see another unsecured wifi network (D Link) on my list. As I have recently replaced an old modem router (D link) with a new fancy one (wireless gateway), I am wondering if this is somehow still attached to my computer. The D link wifi unsecured network has a different IP address than my newly formed secure wifi network's IP address.
Also - if I turn my wifi off (regardless of if I am on the dlink or my new secured wifi) I can still watch netflix etc. on my tv from living room which tells me the the wifi is still on. Why is this so?
Does my Mac have two IP addresses or is that D link someone elses?
THank you to anyone who can straighten me out on this as I am confused.

Thanks Tony,
Believe it or not, I had already done that - that is why I was confused as I kept seeing it in the wireless networks that I was seeing even though I had deleted it in my advanced Network of Systems Preferences. I thought if it were mine it would go away, but alas it didn't. Anyway, all is well and I can now relax that everything is secure thanks all to you.
Cheers

PRCT-1302 : The "OCR," has an invalid IP address format

Dear RAC experts,
I am setting up RAC nodes and during installation it fails with error PRCT-1302.
PRCT-01302: The "{0}" has an invalid IP address format
Cause: The format of the subnet number and/or the subnet mask is an invalid IP address format.
Action: Make sure that both the subnet number and the subnet mask have a valid IP address format.
It seems like everything OK with subnet.
public network
eth0
         Mask:255.255.255.192 / 26
private interconnect
eth1   Mask:255.255.255.240 / 28
private interconnect
eth2
        Mask:255.255.255.240 / 28
Please advice.
Thanks in advance.
RAC 2node
Linux
VMware
IBM

Hey ioannis,
So I would recommend starting from scratch on this one and seeing if we can get things to work. I would recommend following these steps:
Make sure that you have access to port 80, which is what LabVIEW and the Web Server uses for communication. This might mean turning off virus checkers or firewalls, as Altenbach suggested.
Restart your computer. This is to make sure that there isn't anything already accessing this port that is conflicting.
Start LabVIEW once the computer is back up.
Open the VI that you would like to publish. I might recommend using an Example just to test, but you could use your program.
Select Tools » Web Publishing Tool (WPT).
On the bottom of the WPT window, press the Start Web Server button.
Configure your VI as you would like. You can probably just use the defaults for now.
Select Save to Disk and replace the file if necessary.
Hightlight the address that comes up in the Document URL window and press Ctrl+C to copy it.
Open Internet Explorer and past the URL into the address bar on the development computer.
These steps should be all that is necessary to use the WPT, so please follow them and let me know if they help or not.
Thanks!
Andy F.
Message Edited by Andy F. on 03-17-2006 12:41 PM
National Instruments

DHCP disable on WAN interface

Hello,
I have a cisco router 1721, IOS 12.4(25a)
I enabled dhcp server for my local LAN, and I setup my WAN interface as dhcp interface.
My ISP told me that my router is acting as dhcp server on WAN interface...and is not good for them. Can I stop my cisco router from sending dhcp offers on WAN interface, but send dhcp offers for my local LAN ?
ip dhcp pool LOCAL
   import all
   network 192.168.1.0 255.255.255.0
   dns-server 193.x.x.x
   default-router 192.168.1.222
   domain-name appt.ro
   lease infinite
ip dhcp pool host1
   host 192.168.1.11 255.255.255.0
   client-identifier 0100.0ee8.e23d.94
interface FastEthernet0
mac-address 0019.66b3.d689
ip address dhcp
ip nat outside
ip virtual-reassembly
speed auto
full-duplex
FastEthernet0 is my WAN interface.
Thanks!

I imagine that clients on the WAN side are sending requests with a GIADDR field that matches your DHCP pool's scope. In that case, the router would handout an address. You could add an ACL to the WAN interface to block incoming udp/68 packets:
access-list 101 deny udp any any eq 68access-list 101 permit ip any any!interface FastEthernet0 ip access-group 101 in
That should prevent the router from seeing the client requests while still being able to get server responses.

Can't telnet on WAN interface, ping is ok

Hi all,
I'm not able to telnet to cisco1841 on WAN interface...( Connection timed out; remote host not responding )
telnet from inside network to LAN interface is fine
I can ping the WAN interface
port 23 appears to be closed ( nmap )
Does anyone have an idea why telnet is not working??
part of my config ( 2 wan links for redundancy, can't telnet to none of them):
interface FastEthernet0/0
description ##### LINE TO LAN #####
ip address 192.168.8.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1412
duplex auto
speed auto
interface FastEthernet0/1
description ##### TO CABLE MODEM #####
ip address dhcp client-id FastEthernet0/1
duplex auto
speed auto
no cdp enable
interface ATM0/0/0
no ip address
load-interval 30
atm restart timer 300
no atm ilmi-keepalive
dsl operating-mode auto
pvc 8/48
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Virtual-PPP1
ip address negotiated
ip mtu 1452
ip nat outside
ip virtual-reassembly
no cdp enable
no ppp chap wait
ppp pap sent-username user password pass
pseudowire 212.25.127.15 1 pw-class dialer_to_bezeqint
interface Dialer0
ip address negotiated
ip mtu 1452
ip nat outside
ip virtual-reassembly
encapsulation ppp
load-interval 30
dialer pool 1
dialer idle-timeout 200000
no cdp enable
ppp pap sent-username user password pass
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Virtual-PPP1
ip route 0.0.0.0 0.0.0.0 Dialer0 50
ip route 212.25.127.15 255.255.255.255 FastEthernet0/1 dhcp
no ip http server
no ip http secure-server
ip nat inside source route-map ADSL_NAT interface Dialer0 overload
ip nat inside source route-map CABLE_NAT interface Virtual-PPP1 overload
route-map ADSL_NAT permit 10
match interface Dialer0
route-map CABLE_NAT permit 10
match interface Virtual-PPP1
control-plane
line con 0
login local
line aux 0
line vty 0 4
privilege level 15
logging synchronous
login local
transport input telnet
end

Friend, I recommend you use the settings below, I'm doing like this below I have no problem, look no free access telnet use SSH,
An ace
access-list 10 permit you ip
access-list 10 deny any
line con 0
password you password
login local
length 0
line aux 0
password you password
login local
line vty 0 4
access-class 10 in
exec-timeout 0 0
privilege level 15
password you password
login local
length 0
transport input telnet ssh
line vty 5 15
access-class 10 in
privilege level 15
password you password
login local
length 0
transport input telnet ssh

Crypto on loopback or wan interface

hello,
i have routers terminating vpn on both sides with the loopback ip address as peers.
should i apply the crypto on the loopback interface or on the wan interface?
Thanks.

Hi,
You apply the crypto map on the wan interface.
Dont forget to identify the loopback interface as the source in you crypto-map
crypto map mapname local-address loopback 0
Please rate helpful post

RV180 DHCP IPv4 client working on WAN interface?

Hi,
Does the Cisco RV180 firewall/router support DHCP client on the WAN interface? This is specifically mentioned on the DHCPv6 client, however, it is not mentioned for the IPv4 client. I'd like to set it up using my cable modem in bridged mode connecting it to the WAN interface on the RV180? So I'd get the IP address from my ISP.
Thanks,
Niels
Sent from Cisco Technical Support iPad App

Hello Niels,
The RV180W certainly can pick up a DHCP address from your ISP on the WAN interface, through a bridged modem. In fact, this is the default configuration. Of course, you can also change your connection type to a static IP address or PPPoE connection profile (DSL).
All of our Small Business routers are definately capable of this confiugartion. Personally, I currently use a RV180W with a cable connection. The RV180W picked up the public IP address from my ISP just fine.
All the best,
-David Aguilar
Cisco Small Business Support Center
1-866-606-1866

WRVS4400n v1.1 VLAN on WAN interface

Hi,
Been trying to figure out howto create VLAN's on the WAN interface of the WRVS4400n. Is this even possible with the factory firmware?

Dear Steve,
Thank you for your reply.
The router already has the lastest firmware, 1.1.13
The situation is as follows. Our office gets several services over fiber which is switched to coper over an end node (not protocol just light <-> electric) so essentially we are connected to the internet over ethernet.
Anyway, our provider is rather mysterious over how their services work and preffer that everybody uses the equipment provided by them. The equipment is rather cheap and limited in functionality, also we're having a few problems because the equipment doesn't allow us to switch certain functions off.
We get 3 services from our provider.
1. Internet (VLAN tagged 12)
2. VPN like closed connection between locations (VLAN's tagged 123 and tagged 124)
3. SIP (VLAN untagged 13)
So I did A little investigation and came up with the following.
* For internet services they're using a PPPoE tunnel, this tunnel is established over a tagged VLAN 12.
* VLAN's 123 and 124 are for ourselves, so just connection between our offices. I don't know what the infrastructure/setup is behind this service but it somehow magically works.
* Then finally there's the SIP services which is done over VLAN 13 untagged.
So what I need todo is create a PPPoE tunnel over VLAN 12 (for internet access) and also setup VLAN's 13, 123 an 124 to be forwarded to specific ports on the the router.
/edit:
When I look at the settings in the web interface I only get the VLAN settings for ports 1 to 4 and WLAN (no port 0). I'm pretty sure this router does support it and I could set it if I had a shell on the device but I don't and I'm not seeing it in the webinterface either.

IPv4 private addressing tradeoff: small footprint vs even VLSM length?

Is minimising one's use of the private address space to avoid unnecesary potential overlap worth the hassle of having un-even VLSM lengths?
I am designing my first non-trivial IPv4 addressing scheme in the 10.0.0.0/8 range. Just two small branch offices, but on the access-layer, I'm putting servers, printers, desktops and phones onto separate VLANs. (In fact, when doing L3 at the access-layer, you can quickly end up with multiple VLANs).
Now, few of these VLANs are so big that they'll need a /24 all to themselves. In fact, a /27 for phones and printers will be fine. I'll give a /24 to desktops because 255.255.255.0 is the only mask which semi-technical users understand. Maybe a /25 for servers, which gives a bit of room for further subnetting and putting VMs onto their own VLANs.
I'll summarise each site over DMVPN as a /21 subnet. Neat.
But at each site the routing tables look messy, with the router sporting addresses like 10.9.13.129/27 and there isn't any real pattern between the L3 address and the VLAN number.
Why don't I just dole out /24's to each VLAN, After all, I'm hardly going to minimise conflict with private IP addresses chosen by prospective partners by using /20's instead of /21's for each site (right?), and even if they do, NAT can handle all these situations elegantly (right?).
What about you, would you minimise your footprint in the address space and deal with 'unevenness' in subnet sizes? Or would you be easier on your eyes now and simply bite the bullet if you had to NAT one day?
thanks!
David.
Message was edited by: David Bullock - tries to get the crux of the question closer to the top of text.

I chose Alessio's as the 'correct' answer, since it mentioned route summarisation. But both answers were correct in the sense that they were quite reasonable.
In the end, I decided to go wtih my varying-length VLSM approach, to keep the address-sprawl at each site confined to a /21 subnet. I don't find the varying-length VLSM to be much of an nuisance in practice. I miss out on being able to make the 3rd octet 'line up' with the VLAN, but I feel that's a pretty delicate affair anyhow. Some person just has to give VLAN100 as a 'best practice' for the Voice VLAN, for example, and you either start working with a /17 at each site (minimally), or abandon your numbering scheme. You'd really have to go with a /16 for each site to ensure you can number 254 VLANs in this fashion. And that means for each site that you chose, there's a 1-in-256 chance you'll pick the same second octet as someone else. With my scheme, there is a 1 in 8192 chance that I'll pick the same address range, so I've decreased the likelyhood of a conflict by a factor of 32.
At the end of the day though, so long as route summarisation works, all other considerations seem to be a matter of taste.

Wi-Fi has self-assigned IP address 169.254.9.151 and will not be able to connect to the Internet

In trying to setup my AirPort Extreme, it connects to the Internet on ethernetcables to computer but says it is not on WI-FI. I have configured it with all that I casn think of and yet I get, "Wi-Fi has self-assigned IP address 169.254.9.151 and will not be able to connect to the Internet." Can anyone tell me what is wrong?
I did both a soft reset and a hard reset to no avail. PLEASE someone help!!
Thanks!

I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
If the above steps do not solve the problem, start over with step 1 above, but then perform the next steps between steps 1 & 2. above.
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Continue with step 2 in the first set of steps.
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

Gateway WAN interface has no IP, private address

Similar Messages

Maybe you are looking for