🚀 go-pugleaf

Hi Alex,

Doh, I think I got the wrong end of the stick!

I'm not sure if I know the answer, but for clarity am I right in 
thinking that what you'd like to do is the following:

eth0=210.2.5.16-31 ---  Router ---  eth1=210.2.5.19
                            |
                            |
                             -------- eth2=210.2.5.25


  i.e. pick up everything on eth0 for the address range 210.2.5.16 
through 210.2.5.31, and then route to either eth1 or eth2 for the 
appropriate IP addresses. Additionally you'd like both eth1 and eth2 to 
be outside of the firewall, i.e. in the DMZ.

If this is the case then your original mask looks to me to be correct 
since it masks of your block of assigned addresses. Maybe what really 
needs to be played with is the Yast2 Network Routing configuration 
rather than the firewall stuff (note I'm guessing since this is getting 
well out of my depth :-) ).

Good luck

JH





alex wrote:
>>As Cedric says they need be on seperate subnets, however when your
>>current subnet mask is bitwise AND'ed with either of the two current
>>addresses you specify it can't see any difference between the subnets.
>>The solution   is to reallocate either of the two IP addresses so that
>>they  appear different using your existing subnet mask or to change the
>>last part of your subnet mask to
>>248 = 1111 1000
>>
> 
> i get from my isp 16 addresses this can only be done by a subnet
> 255.255.255.240 (210.2.5.16-31) - i think so!? if i am wrong - please
> correct me... and please tell my why (newbie :-((( ). this is the situation
> i'm in - and i need to workaround - how ever!
> 
> can i change the subnetmask without telling this my isp? realy i haven't
> anytime worked with calculating ip subnets... and haven't deep tcpip
> knowledge :-((( one of my greatest problems...
> 
> am i right and will this be working if i will change this to
> eth0 = 210.2.5.17 / 255.255.255.252 - (210.2.5.16-19)
> eth1 = 210.2.5.20 / 255.255.255.248 - (210.2.5.16-23)
> eth2 = 210.2.5.24 / 255.255.255.248 - (210.2.5.24-31)
> 
> hm... looks wrong... eth0 and eth1 having overlapping ip's... in eth0 .19 is
> broadcast adress and in eth1 the .23 - this looks like only 2 hosts in
> dmz... shit...
> 
> hm. i don't realy need to route the official ip address over eth2 - i can
> masquerade - if no other way is possible... but this might bei a bad
> workaround, on my view.
> 
> 
> Alex
> 
> 
> 
>