Announcement

Collapse
No announcement yet.

Superscope traffic routing

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Superscope traffic routing

    By the impending lack of IP addresses I was forced to change the DHCP scope to a superscope.

    Our new setup

    DHCP superscope (Windows 2003 R2)
    - Scope 1 - 192.168.0.x subnet 255.255.255.0
    - Scope 2 - 192.168.1.x subnet 255.255.255.0

    All DHCP requests are routed to the gateway/firewall (No DHCP relay agent). The firewall has IP-address 192.168.0.254 and IP-alias 192.168.1.254.

    The above situation works ok. But all traffic from 192.168.0.x to 192.168.1.x and vice versa is routed by the gateway. This poses no problem in daily use. When there is a deployment of workstation images its hard for the gateway (network performance).

    Is there a possibility to tackle this issue without requiring another IP range (172.16.x or 10.x.x).
    I think it is not in accordance with the standard to change the subnet to 255.255.254.0.
    Last edited by rka; 24th March 2011, 21:25.

  • #2
    Re: Superscope traffic routing

    no reason you couldn't change the subnet
    changing it to 255.255.254.0 wouldn't solve your problem though I don't think.. (although my binary is rustier than the titanic)
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment

    Working...
    X