Banda Ancha EU

Comunidad de usuarios
de fibra, móvil y ADSL

ADSL

Caída de Telefónica o mi router se ha muerto

RaulM21

Buenos días, tengo ADSL desde hace tres semanas. Hasta el miércoles iba de culo, pero compré un router Conceptronic C54APRA2+ que me solucionó los cortes contínuos.

Ayer por la tarde estaba tocando la config. del router y de repente petó la conexión (no toqué nada crítico, sólo la DMZ), por lo que volví a subir una config. previa que funcionaba perfectamente. Esto no funcionó, ni volver a subir firmwares ni nada de nada. Lo extraño es que al volver a poner el Xavi 7868R de telefónica, algo lento, pero conectaba. Ésta mañana lo he mirado y ni siquiera funcionaba éste.

Lo extraño es que el router nuevo me da unos valores de bajada y subida algo extraños:

3994 y 639, este último, el doble de lo que debería, y la bajada muy por encima de los 3 MB que tengo contratados.

Observo unos mensajes que da el log que no entiendo muy bien dónde cambiarlo:

Please set the MAC Address for the WAN Bridge.
Jan 1 12:00:15> Set the Environment variable 'wan_br_mac'.

ERROR - WAN Bridge Creation: wbr0

Voy a pegar el log del router junto con los datos del status:

 Device Information

 Firmware Version : V3.02B01T01.GE.20070104

 LAN

 MAC Address 00:xx:xx:xx:xx:xx

 IP Address 192.168.1.1

 Subnet Mask 255.255.255.0

 DHCP Server Enabled

 NAT Enabled

 WAN

 Virtual Circuit

 Status Connected

 Connection Type PPPoE

 IP Address 88.x.xxx.xx3

 Subnet Mask 255.255.255.255

 Default Gateway 192.168.153.1

 DNS Server 80.58.61.250

 Jan 1 12:00:10> AP Acquiring Lock

 Jan 1 12:00:11> NTP Polling Timer for DHCP Started succesfully.

 Jan 1 12:00:11> DSL Polling Timer Started succesfully.

 Jan 1 12:00:11> Firewall NAT service started

 Jan 1 12:00:11> AP REPORT LOCK ACQUIRED

 Jan 1 12:00:11> wlan_handle_load_event - Acquired Lock

 Jan 1 12:00:12> MAC address is : 00:80:5a:5c:77:bf

 Jan 1 12:00:15> starting on port 80

 Jan 1 12:00:15> (c)2000 Netfilter core team

 Jan 1 12:00:15> netfilter PSD loaded - (c) astaro AG

 Jan 1 12:00:15> Initializing the WAN Bridge.

 Jan 1 12:00:15> Please set the MAC Address for the WAN Bridge.

 Jan 1 12:00:15> Set the Environment variable 'wan_br_mac'.

 Jan 1 12:00:15> xx.xx.xx.xx.xx.xx

 Jan 1 12:00:15> Mounted root (squashfs filesystem) readonly.

 Jan 1 12:00:15> Mounted devfs on /dev

 Jan 1 12:00:15> 64k freed

 Jan 1 12:00:15> Algorithmics/MIPS FPU Emulator v1.5

 Jan 1 12:00:15> registered device TI Avalanche SAR

 Jan 1 12:00:15> Ohio250(7200/7100A2) detected

 Jan 1 12:00:15> DSP binary filesize = 356930 bytes

 Jan 1 12:00:15> Setting mode to 0xffff

 Jan 1 12:00:15> version:[6.00.01.00]

 Jan 1 12:00:15> Disable_igmp_snooping_register!!!

 Jan 1 12:00:15> Setting mode to 0xffff

 Jan 1 12:00:15> Default Asymmetric MTU for nas0 1500

 Jan 1 12:00:15> Registering protocol inspector: 0x94176bd8 for VCC:0x9400da00

 Jan 1 12:00:15> Default Asymmetric MTU for br0 1500

 Jan 1 12:00:15> Bridge Created: br0

 Jan 1 12:00:16> Bridge Created: br1

 Jan 1 12:00:16> Bridge Interface Added: eth0

 Jan 1 12:00:17> WPA Authenticator Started

 Jan 1 12:00:17> 2

 Jan 1 12:00:17> Default Asymmetric MTU for br1 1500

 Jan 1 12:00:17> 2

 Jan 1 12:00:20> Default Asymmetric MTU for wlan0 1500

 Jan 1 12:00:20> Default Asymmetric MTU for wdsup0 1500

 Jan 1 12:00:20> Default Asymmetric MTU for wdsdw0 1500

 Jan 1 12:00:20> Default Asymmetric MTU for wdsdw1 1500

 Jan 1 12:00:20> Default Asymmetric MTU for wdsdw2 1500

 Jan 1 12:00:20> Default Asymmetric MTU for wdsdw3 1500

 Jan 1 12:00:20> AP Driver configuration successful

 Jan 1 12:00:24> WDS manager Started PID : 164

 Jan 1 12:00:24> Configured WDS manager

 Jan 1 12:00:24> AP IS UP

 Jan 1 12:00:24> MemAddr=0xa4000000, RegAddr=0xa4080000

 Jan 1 12:00:24> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58f0 Data 0x8

 Jan 1 12:00:24> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58d4 Data 0x10

 Jan 1 12:00:24> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58b0 Data 0x4

 Jan 1 12:00:24> whal_hwCtrl_ProcessEepromBR : CurrEepromBufPtr = 0xc

 Jan 1 12:00:24> whal_hwCtrl_GetNvsDataSize: eepromImage.len = 0x1d9 214: Get NVS file information: NvsDataLen = 0x134 tblsOffset 0xa9

 Jan 1 12:00:24> whal_acxProcInitiate: Cpu halt -} download code

 Jan 1 12:00:24> DSL Carrier is down

 Jan 1 12:00:24> whal_acxProcLoadFwImage: 0xa4000000, 0x0

 Jan 1 12:00:24> whal_acxProcLoadFwImage() -- Loading FW image

 Jan 1 12:00:24> Compiled for DCR radio

 Jan 1 12:00:24> whal_acxProcLoadFwImage: 1, pBuf=0xc00b0d10, len=0x14b50. Extra pBuf=0x0, len=0x0

 Jan 1 12:00:24> whal_acxProcLoadFwImage: 2, pBuf=0xc00b0d10, len=0x14b50. Extra pBuf=0x0, len=0x0

 Jan 1 12:00:24> whal_acxProcLoadFwImage: 3, pBuf=0xc00b0d10, len=0x14b50, DataLen=0x14b48

 Jan 1 12:00:24> whal_acxProcLoadFwImage: 4, pBuf=0xc00b0d10, len=0x14b50

 Jan 1 12:00:24> whal_acxProcLoadFwImage: Checksum, calc=0x6dc2a3, file=0x6dc2a3

 Jan 1 12:00:24> ----------------------------------------------------------------

 Jan 1 12:00:24> ----------------------------------------------------------------

 Jan 1 12:00:24> START BSS, SSID=Router, BSSID=00-xx-xx-xx-x-BF

 Jan 1 12:00:24> ----------------------------------------------------------------

 Jan 1 12:00:24> ----------------------------------------------------------------

 Jan 1 12:00:24> AP Power Level = 1

 Jan 1 12:00:24> Regulatory Domain = ETSI

 Jan 1 12:00:24> Net[0] : Channel=7

 Jan 1 12:00:24> ----------------------------------------------------------------

 Jan 1 12:00:24> FW Watchdog is Enabled

 Jan 1 12:00:24> AP Releasing Lock

 Jan 1 12:00:28> ERROR - WAN Bridge Creation: wbr0

 Jan 1 12:00:28> ERROR - WAN Bridge Creation: wbr0

 Jan 1 12:00:28> ERROR - WAN Bridge Creation: wbr0

 Jan 1 12:00:28> ERROR - WAN Bridge Creation: wbr0

 Jan 1 12:00:28> Bridge Interface Added: wlan0

 Jan 1 12:00:44> DSL in Sync

 Jan 1 12:00:44> DSL Carrier is up

 Jan 1 12:00:44> sar read trained mode (3)(ADSL_G.dmt.bis)

 Jan 1 12:00:45> pingStat 2, oamHdr 230 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 200 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 280 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 240 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 260 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 600 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 230 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 800230 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 2B0 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 330 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 3B0 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 8002B0 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 800330 result 0

 Jan 1 12:00:45> pingStat 2, oamHdr 8003B0 result 0

 Jan 1 12:00:45> get 0xF at Addr 0xA30085B0

 Jan 1 12:00:45> pppd 2.4.3 started by root, uid 0

 Jan 1 12:01:20> PPPD Successfully Launched

 Jan 1 12:01:20> Timeout waiting for PADO packets

 Jan 1 12:01:20> Unable to complete PPPoE Discovery

 Jan 1 12:01:20> pppd 2.4.3 started by root, uid 0

 Jan 1 12:01:21> Connect: ppp0 {--} nas0

 Jan 1 12:01:23> PAP authentication succeeded

 Jan 1 12:01:23> peer from calling number 00:09:B6:8C:24:19 authorized

 Jan 1 12:01:23> WAN IP address 88.x.xxx.xx3

 Jan 1 12:01:23> WAN gateway 192.168.153.1

 Jan 1 12:01:23> primary DNS address 80.58.61.250

 Jan 1 12:01:23> secondary DNS address 80.58.61.254

 Jan 1 12:01:23> ppp0

 Jan 1 12:01:23> PPPoE Connect with IP Address 88.0.200.103

 Jan 1 12:01:23> PPPoE Connection Successfully Established

 Jan 1 12:01:23> PPPoE Connect with Gateway IP Address: 192.168.153.1

Es muy extraño porque un amigo dice haber tenido problemas también en la misma localidad, pero ahora mismo me encuentro a 3 Km. de casa donde creo que usan la misma central y navego sin problemas.

BocaDePez
BocaDePez

¿No se habrá desconfigurado el router?.

Yo le haría un reset a valores de fábrica y lo configuraria de nuevo.

Saludos.

RaulM21

Hola, ya está arreglado. Ha sido muy raro. Mientras funcionaba bien guardé una config. para restaurarlo por si acaso, pero cuando petó coincidió que estaba tocando la configuración. Hoy investigando me he dado cuenta de que el botón "Enable bridge filters" estaba activo. Lo he quitado y todo perfecto.

El caso es que no se desactivaba ni siquiera con el botón de reset, ni cargando la configuración previa.

Ahora ya va perfectamente.

Saludos.