Thanks Thanks:  16
Likes Likes:  9
Dislikes Dislikes:  0
Page 12 of 32 FirstFirst ... 2891011121314151622 ... LastLast
Results 166 to 180 of 471

Thread: Server cccam pe router wl500g ...

  1. #166
    Standard RSP member
    Join Date
    09 Sep 2007
    Posts
    161
    Mentioned
    0 Post(s)
    Rep Power
    62

    Default

    Am incercat si eu un upgrade de firmware la un topex premium de la openwrt kamikaze (Openwrt 2.4.35.4) la backfire din interfata luci sectiunea firmware.Am selectat imaginea backfire (openwrt-brcm47xx-squashfs.trx) a incarcat-o in memorie i am dat proceed si pulseaza ledul de power.Am asteptat dar nu se mai intampla nimik. Poate cineva sa ma ajute va rog? Multumesc anticipat!

  2. #167
    Golden Member
    Join Date
    05 Sep 2007
    Posts
    812
    Mentioned
    0 Post(s)
    Rep Power
    66

    Default

    Pai intra in safe mode si pune imaginea cu firmware restoration

  3. #168
    Standard RSP member
    Join Date
    09 Sep 2007
    Posts
    161
    Mentioned
    0 Post(s)
    Rep Power
    62

    Default

    Usor de zis , dar cum. Sunt incepator si as aprecia foarte mult daca ma poti ajuta step by step.

    ---------- Post added at 19:02 ---------- Previous post was at 17:08 ----------

    Am rezolvat.THX resofty

  4. #169
    Standard RSP member
    Join Date
    09 Sep 2007
    Posts
    161
    Mentioned
    0 Post(s)
    Rep Power
    62

    Default

    Ce versiune de kernel este mai buna pentru cccam/oscam 2.4 sau 2.6 (openwrt backfire)?Stie cineva daca functioneaza cccam sau oscam pe ddwrt sau oleg?
    Multumesc!

  5. #170
    Golden Member
    Join Date
    05 Sep 2007
    Posts
    812
    Mentioned
    0 Post(s)
    Rep Power
    66

    Default

    Pe 2.4 merg versiunile pana in 2.1.1
    pe 2.6 merg toate versiunile , vezi sa folosesti librariile care trebuie.
    Merge si pe ddwrt si pe oleg.

    PS: documentarie gasesti aici
    http://www.sateliti.info/showthread.php?t=14842
    si aici
    http://www.sateliti.info/showthread.php?t=8573

  6. #171
    Member Beginner
    Join Date
    13 Jul 2007
    Posts
    17
    Mentioned
    0 Post(s)
    Rep Power
    0

    Default

    am incercat si eu sa pun cccam 2.14 pe un topex aka asus wl500gp v1 cu backire pe el si m-am impotmolit.
    iata ce am facut am pus cccam.mipsel in /bin am pus librariile alea noi de pe forum in lib, cccam.cfg in etc si asa arata scriptul de start

    #!/bin/sh

    if [ -n "`pidof CCcam.mipsel`" ] ; then
    killall CCcam.mipsel
    fi

    #sleep 1
    #export LD_PRELOAD=/lib/ld.so.1:/lib/libcrypt.so.1:/lib/libstdc++.so.6:/lib/libm.so.6://lib/libc.so.6:/lib/libgcc_s.so.1:/lib/libpthread.so.0:/lib/libnss_dns.so.2:/lib/libresolv.so.2
    #export LD_LIBRARY_PATH=/lib
    export LD_LIBRARY_PATH=/lib
    #sleep 1
    #killall logger syslogd klogd
    sleep 1
    /bin/CCcam.mipsel -C /etc/CCcam.cfg

    cand pornesc din putty scripul apare procesul la processes in luci dar daca inchid putty se inchide si procesul
    in system log zice asa
    "OpenWrt user.info kernel: FPU emulator disabled, make sure your toolchainwas compiled with software floating point support (soft-float)"

    ce gresesc?

  7. #172
    Member Beginner
    Join Date
    22 Feb 2007
    Posts
    22
    Mentioned
    0 Post(s)
    Rep Power
    0

    Default

    Quote Originally Posted by guru69 View Post
    /bin/CCcam.mipsel -C /etc/CCcam.cfg
    incearca, pentru a face rezident:

    /bin/CCcam.mipsel & -C /etc/CCcam.cfg

    sau

    /bin/CCcam.mipsel -C /etc/CCcam.cfg &

  8. #173
    Member Beginner
    Join Date
    13 Jul 2007
    Posts
    17
    Mentioned
    0 Post(s)
    Rep Power
    0

    Default

    Quote Originally Posted by @teddy View Post
    incearca, pentru a face rezident:

    /bin/CCcam.mipsel & -C /etc/CCcam.cfg

    sau

    /bin/CCcam.mipsel -C /etc/CCcam.cfg &
    ok cu variana a doua ramane rezident cu un cpu usage de peste 80% dar tot nu merge si tot acelasi mesaj il gasesc in system log

  9. #174
    Member Beginner
    Join Date
    13 Jul 2007
    Posts
    17
    Mentioned
    0 Post(s)
    Rep Power
    0

    Default

    chiar nu stie nimeni ce-am facut gresit?

  10. #175
    Happy fery21's Avatar
    Join Date
    18 Feb 2008
    Location
    Big Bang
    Posts
    2,460
    Mentioned
    7 Post(s)
    Rep Power
    77

    Default

    Quote Originally Posted by guru69 View Post
    ok cu variana a doua ramane rezident cu un cpu usage de peste 80% dar tot nu merge si tot acelasi mesaj il gasesc in system log
    mi se pare normal sa ai erroare nu mai spatiu!! la backfire
    pune boot de pe stick

    -/bin/CCcam.mipsel -C /etc/CCcam.cfg & e cu boot din bin
    -opt/var/bin/CCcam.mipsel -C /etc/CCcam.cfg & boot de pe stick
    ..::EGAMI TEAM::..

  11. #176
    Member Beginner
    Join Date
    13 Jul 2007
    Posts
    17
    Mentioned
    0 Post(s)
    Rep Power
    0

    Default

    o sa incerc si cu stick
    dar credeam ca pe asta premium merge si fara stick

  12. #177
    Standard RSP member
    Join Date
    09 Feb 2007
    Location
    Bucharest
    Posts
    97
    Mentioned
    5 Post(s)
    Rep Power
    63

    Default MAC si IP Filtering ?

    Salutare!

    Am un router Topex varianta Deluxe si cu Cccam+DDWrt kamikaze dupa tutorialul lui Resofty. In spatele lui (in LAN) am o mini retea vreo 5 calcuri (ale mele si a catorva vecini).
    Din motive de securitate am DHCP dezactivat in reteaua Interna (atat LAN cat si WLAN).
    Doresc sa impun urmatoarele: sa aibe access la internet DOAR cei care au IPuri date (impuse) de mine si care au DOAR MACurile aferente fiecaruia.
    Cu alte cuvinte daca schimba IPul, sa nu-i mai mearga internetul SAU daca schimba MACul, de asemenea sa nu-i mai mearga Internetul, mai mult: Daca are un IP care nu este "legat" de MACul corect sa nu-i mai merga Internetul. In LAN se pot vedea...nu mai intereseaza asta, este vorba doar de iesire pe Internet.
    Tin sa precizez ca NU stiu Linux insa stiu sa caut pe Google!
    Iata ce am gasit ca o posibila rezolvare:
    In fisierul: /etc/firewall.user se adauga urmatoarele:

    # Blocare tot trafic catre WAN
    iptables -A forwarding_rule -j DROP
    # Reguli Acceptare acess si legare IP de un anumit MAC - nr1
    iptables -A forwarding_rule -d 192.168.0.10 -j ACCEPT
    iptables -A forwarding_rule -s 192.168.0.10 -m mac --mac-source 00:01:02:F2:E7:EH - j ACCEPT
    # Reguli Acceptare acess si legare IP de un anumit MAC - nr2
    iptables -A forwarding_rule -d 192.168.0.11 -j ACCEPT
    iptables -A forwarding_rule -s 192.168.0.11 -m mac --mac-source 00:00:12:CF:E3:2D - j ACCEPT

    etc

    Doresc sa inreb cunoascatorii daca fac vreo prostie folosind liniile de mai sus, si daca liniile fac ceea ce vreau eu sa faca!

    Multumesc

  13. #178
    Happy fery21's Avatar
    Join Date
    18 Feb 2008
    Location
    Big Bang
    Posts
    2,460
    Mentioned
    7 Post(s)
    Rep Power
    77

    Default

    In firewall.user blochezi portile nu si useri nedoriti. parca pe dd-wrt e posibil si limita de banda pe fiecare ip nu? sau gresesc?
    ..::EGAMI TEAM::..

  14. #179
    Golden Member
    Join Date
    05 Sep 2007
    Posts
    812
    Mentioned
    0 Post(s)
    Rep Power
    66

    Default

    Configuratia arata bine acu nu stiu cat de functionala e , eu as fi facut altfel:



    iptables -A forwarding_rule -i br0 -s 192.168.0.10 -m mac --mac-source 00:01:02:F2:E7:EH - j ACCEPT
    iptables -A forwarding_rule -i br0 -s 192.168.0.11 -m mac --mac-source 00:00:12:CF:E3:2D - j ACCEPT
    iptables -A forwarding_rule -i br0 -j DROP

  15. #180
    Standard RSP member
    Join Date
    09 Feb 2007
    Location
    Bucharest
    Posts
    97
    Mentioned
    5 Post(s)
    Rep Power
    63

    Default

    Quote Originally Posted by resofty View Post
    Configuratia arata bine acu nu stiu cat de functionala e , eu as fi facut altfel:
    iptables -A forwarding_rule -i br0 -s 192.168.0.10 -m mac --mac-source 00:01:02:F2:E7:EH - j ACCEPT
    iptables -A forwarding_rule -i br0 -s 192.168.0.11 -m mac --mac-source 00:00:12:CF:E3:2D - j ACCEPT
    iptables -A forwarding_rule -i br0 -j DROP
    Multumesc Resofty.

    Din ce observ regula DROP generala ai pus-o la urma. Este corect asa sau nu are importanta ca pozitie in fisier.
    Mai vad ca ai folosit br0 si eu am urmatoarele:

    Raw Information
    WAN Interface
    eth0.1 Link encap:Ethernet HWaddr 00:15:F2:77:CD:77
    inet addr:10.88.33.15 Bcast:10.88.33.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    LAN Interface
    br-lan Link encap:Ethernet HWaddr 00:15:F2:77:CD:77
    inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    Interface LOOPBACK
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1

    Wireless Interface
    wl0 IEEE 802.11-DS ESSID:""
    Mode:Managed Channel:0 Access Point: Not-Associated
    Bit Rate:54 Mb/s Tx-Power:32 dBm

    Este corect "br0" sau "br-lan" ? Sau "br0" = "br-lan" + "wl0" ?

    Celelalte reguli de Port forwarding raman valabile ?
    ### Open port to WAN
    ## -- This allows port 22 to be answered by (dropbear on) the router
    iptables -t nat -A prerouting_wan -p tcp --dport 22 -j ACCEPT
    iptables -A input_wan -p tcp --dport 22 -j ACCEPT
    ## -- This allows port 12000 to be answered by (dropbear on) the router
    iptables -t nat -A prerouting_wan -p tcp --dport 12000 -j ACCEPT
    iptables -A input_wan -p tcp --dport 12000 -j ACCEPT

    Cum fac ca un port intern sa fie forwardat catre alt port diferit ca numar?
    Deci daca am FTP de la 192.168.0.10:21 sa-l pot accesa din WAN pe portul 8001 (host_dyndns:8001 ?

Page 12 of 32 FirstFirst ... 2891011121314151622 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •