kaotoby wrote:
對了 問一下大大你...(恕刪)
我自己的不會，因為我把SN和pasasword改成和本來ONU一樣的，確定SLID是G.984的GPON pasword
如果SN改不一樣，應該原本SN就洗掉了，但可以自動洗掉也代表可以自動洗回來。不用機房人員操作
反之如果無法洗掉，就不能透過新SN+老password(SLID)更改，需要機房手動清除
個人積分：15828分
文章編號：60766486
個人積分：22分
文章編號：60769441
石光上林 wrote:
我自己的不會，因為...(恕刪)
根據Google出來的百度文庫的各種資料
解釋了GPON各種認證原理
http://wenku.baidu.com/view/9092dc2ef121dd36a22d8242.html
http://wenku.baidu.com/view/da30ba526137ee06eff918d6.html
我所學到的就是
GPON認證市面上主流就2種
1.物理標示認證 (台灣...)
－設備SN (24 byte, 12 ASCII, 前4個字母是廠商標示)
－Password (或稱SLID) (20 byte, 10 ASCII)
－MAC (好像很少人在榜MAC?)
2.邏輯標示認證 (中國自己搞起來的)
－LOID (唯一, 48 byte, 24 ASCII, 不足補0x00)
－LOID Password (24 byte, 12 ASCII, 不足補0x00)
兩個認證的時間點和方式和規格都不同
回到重點
應該把SN和SLID改了就可以認證了 (不過這在SFP模組上比較難一點點, 這周末應該可以來實驗)
至於ALU的板本控制...中華你早該關了(不知到台中這邊的機房關版控了沒...)
不然就直接打去機房註冊?(最終手段)
我擔心註冊完新的把I-040GW的註冊給刪了...
我大陸的朋友換ONU都是直接買新的機器
機器打上LOID和LOID密碼註冊...就開通了
然後舊的機器也可以用(阿沒綁SN當然能用...)
個人積分：15828分
文章編號：60795858
kaotoby wrote:
根據Google出...(恕刪)
今天終於搞定上海貝爾I-240W，感謝CHINADSL上的朋友幫忙搞定了修改eqid和eqvid
我們將eqid修改成I040GW，將eqvid修改成3FE99997HGW001
然後剛好機房最近升版，導致我斷線，去電要求關閉版本下載DLSW，但SWVERPLND還是開的
這種情況下換上BCM68380公版不會拿到gem port
但換上修改後的I-240W，3FE55921AAAA就可以正常拿到gem port
只是bridge讓後方撥號、IPTV這兩個服務需要額外綁住lan port
算是broadcom上面小小不方便
但ipv6 prefix delegation、radvd都正常運作，後方設備也可以撥號，這樣就足夠了
北分腺萎的裝成蟲最後還是輸給我了 哈哈
#ONT/system/shell>ifconfig -a
bcmsw Link encap:Ethernet HWaddr 00:12:BF:00:00:01
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23365 errors:0 dropped:0 overruns:0 frame:0
TX packets:20238 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2681487 (2.5 MiB) TX bytes:6115413 (5.8 MiB)
Base address:0xffff
br0 Link encap:Ethernet HWaddr 88:03:55:F9:C4:80
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:b011:4002:18bb:4ef2:bfff:fef9:c480/64 Scope:Global
inet6 addr: fe80::4ef2:bfff:fef9:c480/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:281790 errors:0 dropped:0 overruns:0 frame:0
TX packets:344148 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:178980705 (170.6 MiB) TX bytes:409019425 (390.0 MiB)
brdg Link encap:Ethernet HWaddr 00:12:BF:00:00:03
inet6 addr: fe80::219:c7ff:fe00:3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:236 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14438 (14.0 KiB) TX bytes:1344 (1.3 KiB)
eth0 Link encap:Ethernet HWaddr 88:03:55:F9:C4:80
inet6 addr: fe80::4ef2:bfff:fef9:c480/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15433 errors:0 dropped:0 overruns:0 frame:0
TX packets:14549 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1322484 (1.2 MiB) TX bytes:5632453 (5.3 MiB)
eth1 Link encap:Ethernet HWaddr 88:03:55:F9:C4:80
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1300 errors:0 dropped:0 overruns:0 frame:0
TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:96326 (94.0 KiB) TX bytes:96637 (94.3 KiB)
eth2 Link encap:Ethernet HWaddr 88:03:55:F9:C4:80
inet6 addr: fe80::4ef2:bfff:fef9:c480/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1300 errors:0 dropped:0 overruns:0 frame:0
TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:96326 (94.0 KiB) TX bytes:96637 (94.3 KiB)
eth3 Link encap:Ethernet HWaddr 88:03:55:F9:C4:80
inet6 addr: fe80::4ef2:bfff:fef9:c480/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:236 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14438 (14.0 KiB) TX bytes:1344 (1.3 KiB)
ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1452 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lan1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lan2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lan3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1662 errors:0 dropped:0 overruns:0 frame:0
TX packets:1662 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:349534 (341.3 KiB) TX bytes:349534 (341.3 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:114.25.227.194 P-t-P:168.95.98.254 Mask:255.255.255.255
inet6 addr: 2001:b011:4002:4c0:f93c:bb39:cbe0:b19d/64 Scope:Global
inet6 addr: fe80::f93c:bb39:cbe0:b19d/10 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1480 Metric:1
RX packets:338142 errors:0 dropped:0 overruns:0 frame:0
TX packets:270688 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:400586724 (382.0 MiB) TX bytes:176860370 (168.6 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wan0 Link encap:Ethernet HWaddr 88:03:55:F9:C4:85
inet6 addr: fe80::4ef2:bfff:fef9:c485/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1300 errors:0 dropped:0 overruns:0 frame:0
TX packets:642 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:96326 (94.0 KiB) TX bytes:96637 (94.3 KiB)
wan0.v345 Link encap:Ethernet HWaddr 88:03:55:F9:C4:85
inet6 addr: fe80::4ef2:bfff:fef9:c485/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:338215 errors:0 dropped:0 overruns:0 frame:0
TX packets:270766 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:404397314 (385.6 MiB) TX bytes:183689551 (175.1 MiB)
wl0 Link encap:Ethernet HWaddr 88:03:55:F9:C4:84
inet6 addr: fe80::4ef2:bfff:fef9:c484/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:1 overruns:0 frame:51967
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:84
wl0.1 Link encap:Ethernet HWaddr 88:03:55:F9:C4:85
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:51967
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wl0.2 Link encap:Ethernet HWaddr 88:03:55:F9:C4:86
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:51967
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wl0.3 Link encap:Ethernet HWaddr 88:03:55:F9:C4:87
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:51967
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
附上ALU AONT的mibdump
附加壓縮檔: 201607/mobile01-79d1d3a07acb17b377ae45a97648fb43.zip
順帶一提這個firmare是從丹麥電信抓的，只是不知道為什可能地區設定刷不掉，或是我還不會操作EEPROM的刷寫
才保留成中國聯通的。
3FE55921AAAA是在ALU ISAM 5.X版本中的國際板ONT，所以OLT每次進版都會發布相對應版本的ONT firmware
也许是一场难圆的梦
一场没有结局的梦
多少的笑语飞散在风中
又围绕在我耳边
個人積分：15828分
文章編號：63173796
kaotoby wrote:
根據Google出...(恕刪)
中華電信的陷阱 或是電信研究所的網管出錯
出去的路有兩條，不同filter，所以不會有規則重疊的現象
一個filter tag 0x8100,一個filter untag 0x0800
回來得路程就有問題了，兩條路同樣都是filter tag 0x8100
一個行為是output tag 另一個行為是output untag(pup tag)
這會讓ONU必須要建立兩條WAN在UI上才可以使用，而且是隨機使用一條
因為每次開機建立rule順序不同，所以每次隨機一個WAN去回路徑相同，該WAN啟用
如果只建立tag or untag任何一個WAN，那每次開機/插拔光纖皆有機率FAIL WAN。
這甚麼意思?
白話一點，有人把一台switch的一個port的access vlan和trunk vlan去allow同一個vlan id
上一次沒有仔細看hit 0的rule，這次仔細看才知道 為什麼之前有時候連不上....
看看莊成bug先生要當植白HOLO到何時?
# vlanctl --if gpon0.0 --tx --tags 1 --show-table
VLAN Rule Table : gpon0.0, Tx, nbrOfTags 1, default DROP
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : TX, 1 tag(s)
Tag Rule ID : 0
Rx VLAN Device : DEFAULT
Filters
Rx REALIF :
Tx VLANIF : veip0
EtherType : 0x00008100
VLAN Tag 0 : pbits -, cfi -, vid 4082, (tci 0x0FFF/0x0FF2), ether -
Commands
00:[SET_PBITS, 0x00000000, 0x00000000]
01:[SET_VID, 0x00000058, 0x00000000]
Rule Type : Flow
Hit Count : 2753
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : TX, 1 tag(s)
Tag Rule ID : 1
Rx VLAN Device : DEFAULT
Filters
Rx REALIF :
Tx VLANIF : veip0
EtherType : 0x00008100
VLAN Tag 0 : pbits -, cfi -, vid 0, (tci 0x0FFF/0x0000), ether 0x00008863
Commands
00:[SET_PBITS, 0x00000000, 0x00000000]
01:[SET_VID, 0x00000058, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : TX, 1 tag(s)
Tag Rule ID : 2
Rx VLAN Device : DEFAULT
Filters
Rx REALIF :
Tx VLANIF : veip0
EtherType : 0x00008100
VLAN Tag 0 : pbits -, cfi -, vid 0, (tci 0x0FFF/0x0000), ether 0x00008864
Commands
00:[SET_PBITS, 0x00000000, 0x00000000]
01:[SET_VID, 0x00000058, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
# vlanctl --if gpon0.0 --tx --tags 0 --show-table
VLAN Rule Table : gpon0.0, Tx, nbrOfTags 0, default DROP
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : TX, 0 tag(s)
Tag Rule ID : 0
Rx VLAN Device : DEFAULT
Filters
Rx REALIF :
Tx VLANIF : veip0
EtherType : 0x00008863
Commands
00:[PUSH_TAG, 0x00008100, 0x00000001]
01:[SET_PBITS, 0x00000000, 0x00000000]
02:[SET_VID, 0x00000058, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : TX, 0 tag(s)
Tag Rule ID : 1
Rx VLAN Device : DEFAULT
Filters
Rx REALIF :
Tx VLANIF : veip0
EtherType : 0x00008864
Commands
00:[PUSH_TAG, 0x00008100, 0x00000001]
01:[SET_PBITS, 0x00000000, 0x00000000]
02:[SET_VID, 0x00000058, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
# vlanctl --if gpon0.0 --rx --tags 1 --show-table
VLAN Rule Table : gpon0.0, Rx, nbrOfTags 1, default DROP
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : RX, 1 tag(s)
Tag Rule ID : 0
Rx VLAN Device : veip0
Filters
VlanDev MacAddr : No
VLAN Tag 0 : pbits 0, cfi -, vid 88, (tci 0xEFFF/0x0058), ether -
Commands
00:[SET_VID, 0x00000FF2, 0x00000000]
01:[SET_ETHERTYPE, 0x00008100, 0x00000000]
Rule Type : Flow
Hit Count : 1656
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : RX, 1 tag(s)
Tag Rule ID : 1
Rx VLAN Device : veip0
Filters
VlanDev MacAddr : No
VLAN Tag 0 : pbits 0, cfi -, vid 88, (tci 0xEFFF/0x0058), ether -
Commands
00:[POP_TAG, 0x00000000, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : RX, 1 tag(s)
Tag Rule ID : 2
Rx VLAN Device : veip0
Filters
VlanDev MacAddr : No
VLAN Tag 0 : pbits 0, cfi -, vid 88, (tci 0xEFFF/0x0058), ether -
Commands
00:[POP_TAG, 0x00000000, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : RX, 1 tag(s)
Tag Rule ID : 3
Rx VLAN Device : veip0
Filters
VlanDev MacAddr : No
VLAN Tag 0 : pbits 0, cfi -, vid 88, (tci 0xEFFF/0x0058), ether -
Commands
00:[SET_VID, 0x00000000, 0x00000000]
01:[SET_ETHERTYPE, 0x00008100, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
===> gpon0.0 (ONT) : RX, 1 tag(s)
Tag Rule ID : 4
Rx VLAN Device : veip0
Filters
VlanDev MacAddr : No
VLAN Tag 0 : pbits 0, cfi -, vid 88, (tci 0xEFFF/0x0058), ether -
Commands
00:[SET_VID, 0x00000000, 0x00000000]
01:[SET_ETHERTYPE, 0x00008100, 0x00000000]
Rule Type : Flow
Hit Count : 0
--------------------------------------------------------------------------------
# vlanctl --if gpon0.0 --rx --tags 0 --show-table
VLAN Rule Table : gpon0.0, Rx, nbrOfTags 0, default DROP
No entries found
--------------------------------------------------------------------------------
也许是一场难圆的梦
一场没有结局的梦
多少的笑语飞散在风中
又围绕在我耳边
個人積分：79分
文章編號：63695269
個人積分：15828分
文章編號：63697160
jeremy9678 wrote:
請問台灣中華光世代...(恕刪)
如果你要使用SFP，記得先請他把profile換成I040GB/GA或是I040GW的bridge mode
這樣才不會使用veip, 使用舊的pptp。sfp onu都是pptp軟體接口
再來，請他關閉兩個東西就好了
isadmin@ALU7360>configure>equipment>ont#configure equipment ont interf
ace 1/1/1/1/128 subslocid 289Y006500 sw-ver-pland disabled iphc-allowed enable ?
[no] sw-dnload-version: standby ONT software version number to be downloaded. If
sw-ver-pland is set to delayactivate, sw-dnload-version
cannot be set to disabled.
default = DISABLED
[no] plnd-var : planned variant of the ONT hardware version.Use DO for
Data-only ONTs,SIP for SIP ONTs,H.248 for MEGACO ONTs
default = ""
sw-ver-pland disabled這個關閉，sw-dnload-version應該跟著關閉
在手動關調plnd-var
然後請mikrotik協助教你修改gpon password
上面例子為電路編號 289Y006500的電路
假設電路編號某些區域是3589Y006500，就是輸入589Y006500，自行刪減第一位數
但可能要輸入hex，自行搜索ascii轉hex
289Y006500就變成
32383959303036353030
另外有人可能不會敲CLI，雖身為網管以不熟悉CLI為恥，但還是放上UI設定教學
附加壓縮檔: 201703/mobile01-cd9e8f3c871527b96f186df87bf11bf0.zip
也许是一场难圆的梦
一场没有结局的梦
多少的笑语飞散在风中
又围绕在我耳边
個人積分：79分
文章編號：63697502
個人積分：15828分
文章編號：63697596
個人積分：79分
文章編號：63700570
個人積分：15828分
文章編號：63704274
tsengleoo wrote:
了解，但前面那些指令應是給7360用的吧
只怕機房端是用7342的OLT...
到時候就用不上的吧？
還是說7342的話更簡單，只要改網管為橋接模式？
指令只有ISAM共板的寫得比較好，承襲自7302 7330 來的
7342如果只有TL1語法，用起來十分困難，貝爾ALU台灣也沒有人會用，如果有升版到4.8 應該CLI還能使用一部分
AMS 5520網管UI是差不多的
7342實際上沒有router mode的GPON，也就是沒有implement G.988，沒有veip端口
7342是一個孤立出來的repo，軟體也在4.8以後就沒有在大量修正問題了，一個原因是對岸7342在退場了
也许是一场难圆的梦
一场没有结局的梦
多少的笑语飞散在风中
又围绕在我耳边
