Issue with connection to remaining internal network

Issue with connection to remaining internal network

Issue with connection to remaining internal network
Issue with connection to remaining internal network
2024-01-30 22:38:14 - last edited 2024-02-14 09:02:16
Model: TL-SG1016PE  
Hardware Version: V5
Firmware Version: 1.0.1 Build 20230712 Rel.73926

I purchased this switch a couple of days ago to give me more ports on a part of my network. I'm having a challenge getting it to connect properly.

 

Let me describe the situation. Here is my network:

- Starlink is my ISP. The router is in bypass mode.

- My router is Araknis AN-220-RT. I am running only the default VLAN, no internal sub networks.

- The router is some distance from my utility room, where the bulk of my network gear is housed. The ethernet line from the router is fed into a 48-port TRENDnet switch, not managed. I have a bunch of other networking gear in the house. This is not where I installed the TL-SG1016PE. I'm having no issues with the network in the house.

- A line from the TRENDnet switch is run to an outbuilding on the property. Here is where I installed the TL-SG-1016PE.

- Prior to the upgrade, I had two switches in this location: a Hikvision DS-3E0510P-E (8 ports with PoE) and a TRENDnet 5-port unmanaged switch daisychained to it.

- The Hikvision switch fed some PoE security cameras, a TP Link WAP (EAP245), and some TVs.

- I wanted to add more ports in this area so I bought the TP Link managed switch with PoE.

 

When I replaced the Hikvision and TRENDnet switches with the TP Link, I was unable to establish an internet connection in that location. The link light for downstream devices were blinking and the devices that needed PoE were getting it, but the link light on the main line back to the house was dead. I found that if I connected that line to the Hikvision switch first and then daisychained the TP Link switch off of it, all was well. This is not an ideal hardware situation for me so I would like to get the TP Link switch working solo. I did a bunch of troubleshooting but I'm out of ideas. Would be great if someone here could point me in the right direction.

 

Here is a summary of the settings in the TL-SG1016PE:

- DHCP enabled

- IGMP snooping disabled

- no LAG groups

- no port mirroring

- Loop prevention disabled

- MTU and Port-based VLAN disabled

- 802.1Q VLAN enabled, all ports untagged

 

Here are some of the settings in the Araknis router:

- VLAN page: only the default VLAN, device management enabled, LAN untagged

- no VPN tunnels in use

- IP Mode page: dual-stack IP disabled, IPv6 to IPv4 tunnel disabled

- Local DNS database page: domain name router90760d.com, no local DNS hosts

 

Any ideas for me? Thanks in advance.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Issue with connection to remaining internal network-Solution
2024-02-13 20:49:41 - last edited 2024-02-14 09:02:16

It appears to be a wiring issue. It was a non-standard cable that was run between the two locations that was then terminated in ethernet jacks on either end. I'm getting only about 7 MB/s through this line. If the managed switch needs a certain minimum transmission speed to function, then this cable is not providing it.

 

The specs on the cable are as follows: CELFIL Cable, BJAB, 6 Pair, 22 AWG, Solid Annealed Copper Conductor

Recommended Solution
  0  
  0  
#13
Options
12 Reply
Re:Issue with connection to remaining internal network
2024-01-31 05:40:06

Hi @JeremyM 

Thanks for posting in our business forum.

No internet, huh? Strange. So, can you make sure that the uplink cable is working ok?

What about you connect a PC to this uplink cable? Do you get an IP address and what about the ping result? About the ping, read this.


If you have an IP and ping to the gateway is okay, what would be the result of trace route on your PC?

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#2
Options
Re:Issue with connection to remaining internal network
2024-01-31 15:16:05 - last edited 2024-01-31 16:22:39

Thanks for the response @Clive_A . I posted in the business forum because when I specified this switch, the website directed to me here. I hope that is not a problem.

 

I'm running a Mac with no ethernet jack. I've ordered an ethernet to USB dongle. It will arrive tomorrow.

 

