Periodically I get stuck on a config change on my sonicwall. I need help with this one from an experienced sonicwall user. I am using sonicwall enhanced with X0-LAN, X1-WAN in a typical setup. I am now adding X2-SIP which is a dedicated WAN channel talking to my SIP provider. I need to setup NAT and routing so that (1) the provider sees all traffic as coming from x.x.x.38(x2), (2) all return traffic goes to y.y.y.23(x0). So basic NAT so far. But I also need to assure that any incoming traffic on X2 destined for x.x.x.38 goes to y.y.y.23(x0). Inbound and outbound must be fully NAT so that SIP will work. I'm not keeping the order of routing vs NATting clear in my head. I am able to setup a route so that a ping on the LAN-side server will route out X2 to the provider and respond back to me. I guess since it responds this validates that the "built-in" NAT is working. What I can't do is get an inbound ping to make it through the FW - all packets get dropped (drop rule 36). Do I need an incoming route? Or will NAT alone suffice for incoming? i have tried a typical two-rule NAT which I have done many times but the different interface is what's throwing me. Anybody done this specifically on sonicwall enhanced and can help?