Sonicwall PRO 2040 intervlan routing for Netgear GSM7248

Basically, one port comes down from the firewall to the switch. I have a sub-interface on the firewall for the second vlan. The LAN is on the default vlan and then I have a second vlan. The port that goes to the firewall is in both vlans and tagging is enabled on that port in vlan2. The "access port" that is in vlan2 does not have tagging on it.

What is wrong with this setup?
user6345Asked:
Who is Participating?
 
ccomleyConnect With a Mentor Commented:
Both VLANs are tagged?
The Netgear device is supporting BOTH tags on the outside connection?
Is the Netgear passing the tags across or stripping them?
If passing, the Sonicwall is accepting BOTH tags on that interface?
0
 
ccomleyCommented:
I can't begin to visualise it. Diagram?

What are you actually trying to achieve?
0
 
user6345Author Commented:
Sonicwall ====Netgear
       |                        |
       |                        | VLAN1 - 192.168.0.0/24 Default LAN - Accessible from VLAN2 via Sonicwall
       |                        | VLAN2 - 192.168.1.0/24 Second Network - Accessible from VLAN1 via Sonicwall
       |
       | Main LAN interface - 192.168.0.1/24
       | Subinterface for VLAN2 - 192.168.1.1/24 - set to use vlan 2 id tags

What I am trying to achieve:
intervlan routing with the firewall
0
The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

 
ccomleyCommented:
"Subinterface" is set up how?  I take it you don't mean a separate X1 phyiscal port?
0
 
user6345Author Commented:
      X0      LAN        192.168.0.1        255.255.255.0        Static        100 Mbps full-duplex        Default LAN       
      X0:V2      LAN       192.168.1.1       255.255.255.0       Static       VLAN Sub-Interface       VLAN2

Yeah, Subinterface... It is on one interface (X0)....... ^^^^This was copied from the web interface^^^

0
 
user6345Author Commented:
Also, right now I am not worried about the routing part. All I really care about is getting vlan2 to be able to communicate with the firewall at all..... Vlan1 can communicate fine. It seems like there is a problem with the tagging....
0
 
user6345Author Commented:
UPDATE:

After correcting the "Access ports" VLAN IDs in the Switch >> VLAN >> Port Config section on the web configuration interface. I was able to get the default VLAN and VLAN 2 to work over the link to the firewall.
0
 
user6345Author Commented:
You didn't really help much, but I am going to give you the points anyway.
0
 
ccomleyCommented:
So before that your answer to my second question above was "no" and this didn't help? :-)

We can only provide answers to questions and information you give us, we're not psychic! If you havn't give us enough to go on the best we can do is make suggestions where to look.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.