ER-3 -Comcast Fiber
-
@mroth911 said in ER-3 -Comcast Fiber:
OK with the configre of Jared i got it working.where do i put the dmz..?
DMZ would be another port entirely. This complicates the setup a bit, but isn't horrible. If you have ETH0 set for your WAN, and ETH1 for your LAN (e.g. 10.x.x.x) then ETH2 will be your DMZ.
-
so .. on eth2. would i add my first public facing ip address.?
-
@mroth911 said in ER-3 -Comcast Fiber:
so .. on eth2. would i add my first public facing ip address.?
That would be a common choice, and a good one. So yes. Not a strict requirement, but an easy way to go.
-
what would be my gateway then for the /27..
-
eth2 would have an address of X.X.X.65/27
then in your public faicng devices, they would have X.X.X.65/27 through X.X.X.94/27 and use a gateway of X.X.X.65/27 -
That does not make it a DMZ< but jsut another network and everything will route back and forth.. You need to add firewall rules to restrict and such to make it a true DMZ.
-
Ok so i should remove the 10.254.254.1 off of eth2
and config the ip to 64/27
-
@mroth911 said in ER-3 -Comcast Fiber:
Ok so i should remove the 10.254.254.1 off of eth2
and config the ip to 64/27
- I updated my post.
-
@mroth911 said in ER-3 -Comcast Fiber:
what would be my gateway then for the /27..
The IP that you assign to the router's port for that network.
-
Gentalman.. I thank you so much you guys rock!!! .... It is configured. and working!!!
-
One last question... I put a static ip ...in my nic card... then I go on web ask what my ip address is and it's pinging the 242.network as my ip.. not the nic card i configured.
-
It is going through NAT.
-
I see masquerade eth0..
nothing with eth2
-
it's not going threw nat at all? Wondering why eth2 is show ip 242 when i have the nic set to 66 .. Frustrating wish i new more time to learn! Thank you guys for all your help.
-
@mroth911 said in ER-3 -Comcast Fiber:
it's not going threw nat at all? Wondering why eth2 is show ip 242 when i have the nic set to 66 .. Frustrating wish i new more time to learn! Thank you guys for all your help.
The traffic from eth2 is most certainly hitting the NAT masquerade rule.
