qualche novita' interessante

74 views
Skip to first unread message

Maurizio Marini

unread,
Jul 24, 2012, 5:04:03 PM7/24/12
to pivel...@googlegroups.com
Grazie al contributo di un amico che ha postato su altri forum, sono venuto a conoscenza della possibilita' di attivare un tunnel ppoe da dietro il router di alice.
In pratica, qualsiasi host capace di attivare una connessione pppoe, behind router, quindi con ip nattato 192.168.1.x, alzando (/sbin/ifup) una connessione pppoe si vede assegnato un ip pubblico sulla ppp0.
Ecco qua:

[code]
** Summary of what you entered **

Ethernet Interface: eth0
User name:          pippo
Activate-on-demand: No
DNS:                Do not adjust
Firewalling:        NONE
User Control:       yes
Accept these settings and adjust configuration files (y/n)? y
Adjusting /etc/sysconfig/network-scripts/ifcfg-ppp0
Adjusting /etc/ppp/chap-secrets and /etc/ppp/pap-secrets
  (But first backing it up to /etc/ppp/chap-secrets.bak)
  (But first backing it up to /etc/ppp/pap-secrets.bak)



Congratulations, it should be all set up!

Type '/sbin/ifup ppp0' to bring up your xDSL link and '/sbin/ifdown ppp0'
to bring it down.
Type '/sbin/pppoe-status /etc/sysconfig/network-scripts/ifcfg-ppp0'
to see the link status.

# /sbin/ifup ppp0
ifconfig

eth0      Link encap:Ethernet  HWaddr 88:AE:1D:36:B9:BC 
          inet addr:192.168.1.40  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::8aae:1dff:fe36:b9bc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9284767 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9646230 errors:0 dropped:0 overruns:0 carrier:3
          collisions:0 txqueuelen:1000
          RX bytes:4253201802 (3.9 GiB)  TX bytes:1745825042 (1.6 GiB)
          Interrupt:45

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:9664320 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9664320 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1548584325 (1.4 GiB)  TX bytes:1548584325 (1.4 GiB)

ppp0      Link encap:Point-to-Point Protocol 
          inet addr:79.37.66.154  P-t-P:192.168.100.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:197 errors:0 dropped:0 overruns:0 frame:0
          TX packets:231 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:28854 (28.1 KiB)  TX bytes:35754 (34.9 KiB)

[/code]

sto penando a come bypassare il discorso associazione usando opportunamente queste connessioni (se ne psossono attivare piu' di una anche sullo stesso host)



Maurizio Marini

unread,
Jul 24, 2012, 5:09:22 PM7/24/12
to pivel...@googlegroups.com
argh!
di queste connessioni pppoe gia' parlava Emanuele 3 anni fa
https://groups.google.com/d/msg/pivelli-dev/t56vqtXCTIs/E32iUBMFxjcJ

Maurizio Marini

unread,
Jul 25, 2012, 2:58:45 AM7/25/12
to pivel...@googlegroups.com
ok, staimo pensando che usando le credenziali del voip si ottenga la mitica pppoe sul 192.168.200.1

Lecredenziali si ottengono decritatndo il backup:

[code]
openssl aes-128-cbc -K 65316532656263323039373831383630 -nosalt -iv 0 -d -in
AGConfigddmmyy.kry -out AGConfigddmmyy.xml
[/code]

grep routed AGConfig250712.xml                                                                                                                                                     
                <Username>N100920E0...@aliceres.routed</Username>
grep Password AGConfig250712.xml
[...]

una di queste sere provo il tutto :)
e vi aggiorno

Reply all
Reply to author
Forward
0 new messages