- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Virtual system on VSX
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Virtual system on VSX
Hello,
I just created a new interface on a virtual system that coexist with other virtaul systems on a VSX.
On my SMS i see icmp request from a virtual system with ip 192.168.196.34.
i don't have this ip anywhere on my scope.
Does someone faced the same case?
Thank you
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
Yes, this is the default VSX Internal communication network.
This is the network that the VSX uses internally to pass traffic.
This is normal traffic.
If you need to change it, which isnt necessary in most cases, follow this SK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Indeed it's a normal behaviour. If you add explicit rule with source your VS object, desired destination and service (i.e ICMP) then it should do automatic NAT and traffic will appear from real interface IP as a source instead of internal 192.168.x.x
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
Yes, this is the default VSX Internal communication network.
This is the network that the VSX uses internally to pass traffic.
This is normal traffic.
If you need to change it, which isnt necessary in most cases, follow this SK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Indeed it's a normal behaviour. If you add explicit rule with source your VS object, desired destination and service (i.e ICMP) then it should do automatic NAT and traffic will appear from real interface IP as a source instead of internal 192.168.x.x