The ethernet cable from the house to the external building has a female end on it at the building end. I have a short patch cable from that line to the Hikvision switch. I used the same patch cable when I connected the TP Link switch. I think this rules out an issue with the cable but if you see it otherwise, please advise.

 

  1  
  1  
#3
Options
Re:Issue with connection to remaining internal network
2024-02-01 21:33:17 - last edited 2024-02-01 21:45:07

Here is some data from traceroute, ping, and ifconfig. I ran three sets of this, one for each hardware configuration:

1. Trunk line -> Mac

2. Trunk line -> Hikvision switch -> TP Link switch -> Mac

3. Trunk line -> TP Link switch -> Mac

 

I will break these up into three separate replies because it is a lot of text.

 

Results for Trunk line -> Mac

 

MacBook-Air-3:downloads jeremy$ ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.520 ms

 

MacBook-Air-3:downloads jeremy$ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: icmp_seq=0 ttl=117 time=31.184 ms

64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=26.122 ms

 

MacBook-Air-3:downloads jeremy$ 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

anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5c

media: none

status: inactive

anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5d

media: none

status: inactive

en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3c

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3d

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c0

media: autoselect <full-duplex>

status: inactive

en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c4

media: autoselect <full-duplex>

status: inactive

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>

ether 36:c4:73:1c:4f: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 0x0

member: en1 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 8 priority 0 path cost 0

member: en2 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 9 priority 0 path cost 0

nd6 options=201<PERFORMNUD,DAD>

media: <unknown type>

status: inactive

ap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3a:3e:ef:be:80:05

inet6 fe80::383e:efff:febe:8005%ap1 prefixlen 64 scopeid 0xb 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 18:3e:ef:be:80:05

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

awdl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%awdl0 prefixlen 64 scopeid 0xd 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%llw0 prefixlen 64 scopeid 0xe 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::a099:9b05:1486:d853%utun0 prefixlen 64 scopeid 0xf 

nd6 options=201<PERFORMNUD,DAD>

utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::1ab9:ed09:6a3:c736%utun1 prefixlen 64 scopeid 0x10 

nd6 options=201<PERFORMNUD,DAD>

utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000

inet6 fe80::b9c1:c987:bb3e:bfc%utun2 prefixlen 64 scopeid 0x11 

nd6 options=201<PERFORMNUD,DAD>

utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000

inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x12 

nd6 options=201<PERFORMNUD,DAD>

utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::9111:9c4d:4bc6:36e9%utun4 prefixlen 64 scopeid 0x13 

nd6 options=201<PERFORMNUD,DAD>

utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::3c61:6c65:b583:a16e%utun5 prefixlen 64 scopeid 0x14 

nd6 options=201<PERFORMNUD,DAD>

utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::dbbb:4fae:840:5679%utun6 prefixlen 64 scopeid 0x15 

nd6 options=201<PERFORMNUD,DAD>

utun7: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::2ea:35cc:a4ac:aaa4%utun7 prefixlen 64 scopeid 0x16 

nd6 options=201<PERFORMNUD,DAD>

en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6464<VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3c:18:a0:d5:9c:71

inet6 fe80::14bb:1015:c753:1028%en6 prefixlen 64 secured scopeid 0x18 

inet 192.168.0.90 netmask 0xffffff00 broadcast 192.168.0.255

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (10baseT/UTP <full-duplex>)

status: active

 

 

MacBook-Air-3:downloads jeremy$ traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets

 1  192.168.0.1 (192.168.0.1)  134.135 ms  79.130 ms  69.343 ms

 2  100.64.0.1 (100.64.0.1)  125.282 ms  126.554 ms  136.481 ms

 3  172.16.252.60 (172.16.252.60)  107.778 ms  43.662 ms  48.315 ms

 4  undefined.hostname.localhost (206.224.65.148)  60.205 ms

    undefined.hostname.localhost (206.224.65.150)  82.776 ms

    undefined.hostname.localhost (206.224.65.148)  51.125 ms

 5  undefined.hostname.localhost (206.224.66.157)  42.811 ms

    undefined.hostname.localhost (206.224.66.143)  46.905 ms

    undefined.hostname.localhost (206.224.66.147)  43.806 ms

 6  142.250.170.144 (142.250.170.144)  62.997 ms  51.236 ms

    142.250.163.222 (142.250.163.222)  47.617 ms

 7  * * *

 8  dns.google (8.8.8.8)  101.106 ms  111.431 ms  88.161 ms

 

  0  
  0  
#4
Options
Re:Issue with connection to remaining internal network
2024-02-01 21:35:02 - last edited 2024-02-01 21:50:27

Results for Trunk line -> Hikvision switch -> TP Link switch -> Mac

 

MacBook-Air-3:downloads jeremy$ ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=2.070 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.787 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=80.174 ms

 

MacBook-Air-3:downloads jeremy$ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: icmp_seq=0 ttl=117 time=100.679 ms

64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=44.700 ms

 

MacBook-Air-3:downloads jeremy$ 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

anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5c

media: none

status: inactive

anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5d

media: none

status: inactive

en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3c

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3d

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c0

media: autoselect <full-duplex>

status: inactive

en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c4

media: autoselect <full-duplex>

status: inactive

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>

ether 36:c4:73:1c:4f: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 0x0

member: en1 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 8 priority 0 path cost 0

member: en2 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 9 priority 0 path cost 0

nd6 options=201<PERFORMNUD,DAD>

media: <unknown type>

status: inactive

ap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3a:3e:ef:be:80:05

inet6 fe80::383e:efff:febe:8005%ap1 prefixlen 64 scopeid 0xb 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 18:3e:ef:be:80:05

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

awdl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%awdl0 prefixlen 64 scopeid 0xd 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%llw0 prefixlen 64 scopeid 0xe 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::a099:9b05:1486:d853%utun0 prefixlen 64 scopeid 0xf 

nd6 options=201<PERFORMNUD,DAD>

utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::1ab9:ed09:6a3:c736%utun1 prefixlen 64 scopeid 0x10 

nd6 options=201<PERFORMNUD,DAD>

utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000

inet6 fe80::b9c1:c987:bb3e:bfc%utun2 prefixlen 64 scopeid 0x11 

nd6 options=201<PERFORMNUD,DAD>

utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000

inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x12 

nd6 options=201<PERFORMNUD,DAD>

utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::9111:9c4d:4bc6:36e9%utun4 prefixlen 64 scopeid 0x13 

nd6 options=201<PERFORMNUD,DAD>

utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::3c61:6c65:b583:a16e%utun5 prefixlen 64 scopeid 0x14 

nd6 options=201<PERFORMNUD,DAD>

utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::dbbb:4fae:840:5679%utun6 prefixlen 64 scopeid 0x15 

nd6 options=201<PERFORMNUD,DAD>

utun7: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::2ea:35cc:a4ac:aaa4%utun7 prefixlen 64 scopeid 0x16 

nd6 options=201<PERFORMNUD,DAD>

en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6464<VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3c:18:a0:d5:9c:71

inet6 fe80::14bb:1015:c753:1028%en6 prefixlen 64 secured scopeid 0x18 

inet 192.168.0.90 netmask 0xffffff00 broadcast 192.168.0.255

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (100baseTX <full-duplex>)

status: active

 

MacBook-Air-3:downloads jeremy$ traceroute 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets

 1  192.168.0.1 (192.168.0.1)  4.130 ms  1.457 ms  1.338 ms

 2  100.64.0.1 (100.64.0.1)  47.147 ms  59.114 ms  52.375 ms

 3  172.16.252.60 (172.16.252.60)  48.239 ms  113.848 ms  122.032 ms

 4  undefined.hostname.localhost (206.224.65.146)  137.031 ms

    undefined.hostname.localhost (206.224.65.144)  105.954 ms

    undefined.hostname.localhost (206.224.65.146)  109.106 ms

 5  undefined.hostname.localhost (206.224.66.143)  113.477 ms

    undefined.hostname.localhost (206.224.66.157)  120.736 ms

    undefined.hostname.localhost (206.224.66.155)  73.553 ms

 6  * 142.250.163.222 (142.250.163.222)  56.262 ms

    142.250.170.144 (142.250.170.144)  36.241 ms

 7  * * *

 8  dns.google (8.8.8.8)  34.623 ms  34.485 ms  40.57

  0  
  0  
#5
Options
Re:Issue with connection to remaining internal network
2024-02-01 21:36:53 - last edited 2024-02-01 22:04:04

Results for Trunk line -> TP Link switch -> Mac

 

MacBook-Air-3:downloads jeremy$ ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

ping: sendto: No route to host

Request timeout for icmp_seq 0

ping: sendto: No route to host

Request timeout for icmp_seq 1

ping: sendto: No route to host

Request timeout for icmp_seq 2

 

MacBook-Air-3:downloads jeremy$ 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

anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5c

media: none

status: inactive

anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:5d

media: none

status: inactive

en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3c

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether 8e:dc:83:7e:32:3d

nd6 options=201<PERFORMNUD,DAD>

media: none

status: inactive

en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c0

media: autoselect <full-duplex>

status: inactive

en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=460<TSO4,TSO6,CHANNEL_IO>

ether 36:c4:73:1c:4f:c4

media: autoselect <full-duplex>

status: inactive

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>

ether 36:c4:73:1c:4f: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 0x0

member: en1 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 8 priority 0 path cost 0

member: en2 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 9 priority 0 path cost 0

nd6 options=201<PERFORMNUD,DAD>

media: <unknown type>

status: inactive

ap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3a:3e:ef:be:80:05

inet6 fe80::383e:efff:febe:8005%ap1 prefixlen 64 scopeid 0xb 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 18:3e:ef:be:80:05

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

awdl0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500

options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%awdl0 prefixlen 64 scopeid 0xd 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (<unknown type>)

status: inactive

llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=400<CHANNEL_IO>

ether c2:f6:0f:a5:fa:54

inet6 fe80::c0f6:fff:fea5:fa54%llw0 prefixlen 64 scopeid 0xe 

nd6 options=201<PERFORMNUD,DAD>

media: autoselect

status: inactive

utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500

inet6 fe80::a099:9b05:1486:d853%utun0 prefixlen 64 scopeid 0xf 

nd6 options=201<PERFORMNUD,DAD>

utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::1ab9:ed09:6a3:c736%utun1 prefixlen 64 scopeid 0x10 

nd6 options=201<PERFORMNUD,DAD>

utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000

inet6 fe80::b9c1:c987:bb3e:bfc%utun2 prefixlen 64 scopeid 0x11 

nd6 options=201<PERFORMNUD,DAD>

utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000

inet6 fe80::ce81:b1c:bd2c:69e%utun3 prefixlen 64 scopeid 0x12 

nd6 options=201<PERFORMNUD,DAD>

utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::9111:9c4d:4bc6:36e9%utun4 prefixlen 64 scopeid 0x13 

nd6 options=201<PERFORMNUD,DAD>

utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::3c61:6c65:b583:a16e%utun5 prefixlen 64 scopeid 0x14 

nd6 options=201<PERFORMNUD,DAD>

utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::dbbb:4fae:840:5679%utun6 prefixlen 64 scopeid 0x15 

nd6 options=201<PERFORMNUD,DAD>

utun7: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380

inet6 fe80::2ea:35cc:a4ac:aaa4%utun7 prefixlen 64 scopeid 0x16 

nd6 options=201<PERFORMNUD,DAD>

en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=6464<VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>

ether 3c:18:a0:d5:9c:71

inet6 fe80::14bb:1015:c753:1028%en6 prefixlen 64 secured scopeid 0x18 

inet 169.254.241.138 netmask 0xffff0000 broadcast 169.254.255.255

nd6 options=201<PERFORMNUD,DAD>

media: autoselect (100baseTX <full-duplex>)

status: active

  0  
  0  
#6
Options
Re:Issue with connection to remaining internal network
2024-02-01 22:25:41 - last edited 2024-02-01 22:39:21

  @Clive_A Just for fun, I connected the TP Link switch directly to the Araknis router and got this result:

 

MacBook-Air-3:downloads jeremy$ ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.392 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.047 ms

 

Then I plugged the TP Link switch into the TRENDnet switch in the house. This is the same switch into which the upstream side of the trunk line is connected. I got this result:

 

MacBook-Air-3:downloads jeremy$ ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.607 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.643 ms

 

OK, so all of this indicates that the problem occurs only when I plug the TP Link switch into the downstream side of the trunk line. What does this mean? Could it be the way the trunk line is terminated?

 

Here are photos of the upstream side:

 

 

...and the downstream side:

 

 

  0  
  0  
#7
Options
Re:Issue with connection to remaining internal network
2024-02-02 05:48:06

Hi @JeremyM 

Thanks for posting in our business forum.

Seems to be your VLAN config issues.

How to configure 802.1Q VLAN on TP-Link Easy Smart/Unmanaged Pro Switches

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#8
Options
Re:Issue with connection to remaining internal network
2024-02-04 16:34:27

  @Clive_A I read the article. Thanks for pointing me to the resource. I don't see what I am doing wrong with the VLAN configuration. For the initial setup of the switch, I am mirroring the router and using only the default VLAN with all network traffic being untagged.

 

Here is the screenshot of the VLAN config page in the router:

 

 

and here is the switch:

 

All other switches in the network are unmanaged, dumb ones. They don't have the ability to configure VLAN traffic. 

 

What am I missing?

  0  
  0  
#9
Options
Re:Issue with connection to remaining internal network
2024-02-05 03:20:24

Hi @JeremyM 
Thanks for posting in our business forum.

JeremyM wrote

  @Clive_A I read the article. Thanks for pointing me to the resource. I don't see what I am doing wrong with the VLAN configuration. For the initial setup of the switch, I am mirroring the router and using only the default VLAN with all network traffic being untagged.

 

Here is the screenshot of the VLAN config page in the router:

 

 

 

and here is the switch:

 

 

All other switches in the network are unmanaged, dumb ones. They don't have the ability to configure VLAN traffic. 

 

What am I missing?

Sorry that I am not able to help you if there is a third-party device and some unknown feature is involved. I'd recommend you disable "device management". I don't know what that means but it sounds like some kind of management VLAN and it probably would cause a problem.

First, our switch is based on the 802.1Q VLAN and I am not sure how their management VLAN works. It might be a proprietary protocol and require their switch to enable this as well to work?

 

This switch should work by default if you did not set up any VLAN and it looks like it is on default, VLAN1 unmodified. The switch should work with VLAN 1 and it should pass whatsoever from VLAN 1(uplink).

Only thing I can tell wrong is the device management.

 

Just try to get everything on default/unmodified and see if they work together.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Beta firmware got some NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#10
Options
Re:Issue with connection to remaining internal network
2024-02-08 18:35:15

  @Clive_A 

I tried disabling device management in the Araknis router and it made no improvement. With the TP link switch connected directly to the trunk line, devices were not able to achieve a connection to the internet.

 

Have you given any thought to my earlier finding that connecting the TP Link switch directly to the Araknis router was successful but connecting it to the trunk line posed problems?

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 547

Replies: 12

Related Articles