IPv4 Address Range Acquisition and Assignment

I'm in a situation where a site has an existing Internet connection that we're using, but we have a larger pipe dropping soon that has a large c block assigned.  Notwithstanding, in the interim I have to deal with what we have.

I am not aware of the topology of their current infrasctructure except that they've given us a Cisco switch with 4 ports, each with a separate public ip assigned to each interface.  I am, unfortunately, needing a smallish block of IPs for this one interface right now (perhaps 5-10) and I am not exactly sure of the appropriate questions to ask nor what to tell them regarding getting this in position for my SonicWALL router to accept so that it can make the appropriate assignments for devices inside of it's network.

It seems that I may need to grok BGP and ASN's a little better to tell them what I want, but perhaps I'm going too far into implementation in my mind for this issue.

At any rate, I'd certainly appreciate understanding what I need to ask and explain a bit better to get this temporary fix in place.


gpsocsAsked:
Who is Participating?
 
digitapConnect With a Mentor Commented:
they should have given you an IP address with a subnet mask.  the subnet mask will define that you have four contiguous IP addresses starting with 123.123.123.123.  my guess is your subnet mask is 255.255.255.248 or 123.123.123.123/29.  this would be 6 hosts.  one for gateway, one for broadcast giving you a range of 123 - 126.

i'd use 123.123.123.123 as the WAN IP and the subnet mask of 255.255.255.248 (assuming this is what they gave you).  they should have provided you with a gateway and the DNS information.

go to network > interfaces.  edit the WAN interface and you'll see where the information should go.
0
 
digitapCommented:
what i'm seeing is that you ask for a block of 5 IP addresses.  then, use one for the WAN interface, set the subnet mask...done.  if they are non-contiguous, you'll use one for the WAN interface along with the appropriate subnet mask.  then, use the KB below to get others "assigned" to the WAN interface.

https://www.fuzeqna.com/sonicwallkb/consumer/kbdetail.asp?kbid=7621

regarding the secondary internet, i'd assign it to an additional interface on the sonicwall and use routes to send traffic out of it as needed.  if you want to assign VPN connections, then i'd move the "crappy" internet to an additional interface making it a secondary WAN, then put the long-term internet on the X1 interface as the primary WAN.  you'll want to remember to move the ARP entries for the non-contiguous subnets if that's necessary.
0
 
gpsocsAuthor Commented:
Okay, I've got a range!  Only 4, but that's getting me from point A to B right now.

So where do I set the subnet for this particular scenario for utilization?  Example, let's say I have 123.123.123.123, .124, .125 and .126.  I'm not exactly sure where you're saying to set the subnet on this unit.  Just wanting to make sure I'm getting this right vs playing.
0
Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

 
Cas KristConnect With a Mentor Commented:
Yes digitap is right. When the subnetmask is setup you can use the other ip addresses when you use nat policies (or the public server wizard, which makes the nat policies for you), make sure you use the most recent firmware for your sonicwall.
0
 
digitapConnect With a Mentor Commented:
indeed, up to date firmware is important, thanks for the reminder!  further, the public server wizard will setup the WAN > LAN firewall access rules.  it will also create three NAT policies, ingress; egress; loopback.
0
 
gpsocsAuthor Commented:
Okay, thanks.  

I ended up having an issue where connections are being made across the VPN from the 10.10.11.1 side, but not back up from the 10.10.12.0/24 side.  It has me quite baffled at the moment as to why suddenly traffic is altogether not seeming to pass back up and to connect with units up stream and still on our fabric.  Hrm.

So yeah, trying to sort this out today...
0
 
gpsocsAuthor Commented:
Blah, sorry, more delays in this one task and with these issues.  FINALLY back on this today.

Are you saying on the Network -> Interfaces -> General tab to use the IP address "123.123.123.123" with a subnet of 255.255.255.248 and then when setting up NAT for the various devices I just use an IP from that subnet?

Thanks again and thanks for your patience for the points assignment.
0
 
digitapConnect With a Mentor Commented:
sure, no problem.

you are correct as the location of setting the WAN IP address. network > interfaces > WAN (X1). under the first tab you'll find where you can set the static IP. you'll need the IP 123.123.123.123, mask 255.255.255.248, and gateway (whatever they gave you).

for NAT, you could use either the IP assigned to the WAN or one of the others. the subnet mask based on the WAN IP would help determine what IP addresses can be used and the sonicwall can figure that out. use the public server wizard to setup the firewall access rules and the NAT policies. here's a kb for that information if you need it.

https://www.fuzeqna.com/sonicwallkb/consumer/kbdetail.asp?kbid=7027

0
 
gpsocsAuthor Commented:
Thanks, posted another question regarding the TZ180 just a few minutes ago if interested.
0
 
digitapCommented:
yup...just saw it. thanks for the points!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.