ip virtual-reassembly - s it safe to remove?

Unanswered Question
Dec 13th, 2007
User Badges:

Hi...


I have not used NAT on Cisco routers for a while (last time was on IOS 12.1), and I noticed that the command above (ip virtual-reassembly) is enabled by default when NAT is configured on an interface (starting from 12.3 something).


My question is: is it safe to remove this command from NAT-enabled interface? Reason being, we believe that this command is the root cause of several weird issues we've been experiencing. One of which was on ISDN BRI S/T interface. It appeared that any packets less than 500 bytes in size are dropped when this command is enabled.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
michaelchoo Thu, 12/13/2007 - 21:02
User Badges:

Edison,


Thank you for your prompt reply. I have read that document before. It still does not say if the command can safely be removed from a NAT-enabled interface.

Edison Ortiz Thu, 12/13/2007 - 21:07
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

It's not best practice to disable it but if you think that's the root of the problem, test it and see if it does.


I haven't seen anyone claiming that command creates a problem in their network connectivity.

michaelchoo Thu, 12/13/2007 - 21:15
User Badges:

OK. So, are you saying that removing the command will not stop NAT operation? Based on what I've read, this command appears to be a "safety measure" against some attacks, and that it does not really actively participate in NAT-ing operation. Can you confirm this?


Thanks.

Edison Ortiz Thu, 12/13/2007 - 21:20
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

Confirmed.

michaelchoo Thu, 12/13/2007 - 21:23
User Badges:

Thank you. That's all I wanna know. :)


Although this command may not cause issues in your experience, specifically on our customer's network, we've seen evidence that this may cause some problems. May not be the command, per se. Could be IOS bug.

Actions

This Discussion