Got it

NAT doesn‘t work on eNSP 1.2.00.370

Latest reply: Nov 6, 2015 16:25:34 3684 4 0 0 0

NAT still doesn't work on eNSP (including latest version 1.2.00.370)
I've got the same result as with version 1.2.00.360
Please see my previous post
http://forum.huawei.com/enterprise/thread-287057.html

Lab 3-2 from "HCNA-HNTD Intermediate Lab Guide v2.1" cannot be done as expected.
eNSP doesn't work correctly after applying NAT command on interface.
[R1-GigabitEthernet0/0/0]nat outbound 3000 address-group 1
or
[R3-GigabitEthernet0/0/0]nat outbound 2000
and after sending interesting traffic, of course.


Some additional information:
Before applying NAT commands on interfaces
  S1 can ping R1  (ping 10.0.4.1)
  S2 can ping R3  (ping 10.0.6.3)
  Windows Task Manager
    total CPU usage = 45%
    VBoxHeadless.exe CPU usage = 13%
    VBoxHeadless.exe CPU usage = 13%
After applying NAT commands on interfaces and sending interesting traffic
  S1 can't ping R1  (ping 10.0.4.1)
  S2 can't ping R3  (ping 10.0.6.3)
  Windows Task Manager
    total CPU usage = 100%
    VBoxHeadless.exe CPU usage = 50%
    VBoxHeadless.exe CPU usage = 50%

Please fix it.

Thank you.

  • x
  • convention:

user_2190635
Created Nov 5, 2015 09:16:26

I configured according to the NAT documentation. It's works.

View more

This article contains more resources

You need to log in to download or view. No account? Register

x
  • x
  • convention:

vmavrin
Created Nov 6, 2015 07:35:04

Clarification.
At least, NAT doesn't work if configured according to Lab 3-2 from "HCNA-HNTD Intermediate Lab Guide v2.1"

View more
  • x
  • convention:

ensp_commiter
Created Nov 6, 2015 08:30:11

you mean the second floor's configuration is different from HCNA-**** ?

View more
  • x
  • convention:

vmavrin
Created Nov 6, 2015 16:25:34

Configuration in file nat.rar above is logically the same like in the Lab 3-2
However, I used topo-file that built in eNSP
C:\Program Files\Huawei\eNSP\examples\HCNA2.0 Lab\Part 2\Lab 3-2 Network Address Translation (Unconfigured)

You should apply NAT configuration on interfaces and send interesting traffic
to make sure that NAT doesn't work.
Interesting traffic defined in acl.
I used ping from S1 to R3  (ping 119.84.111.3)
   and ping from S2 to R1  (ping 119.84.111.1)

View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.
Information Protection Guide
Thanks for using Huawei Enterprise Support Community! We will help you learn how we collect, use, store and share your personal information and the rights you have in accordance with Privacy Policy and User Agreement.