Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 5625 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SFOS 17.1.0 and Default Gateway

Vik Patel

I have three port configured with segregated networks:

Port 3 - 192.168.1.1 static IP and DHCP

Port 4 - 192.168.2.1 static IP and DHCP

Port 5 - 192.168.3.1 static IP and DHCP

 

Ever since I upgraded from v17.0.8 to v17.1.0 I have noticed that connecting to any of the above networks I always get a default router/gateway of 192.168.3.1. Is this a known issue with 17.1.0 and if so how do I fix?

 

Update: After further testing looks like this is only happening with my static leases.



This thread was automatically locked due to age.
  • 0

    Hi,

    Are you using the XG as your DHCP server? In your DHCP server you set the default gateway.


    ian

  • 0 in reply to rfcat_vk

    yes, there is XG dhcp server running on each port and default gateway for each port is set appropriately ... looks like I always get the gateway ip of my highest port ... if I turn off the dhcp server on port 4 and 5 then I get the correct gateway (192.168.1.1) when I connect to port 3 ... if I turn off dhcp server only on port 5 then I get gateway of 192.168.2.1 when connecting to port 3 ... if dchp is running on all ports, I always get 192.168.3.1 when connect to all ports for my static leases 

  • 0 in reply to Vik Patel

    You need to set the default gateway for each server otherwise you get the "default" gateway as seen by the XG. If you don't tell the client PC what the default gateway you appear to get a random assignment.

    Now as you have asked is this a bug and I would agree with you it is a bug. If you are a business customer you can log a fault, otherwise you have to hope one of the forum mods pass the issue to a developer to investigate.

    Ian

  • 0 in reply to rfcat_vk

    got it ... looks like a bug with "system dhcp static-entry-scope global" which I have set and v17.1.x