02-24-2020 04:05 PM - edited 02-24-2020 04:06 PM
I'm setting up a lab, pfSense router -> c3750 as core -> access switch 3750 as switch1.
I've set the vlan 101 on the core switch, enabled DHCP on the vlan 101. DHCP is working well.
I've setup the route on the core switch, I can reach the router and the web from it.
With the current setup, I can't reach the router or the web from the access switch1.
Here is my configuration for the core and switch1.
Does anyone have any clue on what would prevent me from reaching the web from the switch1 or any client connected to it.
Core:
version 12.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname core ! boot-start-marker boot-end-marker ! ! ! ! no aaa new-model switch 1 provision ws-c3750-48p system mtu routing 1500 authentication mac-move permit ip subnet-zero ip routing ip dhcp excluded-address 192.168.101.252 192.168.101.253 ip dhcp excluded-address 192.168.101.254 ! ip dhcp pool vlan101 network 192.168.101.0 255.255.255.0 default-router 192.168.101.252 dns-server 8.8.8.8 8.8.8.4 ! spanning-tree mode pvst spanning-tree etherchannel guard misconfig spanning-tree extend system-id ! vlan internal allocation policy ascending ! interface FastEthernet1/0/1 ! <!-- Removed useless config info. -->
... ! interface FastEthernet1/0/47 ! interface FastEthernet1/0/48 description LinkToSwitch1 switchport trunk encapsulation dot1q switchport trunk allowed vlan 5,101 switchport mode trunk ! interface GigabitEthernet1/0/1 description LinkToPFSense no switchport ip address 192.168.1.2 255.255.255.0 ! interface GigabitEthernet1/0/2 ! interface GigabitEthernet1/0/3 ! interface GigabitEthernet1/0/4 ! interface Vlan1 no ip address shutdown ! interface Vlan5 description MGMT Vlan ip address 192.168.5.1 255.255.255.0 ! interface Vlan101 description Rack1 ip address 192.168.101.252 255.255.255.0 ! ip classless ip route 0.0.0.0 0.0.0.0 192.168.1.1 ip http server ip http secure-server ! ip sla enable reaction-alerts ! ! line con 0 line vty 5 15 ! end
switch1:
version 12.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname switch1 ! boot-start-marker boot-end-marker ! ! no aaa new-model switch 2 provision ws-c3750-48p system mtu routing 1500 ! ! spanning-tree mode pvst spanning-tree extend system-id ! vlan internal allocation policy ascending ! ! interface FastEthernet2/0/1 switchport access vlan 101 switchport mode access ! <!-- Removed useless config information --> ... ! interface FastEthernet2/0/48 switchport trunk encapsulation dot1q switchport trunk allowed vlan 5,101 switchport mode trunk ! interface GigabitEthernet2/0/1 ! interface GigabitEthernet2/0/2 ! interface GigabitEthernet2/0/3 ! interface GigabitEthernet2/0/4 ! interface Vlan1 no ip address shutdown ! interface Vlan5 ip address 192.168.5.2 255.255.255.0 ! ip default-gateway 192.168.5.1 ip classless ip http server ip http secure-server ! ! line con 0 line vty 5 15 ! end
Thanks
Guillaume Reeves
Solved! Go to Solution.
02-24-2020 04:38 PM
Hi,
You said DHCP is working fine which means users connected to switch 1 are getting internet ? This should work fine as config looks ok.
I have only concern about reaching internet from the access switch1 ( from CLI ).
Do your PFSENSE Router have Route added for 192.168.5.0/24 pointing to 192.168.1.2 ? if not please add it.
From switch1, you can ping 192.168.1.2 and 192.168.1.1 ? If not then disable IP Routing on the switch 2, since you enabled default-gateway command:
on switch 1:
no ip routing
02-24-2020 04:38 PM
Hi,
You said DHCP is working fine which means users connected to switch 1 are getting internet ? This should work fine as config looks ok.
I have only concern about reaching internet from the access switch1 ( from CLI ).
Do your PFSENSE Router have Route added for 192.168.5.0/24 pointing to 192.168.1.2 ? if not please add it.
From switch1, you can ping 192.168.1.2 and 192.168.1.1 ? If not then disable IP Routing on the switch 2, since you enabled default-gateway command:
on switch 1:
no ip routing
02-25-2020 11:56 AM
Hi,
Thanks for your help, vLan 5 was not created on the pfsense.
I had to create it and set the correct firewall rules to allow trafic.
Everything works as expected now.
Guillaume
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide