Hello,

It turns out this only happens when I assign IPs to em1, em2 and em3 directly.
After I bridged them with different virtual ethernets, everything works fine.
Can anybody tell me why? Thanks!

> On 10 Dec 2016, at 2:21 PM, 雷致强 <zhiqiang....@gmail.com> wrote:
>
> en0 en2 and en3 are on my Mac, which is ok, the IP it is assigned is
192.168.3.32 (en1). My problem is that I cannot ping 192.168.1.1 (em1),
192.168.2.1 (em2) yet I can ping 192.168.3.1 (em3, the NIC my Mac is
connecting to) and I can access the Internet. Moreover, all the devices cannot
access the devices on other LANs.
>
> This is what I got on the router:
>
> # route -inet
> route: unknown option -- i
> usage: route [-dnqtv] [-T tableid] command [[modifiers] args]
> commands: add, change, delete, exec, flush, get, monitor, show
> # route show -inet
> Routing tables
>
> Internet:
> Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
> default            27.9.20.1          UGS     2656 45894821     -     8
pppoe0
> BASE-ADDRESS.MCAST localhost          URS        0        0 32768     8 lo0
> 27.9.20.1          27.9.22.243        UH         1       48     -     8
pppoe0
> 27.9.22.243        27.9.22.243        UHl        0   112560     -     1
pppoe0
> loopback           localhost          UGRS       0        0 32768     8 lo0
> localhost          localhost          UHl        1      251 32768     1 lo0
> 192.168.1/24       192.168.1.1        UC         0  1302369     -     4 em1
> 192.168.1.1        1a:cc:00:12:b1:9d  UHLl       0    63715     -     1 em1
> 192.168.1.255      192.168.1.1        UHb        0   350100     -     1 em1
> 192.168.2/24       192.168.2.1        C          0        8     -     4 em2
> 192.168.2.1        1a:cc:00:12:b1:9e  UHLl       0     1951     -     1 em2
> 192.168.2.255      192.168.2.1        Hb         0        1     -     1 em2
> 192.168.3/24       192.168.3.1        UC         2       21     -     4 em3
> 192.168.3.1        1a:cc:00:12:b1:9f  UHLl       0    25515     -     1 em3
> 192.168.3.32       78:9f:70:79:b8:5a  UHLc       1  3399193     -     4 em3
> 192.168.3.33       f0:cb:a1:79:18:43  UHLc       0    67314     -     4 em3
> 192.168.3.255      192.168.3.1        UHb        0       75     -     1 em3
> 192.168.244/24     192.168.244.1      UC         0        0     -     4 em0
> 192.168.244.1      1a:cc:00:12:b1:9c  UHLl       0        0     -     1 em0
> 192.168.244.255    192.168.244.1      UHb        0        0     -     1 em0
>
>> On 10 Dec 2016, at 6:45 AM, Fred <open...@crowsons.com> wrote:
>>
>> On 12/09/16 19:35, 雷致强 wrote:
>>> Sorry, I posted the wrong ifconfig configuration, this is the one on my
Mac:
>>>
>>> $ ifconfig
>>> 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
>>> en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>>     ether 78:9f:70:79:b8:5a
>>>     inet6 fe80::1c73:268c:55f4:65ef%en1 prefixlen 64 secured scopeid 0x4
>>>     inet 192.168.3.32 netmask 0xffffff00 broadcast 192.168.3.255
>>>     nd6 options=201<PERFORMNUD,DAD>
>>>     media: autoselect
>>>     status: active
>>> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>>     options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
>>>     ether 38:c9:86:08:81:84
>>>     nd6 options=201<PERFORMNUD,DAD>
>>>     media: autoselect (none)
>>>     status: inactive
>>> en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
>>>     options=60<TSO4,TSO6>
>>>     ether 2a:00:00:fa:2f:c0
>>>     media: autoselect <full-duplex>
>>>     status: inactive
>>> en3: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
>>>     options=60<TSO4,TSO6>
>>>     ether 2a:00:00:fa:2f:c1
>>>     media: autoselect <full-duplex>
>>>     status: inactive
>>> p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
>>>     ether 0a:9f:70:79:b8:5a
>>>     media: autoselect
>>>     status: inactive
>>> awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
1484
>>>     ether be:e7:72:f1:a8:96
>>>     inet6 fe80::bce7:72ff:fef1:a896%awdl0 prefixlen 64 scopeid 0x9
>>>     nd6 options=201<PERFORMNUD,DAD>
>>>     media: autoselect
>>>     status: active
>>> bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu
1500
>>>     options=63<RXCSUM,TXCSUM,TSO4,TSO6>
>>>     ether 2a:00:00:fa:2f:c0
>>>     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: en2 flags=3<LEARNING,DISCOVER>
>>>             ifmaxaddr 0 port 6 priority 0 path cost 0
>>>     member: en3 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::98f7:b520:f58b:14dc%utun0 prefixlen 64 scopeid 0xb
>>>     nd6 options=201<PERFORMNUD,DAD>
>>> ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
>>>     inet 10.0.0.24 --> 10.0.0.1 netmask 0xff000000
>>>
>>>> On 10 Dec 2016, at 3:16 AM, Mihai Popescu <mih...@gmail.com> wrote:
>>>>
>>>> What is the ifconfig configuration of your PC?
>>>> Do you run any pf configuration on your router?
>>>>
>>>> I really doubt ip forwarding is broken, even on a snapshot!
>>>
>> This is really confusing - en0 en2 and en3 are not active...
>>
>> but em1 and em2 are your issue?
>>
>> what does route show -inet say?
>>
>> hth
>>
>> Fred
>>
>>
>
> Thanks and best regards,
> Siegfried

Reply via email to