我租屋的地方牆壁上有一個網路孔

直接把網路線從網路孔接到電腦可以經由 DHCP 取得 IP 上網

但是中間如果有接其他任何裝置都沒辦法經由 DHCP 取得 IP

試過的裝置有

一台普通 5 port Switch Hub,牌子是 TP-LINK TL-SG1005D,支援自動MDI/MDIX

兩台 WIFI 無線 AP

即使我接上去之後,手動設定正確的IP、netmask 以及 gateway 也都沒辦法上網

使用 arp -a 可以看到正確的 gateway IP 以及正確的 MAC Address

但是直接 ping 又 ping 不到

routing table 也是正常的

Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 59 0 en0



不知道為什麼會有這種狀況發生

這已經超出我理解範圍了...



已知設備為

中華電信光世代小烏龜 D-Link DSL-7740C

接著一台 D-Link DES-1024D

然後網路線接到各個房間


文章關鍵字
請檢查 D-Link DES-1024D裡面的設定,是否有以下或類似的限制,將其取消應可解決。但串接Hub或AP須有一定網路知識,不然易出問題。
1. DHCP IP RANGE開得夠不夠多
2. DHCP 相關設定是否可RELY或有其他限制,如租期過長,IP太少
3. 檢查MAC或防火牆是否有鎖定IP或限制。
4. 檢查其他進階選項是否有鎖定或限制。
以上,細節樓給樓下解說!
補充一下
有些舊的網路設備,交換機或HUB需要使用跳線串接其他網路設備,希望有幫到你!
樓下繼續
kcc16896 wrote:
請檢查 D-Link DES-1024D裡面的設定,是否有以下或類似的限制,將其取消應可解決。但串接Hub或AP須有一定網路知識,不然易出問題。
1. DHCP IP RANGE開得夠不夠多
2. DHCP 相關設定是否可RELY或有其他限制,如租期過長,IP太少
3. 檢查MAC或防火牆是否有鎖定IP或限制。
4. 檢查其他進階選項是否有鎖定或限制。
以上,細節樓給樓下解說!


我找了一下,D-Link DES-1024D 只是單純的 Switch Hub,所以沒有提供任何管理設定介面


Edkang wrote:
問題是未知設備...
看板上這個討論吧...


原來還有這種東西
不過,房東放網路設備的地方是公開的,裡面除了中華電信大烏龜,以及那台 D-Link 的 Switch 以外,沒有再接其他設備了



kcc16896 wrote:
補充一下
有些舊的網路設備,交換機或HUB需要使用跳線串接其他網路設備,希望有幫到你!
樓下繼續


我查了一下,D-Link DES-1024D 和我所有的設備都有支援自動 MDI/MDIX,所以可能不是這個問題


我有試著在接上 Switch 後,手動設定正確連線資訊
IP: 192.168.1.111
Netmask: 255.255.255.0
Gateway: 192.168.1.1
$ ifconfig
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 0c:4d:e9:c3:08:68
inet6 fe80::e4d:e9ff:fec3:868%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.111 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=1<PERFORMNUD>
media: 100baseTX <full-duplex,flow-control>
status: active


然後我下指令 arp -a
結果居然出現了以下這堆東西
brodcast整個 255.255.255.255.......
不知道到底是哪裡出問題了


