<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Pfsense + Cisco Router 1712 + Cisco switch 2960: Inter-vlan routing]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">I have the following devices:</p>
<p dir="auto">Pfsens Box (WAN, LAN1, LAN2, DMZ)<br />
Cisco Router 1712 (1 10/100 Ethernet, 4 integrated Switch Ports)<br />
Cisco Switch 2960<br />
4 PCs</p>
<p dir="auto">My connection</p>
<p dir="auto">PFsense WAN port  =======&gt; Internet OK<br />
PFsense LAN1: ==========&gt; Pfsenes Web GUI OK<br />
PFsense LAN2: ==========&gt; Creating 4 VLANs OK</p>
<p dir="auto">How can connect Pfsense + Cisco 1712 + Cisco 2960 and How can I configure them so that I can achieve the following:</p>
<p dir="auto">1- Behind the firewall, 4 VLANs, 4 different network segment, and they can ping each other<br />
2- 4 PCs in the sub-net can ping the internet</p>
<p dir="auto">I appreciate so much if you can point me to some post where people doing similar thing</p>
<p dir="auto">Best Regards<br />
Minh</p>
]]></description><link>https://forum.netgate.com/topic/38507/pfsense-cisco-router-1712-cisco-switch-2960-inter-vlan-routing</link><generator>RSS for Node</generator><lastBuildDate>Wed, 07 Oct 2026 16:09:41 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/38507.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 23 Oct 2011 18:49:52 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Pfsense + Cisco Router 1712 + Cisco switch 2960: Inter-vlan routing on Tue, 25 Oct 2011 00:36:46 GMT]]></title><description><![CDATA[<p dir="auto">Do you have firewall rules configured on the router?  pfSense creates a new section in the rules for the new VLAN interfaces, whatever you named them.  By default I think its opt1, opt2, etc.  You may need to create a rule to allow traffic from the VLAN's subnet outbound.  I'm pretty sure there are no rules and an implicit deny when you create a new interface.  This would result in you being able to ping the switch from pfSense, but not the other way around.</p>
]]></description><link>https://forum.netgate.com/post/301517</link><guid isPermaLink="true">https://forum.netgate.com/post/301517</guid><dc:creator><![CDATA[bdwyer]]></dc:creator><pubDate>Tue, 25 Oct 2011 00:36:46 GMT</pubDate></item><item><title><![CDATA[Reply to Pfsense + Cisco Router 1712 + Cisco switch 2960: Inter-vlan routing on Mon, 24 Oct 2011 13:57:55 GMT]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">To troubleshoot my problem, I turn on "ip debug packet detail" on the switch</p>
<p dir="auto">When I ping from the switch, I can see packet send from the switch never get reply<br />
When I ping from Pfsense, from Vlan2, I can see the switch responds<br />
I also check the firewall rules on VLAN2, L let it pass "any" source to any destination.</p>
<p dir="auto">I am still not sure why I cannot ping VLAN2 on Pfsense?</p>
<p dir="auto">Thanks<br />
Minh</p>
]]></description><link>https://forum.netgate.com/post/301375</link><guid isPermaLink="true">https://forum.netgate.com/post/301375</guid><dc:creator><![CDATA[MappleTree]]></dc:creator><pubDate>Mon, 24 Oct 2011 13:57:55 GMT</pubDate></item><item><title><![CDATA[Reply to Pfsense + Cisco Router 1712 + Cisco switch 2960: Inter-vlan routing on Mon, 24 Oct 2011 10:50:15 GMT]]></title><description><![CDATA[<p dir="auto">Thanks, almost get it. Small issue remains</p>
<p dir="auto">I have done as advised, as described below</p>
<p dir="auto">Pfsense create VLAN 2 parent interface is LAN port. Connected to trunk port on 2960, VLAN 2 IP 10.10.12.1<br />
On 2960, gi0/1 mode trunk, encapsulation do1q, Connected to Pfsense LAN port,<br />
2960 sw fa0/3 mode access associated with VLAN 2, IP 10.10.12.2<br />
CentOS box, eth0 IP 10.10.12.3<br />
I use VLAN 2 as gateway for network 10.10.12.0: route add -net 0.0.0.0/0 gw 10.10.12.2</p>
<p dir="auto">As a result:</p>
<p dir="auto">From 2960 switch, I can ping CentOS box, e.g. ping 10.10.12.3 successful<br />
From CentOS box, I can ping VLAN 2 on switch, e.g. ping 10.10.12.2 successful</p>
<p dir="auto">From PFsense VLAN 2, I can ping VLAN 2 on switch,e.g.  ping 10.10.12.2 successful, but not the other way around!<br />
(I can not ping VLAN2 from the switch)</p>
<p dir="auto">Could you please help me one more time?</p>
<p dir="auto">Thanks so much<br />
Minh</p>
]]></description><link>https://forum.netgate.com/post/301333</link><guid isPermaLink="true">https://forum.netgate.com/post/301333</guid><dc:creator><![CDATA[MappleTree]]></dc:creator><pubDate>Mon, 24 Oct 2011 10:50:15 GMT</pubDate></item><item><title><![CDATA[Reply to Pfsense + Cisco Router 1712 + Cisco switch 2960: Inter-vlan routing on Mon, 24 Oct 2011 05:46:56 GMT]]></title><description><![CDATA[<p dir="auto">I am unsure of what you want to do with the 1712 and I am also unsure of how many ports you have on your pfSense box so I will assume you have only two, a WAN and  LAN.</p>
<p dir="auto">You need to create four VLAN's and associate them with the LAN port, probably re0.  Activate them, and assign them IP's.</p>
<p dir="auto">On your 2960, connect one port to the LAN of the pfSense box.  You need to switch that port to a trunk port by entering 'switchport trunk encapsulation dot1q' followed by 'switchport mode trunk' on that interface going to the pfSense box.</p>
<p dir="auto">Then, you associate other ports on the switch to VLANs by typing 'switchport mode access' and 'switchport access vlan X' on each interface substituting X with the VLAN number you created on the pfSense box.  You would probably also want to type 'spanning-tree portfast' on your access ports to speed up the STP forwarding state.</p>
<p dir="auto">You could then create a second trunk port from the switch over to your 1712 so you can access all of the VLAN's from it.  Assuming you use FastEthernet 0/0, on that interface, do a no shutdown then proceed to create subinterfaces such as fastethernet 0/0.10, 0/0.11, and so on and just associate each with the proper dot1q VLAN by doing 'encapsulation dot1q X' on each where X is the VLAN ID number.  I find it easiest to have the subinterface number match the dot1q number also, as in fa0/0.10 is dot1q 10.</p>
<p dir="auto">And don't forget to run no shutdown on all of those interfaces ;)  Welcome to the world of Cisco.</p>
]]></description><link>https://forum.netgate.com/post/301316</link><guid isPermaLink="true">https://forum.netgate.com/post/301316</guid><dc:creator><![CDATA[bdwyer]]></dc:creator><pubDate>Mon, 24 Oct 2011 05:46:56 GMT</pubDate></item></channel></rss>