0

I have a two subnets located on two different VLANs:

  • VLAN 1 (192.168.1.0/24)
  • VLAN 2 (192.168.2.0/24)

Each subnet has a gateway at xxx.xxx.x.254.

The MacBook has an IP address 192.168.2.3/24 and gateway 192.168.2.254. When only wired to VLAN 2 via a Thunderbolt adapter, ping 192.168.1.254 works fine. When only connected wirelessly however ping does not work unless ping -S 192.168.2.3 192.168.1.254 is used.

The AP is located on VLAN 2 and I have confirmed the route is fine with a Windows PC successfully pinging 192.168.1.254 when connected via Wi-Fi. I have the issue on two different MacBooks, one running macOS High Sierra and another on Mojave. This is preventing applications accessing devices outside the local subnet.

Any ideas?

Edit: ifconfig output while on wifi - lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=201<PERFORMNUD,DAD> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 stf0: flags=0<> mtu 1280 XHC20: flags=0<> mtu 0 en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether c8:69:cd:8e:74:48 inet6 fe80::149f:8fdf:7056:487f%en0 prefixlen 64 secured scopeid 0x5 inet 192.168.2.3 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304 ether 0a:69:cd:8e:74:48 media: autoselect status: inactive en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=60<TSO4,TSO6> ether 9a:00:04:d6:24:a0 media: autoselect <full-duplex> status: inactive awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484 ether 8e:b9:e4:e2:79:f7 inet6 fe80::8cb9:e4ff:fee2:79f7%awdl0 prefixlen 64 scopeid 0x8 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: active bridge0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500 options=63<RXCSUM,TXCSUM,TSO4,TSO6> ether 9a:00:04:d6:24:a0 Configuration: id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0 maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200 root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0 ipfilter disabled flags 0x2 member: en1 flags=3<LEARNING,DISCOVER> ifmaxaddr 0 port 7 priority 0 path cost 0 nd6 options=201<PERFORMNUD,DAD> media: <unknown type> status: inactive utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000 inet6 fe80::3031:c528:4053:5962%utun0 prefixlen 64 scopeid 0xa nd6 options=201<PERFORMNUD,DAD> utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::e7c7:5a42:64b3:c5de%utun1 prefixlen 64 scopeid 0xb nd6 options=201<PERFORMNUD,DAD> utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380 inet6 fe80::5483:31f6:36c7:7383%utun2 prefixlen 64 scopeid 0xc nd6 options=201<PERFORMNUD,DAD>

  • Please detail exactly how the MacBook is connected to the network when the problem occurs. Is it BOTH connected via the wired Thunderbolt adapter as well as via WiFi? - or only WiFi? – jksoegaard Jun 1 at 19:07
  • System works fine when only wired and fails when only on Wi-Fi. – Lachlan Jun 1 at 23:43
  • Sounds like your WiFi access point / router has a configuration issue. What is the default gateway set to on your MacBook when you're on WiFi only? - is it still 192.168.2.254, or is your WiFi access points also a router? – jksoegaard Jun 1 at 23:48
  • The AP has routing functionality but it is disabled currently. IP and gateway settings for the Mac are identical when wired and wireless (neither is used con-currently). Again, Windows PC operates as expected over Wi-Fi, MacBook will only if '-S' is passed. – Lachlan Jun 2 at 0:14
  • Please include output of "ifconfig" in the Terminal when connected to the WiFi. Sounds like you have multiple interfaces configured on the same subnet or similar. – jksoegaard Jun 2 at 1:07

You must log in to answer this question.

Browse other questions tagged .