$ arp -a
? (1.2.3.4) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.146) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.147) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.149) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.151) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.160) at (incomplete) on en0 ifscope [ethernet]
? (64.4.23.162) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.17) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.23) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.27) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.34) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.41) at (incomplete) on en0 ifscope [ethernet]
? (65.55.223.43) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.14) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.15) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.17) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.34) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.39) at (incomplete) on en0 ifscope [ethernet]
? (111.221.74.48) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.148) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.150) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.155) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.156) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.162) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.169) at (incomplete) on en0 ifscope [ethernet]
? (111.221.77.173) at (incomplete) on en0 ifscope [ethernet]
? (157.55.56.156) at (incomplete) on en0 ifscope [ethernet]
? (157.55.56.165) at (incomplete) on en0 ifscope [ethernet]
? (157.55.56.167) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.142) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.143) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.145) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.147) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.167) at (incomplete) on en0 ifscope [ethernet]
? (157.55.130.175) at (incomplete) on en0 ifscope [ethernet]
? (157.55.235.145) at (incomplete) on en0 ifscope [ethernet]
? (157.55.235.146) at (incomplete) on en0 ifscope [ethernet]
? (157.55.235.151) at (incomplete) on en0 ifscope [ethernet]
? (157.55.235.169) at (incomplete) on en0 ifscope [ethernet]
? (157.55.235.171) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.14) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.17) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.19) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.34) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.39) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.43) at (incomplete) on en0 ifscope [ethernet]
? (157.56.52.44) at (incomplete) on en0 ifscope [ethernet]
? (157.56.53.43) at (incomplete) on en0 ifscope [ethernet]
? (157.56.53.48) at (incomplete) on en0 ifscope [ethernet]
? (169.254.255.255) at (incomplete) on en1 [ethernet]
? (192.168.1.1) at ec:22:80:a6:55:39 on en1 ifscope [ethernet]
? (192.168.1.102) at 0:26:ab:e9:8b:b3 on en1 ifscope [ethernet]
? (192.168.1.113) at (incomplete) on en1 ifscope [ethernet]
? (192.168.1.255) at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]
? (213.199.179.146) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.147) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.149) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.155) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.159) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.160) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.162) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.167) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.175) at (incomplete) on en0 ifscope [ethernet]
? (213.199.179.176) at (incomplete) on en0 ifscope [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]
? (239.255.255.250) at 1:0:5e:7f:ff:fa on en0 ifscope permanent [ethernet]
broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]
分享的文章沒人回應,只好越貼越少
電腦先接牆壁上的網路孔,然後ping分享器,查看TTL是否過低,有可能TTL被修改了,導致無法接二級路由,私接網路設備都會失敗。
不過有方法可以解決,先查看看是不是這個問題吧!

cscworm wrote:
電腦先接牆壁上的網路孔,然後ping分享器,查看TTL是否過低,有可能TTL被修改了,導致無法接二級路由,私接網路設備都會失敗。
不過有方法可以解決,先查看看是不是這個問題吧!


TTL看起來好像正常?

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.055 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.731 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.503 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.555 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.825 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.667 ms
分享的文章沒人回應,只好越貼越少
應該是房東找專業的網管把CORE SWITCH的設定改成不能介接其他網路設備,以免頻寬被搶或亂接無限AP,我看是無解了!不然你就要試試看駭進去SWITCH改設定,被告或被抓不要找我~~~~~~~
kcc16896 wrote:
應該是房東找專業的網管把CORE SWITCH的設定改成不能介接其他網路設備,以免頻寬被搶或亂接無限AP,我看是無解了!不然你就要試試看駭進去SWITCH改設定,被告或被抓不要找我~~~~~~~


這台switch我查過了,沒有設定頁面,他只是一台很普通的switch hub
其實我後來也有直接把我的網路線從switch拔起來,直接接到中華電信光世代小烏龜 D-Link DSL-7740C 這台上面
因為 IP 其實是小烏龜發的,但是一樣取不到 IP...

經過思考只有這幾種可能性
1. 從Switch到我房間網路孔之間,真的有某些神奇設備阻擋自行接 switch,有辦法查嗎?
2. 中華電信光世代小烏龜 D-Link DSL-7740C 這台被設了某些設定,因為這台還蠻多可以設的,很多我都看不懂XD

因為這台中華電信光世代小烏龜有開 Wifi,所以目前我是找一台 Wifi AP,用 Wifi Bridge Mode,如此可以連無線,這台 Wifi AP 後面的網路孔也可以串接其他有線網路並且正常用 DHCP 取得 IP
分享的文章沒人回應,只好越貼越少
如果妳會設定SWITCH的話,看看那台SWITCH有沒有CONSOLE或COM PORT,買條線連進去看設定。好的SWITCH是不會開WEB讓你去改設定的,只能用CONSOLE或TELNET連進去改。非專業的話,請三思而後行。改壞,被抓或被房東發現步要來找我!
文章分享
評分
評分
複製連結

今日熱門文章 網友點擊推薦!