Proszę o informację jak mam skonfigurować na routerze TP-LINK TL-WR842ND z oprogramowaniem Gargoyle połączenie z modemem Hyawei E3131 i siecią Aero 2 ??
Poczytaj:
dane wstawiasz pod swojego operatora.
Poczytałem, ustawoiłem tak jak pisze i nic.
Zaznaczam że mam TP-Link TL-WR842N/ND v1. na Gargoyle wersja1.6.2.2 (r42647)
Co masz w konfiguracji wan-owej potem w statusie i w logach router-a. Wrzuć jakieś obrazki na forum.
A może być problem w oprogramowaniu modemu bo to jest zwykły zakupiony w Play - nie żaden Hilink ??
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 12.110000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 12.120000] usbcore: registered new interface driver ums-usbat
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 12.360000] scsi0 : usb-storage 1-1:1.0
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 12.400000] scsi1 : usb-storage 1-1:1.1
Jan 1 01:00:45 Gargoyle kern.notice kernel: [ 13.360000] scsi 0:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
Jan 1 01:00:45 Gargoyle kern.notice kernel: [ 13.400000] scsi 1:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2
Jan 1 01:00:45 Gargoyle kern.notice kernel: [ 13.410000] sd 1:0:0:0: [sda] Attached SCSI removable disk
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 33.810000] Loading modules backported from Linux version master-2014-05-22-0-gf2032ea
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 33.820000] Backport generated by backports.git backports-20140320-37-g5c33da0
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.020000] cfg80211: Calling CRDA to update world regulatory domain
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.020000] cfg80211: World regulatory domain updated:
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.030000] cfg80211: DFS Master region: unset
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.030000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.040000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.050000] cfg80211: (5140000 KHz - 5860000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 34.340000] NET: Registered protocol family 10
Jan 1 01:00:45 Gargoyle kern.warn kernel: [ 35.740000] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: EEPROM regdomain: 0x0
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: EEPROM indicates default country code should be used
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: doing EEPROM country->regdmn map search
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: country maps to regdmn code: 0x3a
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: Country alpha2 being used: US
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.760000] ath: Regpair used: 0x3a
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.770000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan 1 01:00:45 Gargoyle kern.debug kernel: [ 35.780000] Registered led device: ath9k-phy0
-------------------
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.780000] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xb0000000, irq=40
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.780000] cfg80211: Calling CRDA for country: US
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.790000] cfg80211: Regulatory domain changed to country: US
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.800000] cfg80211: DFS Master region: unset
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.800000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.810000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 35.820000] cfg80211: (5140000 KHz - 5860000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.220000] RPC: Registered named UNIX socket transport module.
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.220000] RPC: Registered udp transport module.
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.230000] RPC: Registered tcp transport module.
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.230000] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.820000] PPP generic driver version 2.4.2
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.970000] tun: Universal TUN/TAP device driver, 1.6
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 36.980000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 37.110000] GRE over IPv4 demultiplexor driver
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 37.140000] GRE over IPv4 tunneling driver
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 37.530000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 37.640000] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 38.260000] NET: Registered protocol family 24
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 38.430000] nf_conntrack version 0.5.0 (455 buckets, 1820 max)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 38.950000] PPTP driver version 0.8.5
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 39.910000] xt_time: kernel timezone is -0000
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 40.820000] Hooked IMQ after mangle on PREROUTING
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 40.820000] Hooked IMQ after nat on POSTROUTING
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 40.830000] IMQ driver loaded successfully. (numdevs = 2, numqueues = 1)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 41.070000] Netfilter messages via NETLINK v0.30.
Jan 1 01:00:45 Gargoyle kern.notice kernel: [ 41.340000] ip_set: protocol 6
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.100000] usbcore: registered new interface driver cdc_acm
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.110000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.280000] usbcore: registered new interface driver usblp
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.310000] usbcore: registered new interface driver usbserial
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.320000] USB Serial support registered for generic
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.320000] usbcore: registered new interface driver usbserial_generic
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.330000] usbserial: USB Serial Driver core
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.440000] USB Serial support registered for Sierra USB modem
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.440000] usbcore: registered new interface driver sierra
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.450000] sierra: v.1.7.40:USB Driver for Sierra Wireless USB modems
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.480000] usbcore: registered new interface driver sierra_net
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.750000] usbcore: registered new interface driver cdc_wdm
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.780000] usbcore: registered new interface driver cdc_ether
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 42.960000] usbcore: registered new interface driver cdc_ncm
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.050000] usbcore: registered new interface driver qmi_wwan
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.080000] usbcore: registered new interface driver rndis_host
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.190000] USB Serial support registered for GSM modem (1-port)
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.190000] usbcore: registered new interface driver option
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.200000] option: v0.7.2:USB Driver for GSM modems
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.230000] USB Serial support registered for Qualcomm USB modem
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.230000] usbcore: registered new interface driver qcserial
Jan 1 01:00:45 Gargoyle kern.info kernel: [ 43.400000] fuse init (API version 7.18)
Jan 1 01:00:50 Gargoyle kern.info kernel: [ 50.310000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 01:00:52 Gargoyle kern.info kernel: [ 52.430000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 01:00:52 Gargoyle kern.info kernel: [ 52.430000] device eth0 entered promiscuous mode
Jan 1 01:00:52 Gargoyle kern.info kernel: [ 52.440000] ADDRCONF(NETDEV_UP): br-lan: link is not ready
Jan 1 01:00:52 Gargoyle daemon.notice netifd: Interface 'lan' is now up
Jan 1 01:00:52 Gargoyle daemon.notice netifd: Interface 'loopback' is now up
Jan 1 01:00:52 Gargoyle kern.info kernel: [ 52.450000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jan 1 01:00:52 Gargoyle user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_3.3.8_ehci_hcd Product=Generic_Platform_EHCI_Controller Serial=ehci-platform
Jan 1 01:00:52 Gargoyle user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.260000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.270000] device wlan0 entered promiscuous mode
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.600000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.610000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.620000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 1 01:00:58 Gargoyle kern.info kernel: [ 58.620000] ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Jan 1 01:01:00 Gargoyle kern.info kernel: [ 60.610000] br-lan: port 2(wlan0) entered forwarding state
Jan 1 01:01:01 Gargoyle daemon.info hostapd: wlan0: STA 00:19:d2:2a:f5:d1 IEEE 802.11: authenticated
Jan 1 01:01:01 Gargoyle daemon.info hostapd: wlan0: STA 00:19:d2:2a:f5:d1 IEEE 802.11: associated (aid 1)
Ok. Dziękuje - działa.
Tylko teraz drugi problem: jak zersetować połączenie na aero2? Podobno jakieś plugin czy skrypt ale nie mam pojecia jak i co ?
Proszę o dalsze wskazówki.
Zrestartować urządzenie możesz z poziomu Gui . Wchodząc w System -restart i wybierasz zaplanowany restart o ile o takie rozwiązanie Ci chodziło
Nie, chodzi mi o zresetowanie połączenia po wpisaniu kodu captcha. Podobno można jakiś automat zastosować :-[ ale nie mam w tej kwestii pojecia.