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

Not able to access XG using wan port deployed on VMWARE(ESXI6.7)

Ashish Kumar Jha over 4 years ago

Hi All,

I have deployed Sophos XG firewall on VMWARE ESXI 6.7 and I am not able to access using WAN IP of XG.

Also I am not able to route traffic to firewall.

Please provide solution as early as possible.

This thread was automatically locked due to age.

Parents

0 apijnappels over 4 years ago

You're not really giving away a lot of info...

As for your first question about not being able to access XG through WAN; did you allow HTTPS access on WAN interface? (And if so, think about if that is what you really want since that means anyone can reach the service).

About not being able to route traffic to firewall. What exactly do you mean with that? What do you want to route to the firewall from where? If possible add a drawing of your network.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ashish Kumar Jha over 4 years ago in reply to apijnappels

Traffic route to firewall means VM's which are in same network those traffic should go to Firewall.
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

Likely a MAC Issue. You need to figure out, if you Adapter matching those, you expect to be on your vSwitch.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ashish Kumar Jha over 4 years ago in reply to LuCar Toni

Do I need to check MAC address of NiC's which are attached to VM?
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

Yes - Use the console, login to XG, go to the Advanced Shell (5 - 3) and check via ifconfig, if all your Ports are actually as intended connected to the matching vSwitch Ports.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ashish Kumar Jha over 4 years ago in reply to LuCar Toni

I checked and found below details:

PortB : 00:50:56:09:0E:B0

PortA : 00:50:56:09:0E:B1

Please suggest is this fine or need to change.
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

That is not what i meant by my initial suggestion. If you have multiple interfaces, the vSwitch is connecting them together. If you alter the XG after deployment or add/remove interfaces, those interfaces can be mixed.

You need to verify, if all your used interfaces are actually the same as intend to be on the vSwitch.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

That is not what i meant by my initial suggestion. If you have multiple interfaces, the vSwitch is connecting them together. If you alter the XG after deployment or add/remove interfaces, those interfaces can be mixed.

You need to verify, if all your used interfaces are actually the same as intend to be on the vSwitch.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Ashish Kumar Jha over 4 years ago in reply to LuCar Toni

I used NIC of two different vlan's

We are running ESXI 6.7 version of VMWARE
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

And those MACs you are using on both VLANs in the vSwitch matches the NICs on the XG firewall console, correct?
Cancel
Vote Up 0 Vote Down

Cancel
0 Ashish Kumar Jha over 4 years ago in reply to LuCar Toni

Yes
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Ashish Kumar Jha

Then you should start to tcpdump the outgoing packets and see, what is happening on this End.

as you can perform tcpdumps, you can verify, if the vswitch is causing the problem or XG. Likely its a vSwitch configuration issue.
Cancel
Vote Up 0 Vote Down

Cancel