moso

Respostas no Fórum

Visualizando 9 posts - 1 até 9 (de 9 do total)
  • Autor
    Posts
  • em resposta a: Placa de Rede com chipset Agere System #6323
    moso
    Participante

    Olá skate_forever!

    Podes me mandar por email o et131x.ko.gz que você gerou no Endian 2.4 para eu testar se funciona direto no Endian 2.4.1?

    O endereço é moso at oi.com.br

    Instalei um Ubuntu 10.04.1 Server e peguei o et131x.ko para ver se funcionava no Endian 2.4.1 mas não rolou…

    Deu a seguinte mensagem:

    root@firewall-01:~ # insmod et131x.ko
    insmod: error inserting 'et131x.ko': -1 Invalid module format

    No /var/log/messages apareceu:

    Nov 24 19:04:05 firewall-01 kernel: [ 8403.011615] et131x: disagrees about version of symbol module_layout

    []’s


    Wireguard_webadmin

    Sistema gratuito (Open Source) para gestão de VPN's WireGuard com uma Web interface intuitiva e fácil de usar.

    Principais funcionalidades:

    - Sistema de Firewall completo e flexível.
    - Encaminhamento de portas
    - Suporte a multi usuário com níveis diferentes de acesso
    - Múltiplas instâncias do Wireguard
    - Crypto key routing para configuração de VPN site-to-site

    O projeto é Open Source, fácil de instalar e está disponível em wireguard_webadmin

    em resposta a: Placa de Rede com chipset Agere System #6322
    moso
    Participante

    Olá skate_forever! 🙂

    Aí vai toda informação que consegui (e até onde consegui ir)… 😀

    login as: root
    root@192.168.1.254's password:
    root@firewall-01:~ # efw-upgrade -s
    Please choose the appropriate channel for your environment and hit [ENTER]:
    1) Production (stable releases)
    2) Development (bleeding edge)
    2
    Please enter your username and hit [ENTER]:
    usuario@dominio.com.br

    Updating cache... ############################# [100%]

    Fetching information for 'efw-community'...
    -> http://endian@supernicolini.com.br:*@updates.endian.org/devel/repodata/repomd.xml
    repomd.xml ############################# [ 50%]
    -> http://endian@supernicolini.com.br:*@updates.endian.org/devel/repodata/filelists.xml.gz
    -> http://endian@supernicolini.com.br:*@updates.endian.org/devel/repodata/primary.xml.gz
    filelists.xml.gz ############################# [ 75%]
    primary.xml.gz ############################# [100%]

    Updating cache... ############################# [100%]

    Channels have no new packages.
    Saving cache...

    Loading cache...
    Updating cache... ############################ [100%]

    Computing transaction...
    No interesting upgrades available.
    /etc/upgrade/upgrade.d/migration:
    ---
    Found: 0
    OK: 0
    root@firewall-01:~ # reboot

    Broadcast message from root (pts/0) (Wed Nov 24 16:43:36 2010):

    The system is going down for reboot NOW!

    *** primeiro problema ***

    login as: root
    root@192.168.1.254's password:
    Last login: Wed Nov 24 16:40:19 2010 from 192.168.1.222
    root@firewall-01:~ # smart install kernel-PAE
    Loading cache...
    Updating cache... ############################ [100%]

    error: 'kernel-PAE' matches no packages. Suggestions:
    error: kernel-3:2.6.32.25-57.e40@i586

    *** tentei… ***

    root@firewall-01:~ # smart install kernel-3:2.6.32.25-57.e40@i586
    Loading cache...
    Updating cache... ####################################################################################### [100%]

    warning: kernel-3:2.6.32.25-57.e40@i586 is already installed
    Computing transaction...

    *** baixei os fontes do driver e dos EFW 2.4 e 2.4.1 para /root/temp ***

    root@firewall-01:~ # mkdir temp
    root@firewall-01:~ # cd temp
    root@firewall-01:~/temp # ls -l
    total 1036608
    -rw-r--r-- 1 root root 515215702 Nov 23 19:16 EFW-COMMUNITY-2.4-devel-srpms.tar.gz
    -rw-r--r-- 1 root root 544790494 Nov 23 16:57 EFW-COMMUNITY-2.4.1-devel-srpm-rpms.tar.gz
    -rw-r--r-- 1 root root 424320 Nov 23 16:11 et131x-1.2.3-3.tar.gz

    *** descompactando os arquivos… ***

    root@firewall-01:~/temp # tar zxf EFW-COMMUNITY-2.4-devel-srpms.tar.gz
    root@firewall-01:~/temp # tar zxf EFW-COMMUNITY-2.4.1-devel-srpm-rpms.tar.gz
    root@firewall-01:~/temp # tar zxf et131x-1.2.3-3.tar.gz

    root@firewall-01:~/temp # cd EFW-COMMUNITY-2.4.1-201011120951/
    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951 # ls -l
    total 240
    drwxr-xr-x 2 root root 4096 Nov 12 12:25 DEVEL_RPMS
    drwxr-xr-x 2 root root 20480 Nov 12 10:11 RPMS
    drwxr-xr-x 2 root root 16384 Nov 12 12:38 SRPMS
    -rw-r--r-- 1 root root 198759 Nov 12 12:28 installer-2.4.1.tar.gz
    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951 # cd DEVEL_RPMS/
    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # ls
    autoconf-2.59-7.endian0.noarch.rpm m4-1.4.3-0.endian0.i386.rpm
    automake-1.9.5-0.endian0.noarch.rpm make-3.81-3.endian0.i586.rpm
    binutils-2.15.92.0.2-25.endian2.i586.rpm man-1.5o2-3.endian1.i386.rpm
    bison-1.875c-2.endian0.i386.rpm nasm-0.98.38-4.endian0.i386.rpm
    build-essential-0.4-endian3.i586.rpm patch-2.5.4-20.endian0.i586.rpm
    cpp-3.4.6-10.endian8.i586.rpm python-setuptools-0.6c9-0.endian2.i586.rpm
    flex-2.5.4a-33.endian0.i386.rpm texinfo-4.8-2.2.endian0.i386.rpm
    gcc-3.4.6-10.endian8.i586.rpm libgcc-3.4.6-10.endian8.i586.rpm
    gcc-c++-3.4.6-10.endian8.i586.rpm libgomp-4.1.2-14.endian1.i586.rpm
    gcc4-4.1.2-14.endian1.i586.rpm libstdc++-3.4.6-10.endian8.i586.rpm
    glibc-kernheaders-2.4-9.1.103.EL.endian1.i586.rpm libstdc++-devel-3.4.6-10.endian8.i586.rpm
    groff-1.18.1.1-5.endian0.i386.rpm

    *** tentando instalar os pacotes… ***

    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # rpm -Uvh binutils-2.15.92.0.2-25.endian2.i586.rpm glibc-kernheaders-2.4-9.1.103.EL.endian1.i586.rpm patch-2.5.4-20.endian0.i586.rpm glibc-headers-2.3.4-2.41.endian8.i386.rpm glibc-extras-2.3.4-2.41.endian8.i386.rpm glibc-devel-2.3.4-2.41.endian8.i386.rpm libgomp-4.1.2-14.endian1.i586.rpm gcc4-4.1.2-14.endian1.i586.rpm make-3.81-3.endian0.i586.rpm cpp-3.4.6-10.endian8.i586.rpm autoconf-2.59-7.endian0.noarch.rpm automake-1.9.5-0.endian0.noarch.rpm m4-1.4.3-0.endian0.i386.rpm libstdc++-devel-3.4.6-10.endian8.i586.rpm
    error: open of glibc-headers-2.3.4-2.41.endian8.i386.rpm failed: No such file or directory
    error: open of glibc-extras-2.3.4-2.41.endian8.i386.rpm failed: No such file or directory
    error: open of glibc-devel-2.3.4-2.41.endian8.i386.rpm failed: No such file or directory

    *** copiei dos fontes do EFW 2.4 os arquivos que faltavam… ***

    root@firewall-01:~/temp # cp ./EFW-COMMUNITY-2.4-201006071652/RPMS/glibc-headers-2.3.4-2.41.endian8.i386.rpm ./EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS/
    root@firewall-01:~/temp # cp ./EFW-COMMUNITY-2.4-201006071652/RPMS/glibc-extras-2.3.4-2.41.endian8.i386.rpm ./EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS/
    root@firewall-01:~/temp # cp ./EFW-COMMUNITY-2.4-201006071652/RPMS/glibc-devel-2.3.4-2.41.endian8.i386.rpm ./EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS/

    *** novo erro… ***

    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # rpm -Uvh binutils-2.15.92.0.2-25.endian2.i586.rpm glibc-kernheaders-2.4-9.1.103.EL.endian1.i586.rpm patch-2.5.4-20.endian0.i586.rpm glibc-headers-2.3.4-2.41.endian8.i386.rpm glibc-extras-2.3.4-2.41.endian8.i386.rpm glibc-devel-2.3.4-2.41.endian8.i386.rpm libgomp-4.1.2-14.endian1.i586.rpm gcc4-4.1.2-14.endian1.i586.rpm make-3.81-3.endian0.i586.rpm cpp-3.4.6-10.endian8.i586.rpm autoconf-2.59-7.endian0.noarch.rpm automake-1.9.5-0.endian0.noarch.rpm m4-1.4.3-0.endian0.i386.rpm libstdc++-devel-3.4.6-10.endian8.i586.rpm
    error: Failed dependencies:
    glibc = 1:2.3.4-2.41.endian8 is needed by glibc-headers-2.3.4-2.41.endian8.i386
    glibc = 1:2.3.4-2.41.endian8 is needed by glibc-devel-2.3.4-2.41.endian8.i386

    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # rpm -qa glibc
    glibc-2.3.4-2.41.endian9

    *** tentei com “–nodeps”… ***

    root@firewall-01:~/temp/EFW-COMMUNITY-2.4.1-201011120951/DEVEL_RPMS # rpm -Uvh binutils-2.15.92.0.2-25.endian2.i586.rpm glibc-kernheaders-2.4-9.1.103.EL.endian1.i586.rpm patch-2.5.4-20.endian0.i586.rpm glibc-headers-2.3.4-2.41.endian8.i386.rpm glibc-extras-2.3.4-2.41.endian8.i386.rpm glibc-devel-2.3.4-2.41.endian8.i386.rpm libgomp-4.1.2-14.endian1.i586.rpm gcc4-4.1.2-14.endian1.i586.rpm make-3.81-3.endian0.i586.rpm cpp-3.4.6-10.endian8.i586.rpm autoconf-2.59-7.endian0.noarch.rpm automake-1.9.5-0.endian0.noarch.rpm m4-1.4.3-0.endian0.i386.rpm libstdc++-devel-3.4.6-10.endian8.i586.rpm --nodeps
    Preparing... ########################################### [100%]
    1:m4 ########################################### [ 7%]
    2:libgomp ########################################### [ 14%]
    3:glibc-extras ########################################### [ 21%]
    4:binutils ########################################### [ 29%]
    5:autoconf ########################################### [ 36%]
    6:glibc-kernheaders ########################################### [ 43%]
    7:libstdc++-devel ########################################### [ 50%]
    8:cpp ########################################### [ 57%]
    9:make ########################################### [ 64%]
    10:patch ########################################### [ 71%]
    11:glibc-headers ########################################### [ 79%]
    12:automake ########################################### [ 86%]
    13:glibc-devel ########################################### [ 93%]
    14:gcc4 ########################################### [100%]

    *** continuando… ***

    root@firewall-01:~/temp/et131x-1.2.3-3 # make
    #@make -C /lib/modules/2.6.32.25-57.e40.i586/build M=/root/temp/et131x-1.2.3-3 modules
    make: *** /lib/modules/2.6.32.25-57.e40.i586/build: No such file or directory. Stop.
    make: *** [modules] Error 2

    root@firewall-01:/lib/modules/2.6.32.25-57.e40.i586 # pwd
    /lib/modules/2.6.32.25-57.e40.i586
    root@firewall-01:/lib/modules/2.6.32.25-57.e40.i586 # ls -l
    total 884
    lrwxrwxrwx 1 root root 46 Nov 24 11:38 build -> ../../../usr/src/kernels/2.6.32.25-57.e40.i586
    drwxr-xr-x 2 root root 4096 Nov 24 11:39 extra
    drwxr-xr-x 9 root root 4096 Nov 11 14:14 kernel
    -rw-r--r-- 1 root root 179057 Nov 24 11:49 modules.alias
    -rw-r--r-- 1 root root 1495 Nov 11 13:20 modules.block
    -rw-r--r-- 1 root root 69 Nov 24 11:49 modules.ccwmap
    -rw-r--r-- 1 root root 144259 Nov 24 11:49 modules.dep
    -rw-r--r-- 1 root root 0 Nov 11 13:20 modules.drm
    -rw-r--r-- 1 root root 73 Nov 24 11:49 modules.ieee1394map
    -rw-r--r-- 1 root root 141 Nov 24 11:49 modules.inputmap
    -rw-r--r-- 1 root root 774 Nov 24 11:49 modules.isapnpmap
    -rw-r--r-- 1 root root 0 Nov 11 13:20 modules.modesetting
    -rw-r--r-- 1 root root 1368 Nov 11 13:20 modules.networking
    -rw-r--r-- 1 root root 74 Nov 24 11:49 modules.ofmap
    -rw-r--r-- 1 root root 34812 Nov 11 13:19 modules.order
    -rw-r--r-- 1 root root 184374 Nov 24 11:49 modules.pcimap
    -rw-r--r-- 1 root root 43 Nov 24 11:49 modules.seriomap
    -rw-r--r-- 1 root root 82971 Nov 24 11:49 modules.symbols
    -rw-r--r-- 1 root root 193135 Nov 24 11:49 modules.usbmap
    lrwxrwxrwx 1 root root 5 Nov 24 11:38 source -> build
    drwxr-xr-x 2 root root 4096 Nov 11 13:20 updates
    drwxr-xr-x 2 root root 4096 Nov 24 11:38 vdso

    Tens alguma idéia de como conseguir compilar o driver?

    []’s

    em resposta a: Placa de Rede com chipset Agere System #6321
    moso
    Participante

    Olá skate_forever! 🙂

    Gostaria de usar o EFW 2.4.1.

    Vou reinstalar ele agora e tentar o seu procedimento passo a passo.

    Assim que tiver os erros eu posto aqui pra ver se você consegue me ajudar.

    Valeu!

    []’s

    em resposta a: Placa de Rede com chipset Agere System #6319
    moso
    Participante

    Olá skate_forever! 🙂

    Tentei pegar arquivos faltantes no EFW-COMMUNITY-2.4.1-devel-srpm-rpms.tar.gz no EFW-COMMUNITY-2.4-devel-srpms.tar.gz mas deu vários erros de dependência e talz, não consegui fazer funcionar.

    Você poderia me enviar o módulo compilado para 2.4 pra ver se funciona direto no 2.4.1?

    Ou talvez você consiga compilar ele no 2.4.1…

    []’s

    em resposta a: Placa de Rede com chipset Agere System #6317
    moso
    Participante

    Olá skate_forever! 🙂

    Estou tentando fazer a mesma coisa no Endian 2.4.1 mas parece que faltam alguns arquivos no EFW-COMMUNITY-2.4.1-devel-srpm-rpms.tar.gz disponível para download… 😛

    Fui tentar instalar o que tinha porém ao executar:

    rpm -Uhv binutils-2.15.92.0.2-25.endian2.i586.rpm glibc-kernheaders-2.4-9.1.103.EL.endian1.i586.rpm patch-2.5.4-20.endian0.i586.rpm libgomp-4.1.2-14.endian1.i586.rpm gcc4-4.1.2-14.endian1.i586.rpm make-3.81-3.endian0.i586.rpm cpp-3.4.6-10.endian8.i586.rpm autoconf-2.59-7.endian0.noarch.rpm automake-1.9.5-0.endian0.noarch.rpm m4-1.4.3-0.endian0.i386.rpm libstdc++-devel-3.4.6-10.endian8.i586.rpm

    eu obtenho o seguinte erro:

    error: Failed dependencies:
    glibc-devel >= 2.2.90-12 is needed by gcc4-4.1.2-14.endian1.i586

    Sabes como posso conseguir fazer funcionar a

    04:00.0 Ethernet controller: Agere Systems ET-131x PCI-E Ethernet Controller (rev 02)

    ???

    []’s

    em resposta a: Ajuda com roteamento no EFW 2.4.1 #6467
    moso
    Participante

    Olá w4rh4ck3r! 🙂

    Obrigado pela dica!

    Porém tem algum detalhe que está me escapando… 😛

    Seria abusar muito pedir para você citar exatamente quais campos alterar e com quais valores?

    Por exemplo, em “if this uplink fails activate” só aparece “Main uplink (main)” (não aparece nada relacionado com a VPN).

    []’s

    em resposta a: Ajuda com roteamento no EFW 2.4.1 #6465
    moso
    Participante

    Olá pessoal!

    Nenhuma idéia de como usar a VPN como “alternativa automática” caso a conexão pela zona laranja pare de funcionar?

    []’s

    em resposta a: Matriz & Filiais: rádio + VPN #6427
    moso
    Participante

    Olá jabinha! 🙂

    Minhas principais dúvidas estão na configuração do Endian…

    Na matriz o Endian terá na zona verde (br0) os endereços 10.0.0.254 e 192.168.19.254; na zona vermelha (ppp0) o endereço do IP fixo da internet; na zona roxa (tap0) a conexão da VPN.

    O Endian da filial terá na zona verde (br0) os endereços 10.1.0.254 e 192.168.19.1; na zona vermelha (ppp0) o endereço do IP fixo da internet; não possui zona roxa mas tem a interface tap1 com um IP fornecido pelo servidor de VPN da matriz.

    Como faço para configurar o Endian de forma que por padrão a comunicação entre a filial e a matriz se dê pelos IPs 192.168.19.0/24 (que estão na zona verde, pela interface br0) e que somente se houver interrupção no link de rádio (rede 192.168.19.0/24) a comunicação passe a ser pela VPN?

    []’s

    em resposta a: Matriz & Filiais: rádio + VPN #6425
    moso
    Participante

    Olá pessoal!

    Alguém aqui no fórum já fez algo parecido com o que eu quero para obter uma espécie de redundância de link entre matriz e filiais?

    []’s

Visualizando 9 posts - 1 até 9 (de 9 do total)