I'm totally stymied - anyone willing to help … (Mostly Solved).
-
Hi Folks,
I'm now up to date with 2.3.4 and have decided to scrap my prior failures and go back to square 1.
I am trying to configure a system with a WAN, LAN, and OPT1 (using a CIDR block from my ISP).
The WAN is the easy part - Set the static IP, Set to IPv4 only, assign the gateway, assign the DNS Servers. Set a rule to forward mail traffic to my mail server.
The LAN "appears" straightforward - Set network, IPv4 only, NO gateway, DHCP on, Assign static IPs for infrastructure systems, Accept default NAT rules. What I mean by appears is that this is what I did in the last attempt and some of my systems could not see outside.
The OPT1/CIDR assignment is where I'm totally lost. It's a /28 block at 160.0/28. I know to assign the OPT1 IP address as the suggested gateway (160.1). However, this is where the confusion really sets in - Do I need to set an OPT1 gateway to point to my static WAN address? Also, what do I need to set on my systems to allow me to use 2 ports - one on the LAN and then second a fixed member of the CIDR block with the routing seeing the 160.1 as it's default GW?
Thanks for any review comments and steps to get me on the right path.
Tim
-
You need a routed subnet from your ISP. Meaning your WAN is one network and another network is routed to your address on that.
-
That's what we "supposedly" have, but there have been a lot of mistakes made by them in his move, so I will have the check the routing on their end again.
-
So you have a transit network to connected this new routed network to you?
-
So you have a transit network to connected this new routed network to you?
Yes - our 24.240.16.0/28 is a CIDR block provided by Cox that rides on our 174.79.33.133 static link.
-
Then:
1. create an inside network, just like any other LAN using that subnet.
2. Put any rules for what that network can access on that interface, just like any other LAN.
3. disable outbound NAT on WAN for that source network
4. pass any inbound access you want on WAN, like from source any to destination 24.240.16.10:80 for a web server there.
5. take the rest of the day off.
-
Then:
1. create an inside network, just like any other LAN using that subnet.
2. Put any rules for what that network can access on that interface, just like any other LAN.
3. disable outbound NAT on WAN for that source network
4. pass any inbound access you want on WAN, like from source any to destination 24.240.16.10:80 for a web server there.
5. take the rest of the day off.
Actually, there turned out to be a 0. step - call Cox level 2 and get our REAL CIDR block. The technical info from the install gave us completely wrong CIDR info. The original 24.249.160.0/28 wasn't even close to our assigned block for the MODEM :o … Almost 80 hours down the drain on this >:(.
Now I don't fee like such a noob.
Thanks to all for bearing with me :-\
