Enable routing on Windows 10

-

On Windows 10

 VMnet3 has IP 172.16.10.1/24, VMnet4 has IP 172.16.32.1/24, to enable routing between these two networks:

1. Start Powershell with administrator

2. List interfaces, find interface index ID

Get-NetIPInterface | select ifIndex,InterfaceAlias,AddressFamily,ConnectionState,Forwarding | Sort-Object -Property IfIndex | Format-Table

3. enable routing on VMnet3 and VMnet4

Set-NetIPInterface -ifindex <required interface index from table> -Forwarding Enabled


PS C:\WINDOWS\system32> Get-NetIPInterface | select ifIndex,InterfaceAlias,AddressFamily,ConnectionState,Forwarding | So
rt-Object -Property IfIndex | Format-Table
ifIndex InterfaceAlias                AddressFamily ConnectionState Forwarding
------- --------------                ------------- --------------- ----------
      1 Loopback Pseudo-Interface 1            IPv6       Connected   Disabled
      1 Loopback Pseudo-Interface 1            IPv4       Connected   Disabled
      4 VMware Network Adapter VMnet8          IPv4       Connected   Disabled
      4 VMware Network Adapter VMnet8          IPv6       Connected   Disabled
      6 Local Area Connection* 1               IPv6    Disconnected   Disabled
      6 Local Area Connection* 1               IPv4    Disconnected   Disabled
      7 VMware Network Adapter VMnet1          IPv6       Connected   Disabled
      7 VMware Network Adapter VMnet1          IPv4       Connected   Disabled
     12 Ethernet                               IPv4    Disconnected   Disabled
     18 Wi-Fi                                  IPv4       Connected   Disabled
     20 Local Area Connection* 11              IPv6    Disconnected   Disabled
     21 Bluetooth Network Connection           IPv4    Disconnected   Disabled
     21 Bluetooth Network Connection           IPv6    Disconnected   Disabled
     23 VMware Network Adapter VMnet3          IPv4       Connected    Enabled
     23 VMware Network Adapter VMnet3          IPv6       Connected    Enabled
     24 VMware Network Adapter VMnet2          IPv6       Connected   Disabled
     24 VMware Network Adapter VMnet2          IPv4       Connected   Disabled
     25 Ethernet 4                             IPv6    Disconnected   Disabled
     25 Ethernet 4                             IPv4    Disconnected   Disabled
     26 VMware Network Adapter VMnet4          IPv6       Connected    Enabled
     26 VMware Network Adapter VMnet4          IPv4       Connected    Enabled
     72 VMware Network Adapter VMnet5          IPv6       Connected   Disabled
     72 VMware Network Adapter VMnet5          IPv4       Connected   Disabled

PS C:\WINDOWS\system32>



Alternatively, change IPEnableRouter register key from 0 to 1, reboot PC

 "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters."



Comments

Post a Comment

Popular posts from this blog

Firepower FMC and FTD troubleshooting

-
 1. Display real time log on FMC or FTD: pigtail for example: pigtail | grep 192.168.2.20                      pigtail | grep sftunnel 2. Restart communication channel manage_procs.pl run it from  the sensor only, run it from FMC will reset all sensors' channel. This scripts are nice to be used when the FMC and FTD have communication problems like heartbeats are not received, policy deployment is failing or events are not received > expert ************************************************************** NOTICE - Shell access will be deprecated in future releases          and will be replaced with a separate expert mode CLI. ************************************************************** admin@FTD:~$ sudo su Password: root@FTD:/home/admin# manage_procs.pl ****************  Configuration Utility  **************  1   Reconfigure Correlator  2   Reconfigure and flush Correlator  3    Restart Comm. channel  4   Update routes  5   Reset all routes  6   Validate Network  0   Exit *****
Read more

ASA IKEv1 VPN troubleshooting Steps and Tips

-
  1. Phase I proposal mismatch  Run show crypto isakmp sa  Initiator: MM_WAIT_MSG2 Responder: No info  Most likely this is phase1 proposal mismatch, verify IKEv1 policy, other symptoms:   Initiator log: Information Exchange processing failed All configured IKE versions failed to establish the tunnel Initiator debug: Received an un-encrypted NO_PROPOSAL_CHOSEN notify message, dropping Responder log: Error processing payload: Payload ID Responder debug:  All SA proposals found unacceptable 2. IKE version mismatch:  Run  show crypto isakmp sa  no info at both initiator and responder Initiator log: Removing peer from correlator table failed, no match! Reason: User Requested  All configured IKE versions failed to establish the tunnel Initiator debug: Oakley begin quick mode PHASE 1 COMPLETED IKE Initiator sending 1st QM pkt Removing peer from correlator table failed, no match! Session is being torn down. Reason: User Requested Responder log: Tunnel Rejected: Conflicting protocols specified
Read more

Firepower 2100/1100 FTD/ASA initial setup, reimage, upgrade.

-
  Chassis FXOS and FTD share same management IP (default 192.168.45.45) Chassis FXOS (192.168.45.45) and ASA ()use different management IP although on same physical interface. SSH to FXOS/FTD are on FTD CLI prompt, go to FXOS using the  connect fxos  command Console to Chassis is on FXOS CLI prompt, go to FTD using the  connect ftd  command The Firepower 1100 does not support the FXOS Firepower Chassis Manager; only a limited CLI is supported for troubleshooting purposes. The Firepower 2100 runs an underlying operating system called the Firepower eXtensible Operating System (FXOS).  If you run ASA on Firepower 2100, ASA can be in the following modes: Appliance mode (the default after ASA 9.13)—Appliance mode lets you configure all settings in the ASA. Only advanced troubleshooting commands are available from the FXOS CLI. See the  FXOS troubleshooting guide  for more information. Firepower Chassis Manager is not supported . ciscoasa# connect fxos [admin] Connecting to fxos. Connected
Read more