@d0ugmac1
It seems improbably that a device that is getting its IP info from a DHCP server cannot ping it.
Yes, I think so too.
Can you confirm that this interface is getting it's configuration via DHCP and was not statically configured by you?
Yes
What is the output of 'netstat -nr' ?
netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.40.1 0.0.0.0 UG 0 0 0 enp5s0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.40.0 0.0.0.0 255.255.255.0 U 0 0 0 enp5s0
192.168.110.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr2
192.168.120.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr3
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
Packet Capture
I captured the moment the host received the ip from the DHCP
113 28.176003513 EliteGro_→ Broadcast ARP 60 Who has 192.168.40.6? Tell 192.168.40.2
114 28.450720504 Tp-LinkT_ → Broadcast ARP 60 Who has 192.168.0.2? Tell 192.168.0.1
115 28.962945937 → Broadcast ARP 60 Who has 192.168.40.1? Tell 192.168.40.101
116 29.019509449 Tp-LinkT_ → Broadcast Realtek 60
117 29.199908945 EliteGro_ → Broadcast ARP 60 Who has 192.168.40.6? Tell 192.168.40.2
118 29.986829576 → Broadcast ARP 60 Who has 192.168.40.1? Tell 192.168.40.101
119 30.020112923 Tp-LinkT_ → Broadcast Realtek 60
120 30.223802271 EliteGro_ → Broadcast ARP 60 Who has 192.168.40.6? Tell 192.168.40.2
121 30.888731265 0.0.0.0 → 255.255.255.255 DHCP 332 DHCP Request - Transaction ID 0xce12c12b
122 30.891301339 192.168.40.1 → 192.168.40.102 DHCP 355 DHCP ACK - Transaction ID 0xce12c12b
123 30.899818906 :: → ff02::16 ICMPv6 110 Multicast Listener Report Message v2
124 30.924978898 Elitegro_ → Broadcast ARP 42 ARP Announcement for 192.168.40.102
125 30.927780417 192.168.40.102 → 224.0.0.22 IGMPv3 54 Membership Report / Join group 224.0.0.251 for any sources
126 30.958652626 Elitegro_ → Broadcast ARP 42 Who has 192.168.40.1? Tell 192.168.40.102
127 30.958871127 Tp-LinkT_ → Elitegro_ ARP 60 192.168.40.1 is at c0:c9:e3:
128 30.971807469 :: → ff02::16 ICMPv6 110 Multicast Listener Report Message v2
129 31.010501726 → Broadcast ARP 60 Who has 192.168.40.1? Tell 192.168.40.101
130 31.018167807 192.168.40.102 → 224.0.0.251 MDNS 87 Standard query 0x0000 PTR _ipps._tcp.local, "QM" question PTR _ipp._tcp.local, "QM" question
131 31.021354203 Tp-LinkT_ → Broadcast Realtek 60
.
139 31.983772401 Elitegro_ → Broadcast ARP 42 Who has 192.168.40.1? Tell 192.168.40.102
140 31.984045877 Tp-LinkT_ → Elitegro_ ARP 60 192.168.40.1 is at c0:c9:e3:
141 32.019246165 192.168.40.102 → 224.0.0.251 MDNS 87 Standard query 0x0000 PTR _ipps._tcp.local, "QM" question PTR _ipp._tcp.local, "QM" question
142 32.024843816 Tp-LinkT_ → Broadcast Realtek 60
143 32.034932907 → Broadcast ARP 60 Who has 192.168.40.1? Tell 192.168.40.101
.
147 32.925087691 Elitegro_ → Broadcast ARP 42 ARP Announcement for 192.168.40.102
To me it looks like the router may still be 'tagging' routed packets for VLAN40 (which would be fine if there was a switch downstream that actually untags it before it hits your end user device).
In my case I’m using a non-managed switch for this network so no untagging occurs.
You are clearly getting packets as the Mbyte count is pretty high for an 'isolated' device.
I need that this machine access the internet so what I do is change the PVID back to the default and I get access again (but in the LAN network not subnet I created).
Maybe I’m over complicating things. Let me tell you what I’m trying to accomplish, maybe there is a simpler solution. I want to create a /24 subnet on a port of the router. Doesn’t need VLANs. To that port I’ve attached an unmanaged switch where I’m attaching all hosts. The router provides the DHCP service for all hosts in the network. I’ll be creating ACLs to control the access to the network.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
