Ubuntu and Pfsense connectivity issues
-
So, I'm quite new to networking, and I'm pretty sure it's a dumb issue, but I couldn't find the answer online.
My configuration is shitty modem/router given by my ISP in PPPoe, behind that, a router with pfsense, and then a managed switch.
My switch have set up 5 vLAN 172.16.10.0/24, 172.16.20.0/24, 172.16.30.0/24, 172.16.40.0/24, 172.16.50.0/24
My DHCP is set up as to lease for each one from 172.16.xx.100 to 172.16.xx.200
As I'm installing and testing stuff on some mini PC I am just disconnecting the eth cable from my desktop and attaching it to whatever I need.This is on 172.16.50.0/24, the gw is 172.16.50.1
Pfsense works as intended and leases out IP (.101, .102, .103, etc), I have internet connectivity on any Windows machine. The Linux machines cannot even ping the gateway (Destination Host Unreachable). But they get an IP and they appear in the DHCP Lease list.
I've reverted my shitty ISP modem/router to work as that and if I plug in the Ubuntu machines directly into it they work just fine.
I've disabled both Snort and pfBlockerNG, plus any restrictive rules (but as Windows machines can do everything I kinda doubt it's a pfsense firewall rules issue).
My best bet is something to configure in Ubuntu, but I'm too green in networking to know WTF I'm doing wrong.
On Linux I've also manually set the default gw but I still can't ping it (Destination Host Unreachable).
I'm kinda short on ideas here, and I would avoid having to install windows on the mini PC
Quick update, I've tried to ping my switch, and I can do it from the windows machines but not from the Linux ones. -
Another little update, I connected my Ubuntu machine directly to pfsense and it's connecting to the default gateway, the issue is something between the managed TP-Link switch and ubuntu
-
@calcifer VLAN issues with TP-Link switches are not uncommon.
-
On older TP-Link switches certainly. But even on those you would expect this to work especially since DHCP is working.
That error though implies the Linux box has no default route, or at least no route to the gateway. Obviously it should be in the same subnet as the gateway and in that situation should be ARPing for it not trying to route to it. So the first thing I would check is the routing and ARP tables on the Linux host.Is the TP-Link switch running in Layer 3 mode by any chance?
Steve
-
@stephenw10 so, i looked more into it and, as I'm a noob on Linux too, I didn't know that for VLAN you have to setup manually the .yaml in /etc/netplan, and configure a VLAN interface... That wasn't necessary on windows, and I'm even studying for the CCNA but no one ever brought this difference up.
It was a stupid thing in the end. Took me two days to figure that out. Bash your head and learn, I guess. -
Ah, you are using the VLANs dircetly on the hosts?
Usually you would not do that. Instead the switch would be configured to provide 'access ports' for each VLAN and hosts can connect to that untagged directly.Interesting that DHCP seemed work without that then. I would not expect it to.
Steve
-
@stephenw10 yeah, the DHCP was working that's why at first I didn't though about an issue between switch and host but between router and host... Anyway if you think it's better letting the switch managing everything, I'll do that, and avoid some more configuration
-
Yes, I would definitely recommend that. If only because that's how virtually all networks with VLANs are setup and if you do something unusual like that you will hit unusual problems!
Really the only reason to trunk tagged VLANs to a host is so that host can access multiple VLANs. So you might do that for a VM server or an access point with multiple SSIDs.Steve
