Solved

WatchGuard x1250e Device IP/Interface Change

Posted on 2011-03-15
2
2,364 Views
Last Modified: 2012-05-11
We have a WatchGuard x1250e that has a trusted lan configured on eth1 (10.120.0.1/22), and a private mpls connection on eth6.  The mpls connection is being moved to a cisco 2950 router that is going to handle all the mpls routing and basically hand anything outside of mpls back to the x1250e to handle.

As part of this they want the cisco 2951 to become 10.120.0.1 and the x1250e to be 10.120.0.2.  

My question:  If I change interface 1 (eth1) using the watchguard system manager from 10.120.0.1/22 to 10.120.0.2/22 will that make the x1250e's ip address 10.120.0.2 or is it changed some other way?

When I tried to make the change initially it came up with a warning "the specified ip address does not match any of the interfaces specified in this config file" which at face value makes sense because there is no interface yet configured as 10.120.0.2.

I being cautious wanted to make sure I'm not going to be bricking the x1250e and after applying the change no longer be able to connect to it with WSM.  My assumption is that following the change I should be able to close the WSM and click the connect to device button and enter 10.120.0.2 and be good to go.  Can anyone confirm?

BTW, I am working on a second WG x1250e that is not in production at the moment.  Thanks for the feedback.
0
Comment
Question by:hereiufund
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 13

Accepted Solution

by:
NarendraG earned 500 total points
ID: 35144759
There will be no issues at watchguard side but you have to change gateway of  all machines to  10.120.0.2 if already machine gateways poing to 0.1.

defiantly you will be able to connect with wsm.

I remember doing it couple of times.

Good Luck

Thanks

0
 

Author Comment

by:hereiufund
ID: 35147211
Thanks NarendraG.  Worked like a charm.  I was just being paranoid I guess.  The cisco 2951 is going to be our new default gateway for voip/data on the lan and take 10.120.0.1.  It's going to hand off external traffic to the wg which is now 10.120.0.2.
0

Featured Post

Now Available: Firebox Cloud for AWS and FireboxV

Firebox Cloud brings the protection of WatchGuard’s leading Firebox UTM appliances to public cloud environments. It enables organizations to extend their security perimeter to protect business-critical assets in Amazon Web Services (AWS).

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Network traffic routing plays key role in your network, if you have single site with heavy browsing or multiple sites, replicating important application data from your Primary Default Gateway ,you have to route your other network traffic from your p…
Imagine you have a shopping list of items you need to get at the grocery store. You have two options: A. Take one trip to the grocery store and get everything you need for the week, or B. Take multiple trips, buying an item at a time, to achieve t…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question