Not pinging Netgate Vlan's
-
@afcarvalho said in Not pinging Netgate Vlan's:
@jarhead I did look.
gi1/0/1 defined as trunk
gi1/0/2 defined with Vlan 10 switchport access
range gi1/0/3-6 with Vlan 20 switchport access
range gi1/0/7-24 with Vlan 30 switchport accessCant't figure out why is the glitch...
A
Yeah, I think you're confusing the switches. That article is referring to the internal switch in the 1100, not your switch.
Again, Interfaces/Switches in pfSense. Make sure you keep 0t on any ports you change. -
-
Ok that should work as long as the Cisco switch is connected to port 2 (LAN). Is it not?
How exactly are you testing?
-
@stephenw10 It's connected to Netgate port 2
I can't access Negate from the switch...
That's the problem.
A
-
Which IP?
How exactly are you testing that?
-
@stephenw10 192.168.104.2 - Cisco Switch IP
192.168.104.1 Netgate -
Netgate port 2 Cable to GI1/0/1 in Cisco Switch configured as trunk
PC connected to gi1/0/11 in Cisco Switch configured as Vlan 30A
-
@afcarvalho said in Not pinging Netgate Vlan's:
I can't access Negate from the switch...
So you are trying to ping 192.168.104.1 from the switch CLI?
What error is shown?
-
-
One other strange thing:
NTP isformation is wrong!
-
It has no WAN connection and the 1100 has no battery backed RTC so it uses the most recent file timestamp.
What are you pinging from there? Clearly not the switch.
What IP address is that? Is that a static IP? How is it connected?
How are you connecting the the pfSense GUI? From a different workstation?
-
@afcarvalho Are you sure you have the WAN and LAN connected correctly? Almost seems like they may be reversed.
As Stephen said, no internet connection there. See where it says Can't check for updates, dead give away.
Also, post the G1/0/1 config. -
@jarhead I have no Wan connected.
I have one PC that I connect via one usb c adapter.
And I have a Wifi connection on that the PC that connects to the net.
That's what I am using to answer in this communication.
When I connect the PC directly to the Negate, it works fine.
The Netgate has the Lan port 192.168.104.1
The Netgate has one Vlan (30) with 172.168.108.1 as static IP and a DHCP service serving 172.168.108.100 to 172.168.100.200.A
-
@afcarvalho
You're getting very confusing now.
If you don't have a WAN connected, why would you think the NTP would be correct??What does "When I connect the PC directly to the Negate, it works fine." mean?
Do you mean you can ping all vlan interfaces?Post the G1/0/1 config.
-
@afcarvalho said in Not pinging Netgate Vlan's:
172.168.108.100 to 172.168.100.200
So when you connect the client does it get an IP in that range?
Can you ping 172.168.108.1?
If you try to ping the LAN IP, outside that subnet the client might be trying to use the wifi if you didn't disable it.
You said the firewall rules are open but are they really open?
-
@stephenw10 Connecting directly the PC to the Netgate, I can't ping 172.168.108.1 (Vlan 30)
-
Ok those rules look good.
When you connect the client directly to the LAN does it get a DHCP lease in the LAN subnet? (192.168.104.0/24)
When you connect it via the switch does it get a lease in the VLAN subnet?
Are you disabling the wifi when you test to be sure the 1100 is the default route?
-
@stephenw10 1st question - yes
2nd question no
3rd question yesA
-
@afcarvalho
3rd time.
Post G1/0/1 config. -
Sorry.
A
