Projecte

General

Perfil

Actions
Copy link

Error #332

tancat

[qmp-users] Wrong DCHP range in XW Nanostations M5 LAN connections

Afegit per Roger Pueyo Centelles fa més de 9 anys. Actualitzat fa casi 9 anys.

Estat:
Tancat
Prioritat:
Alta
Assignat a:
Roger Pueyo Centelles
Categoria:
Network
Versió prevista:
-
Inici:
21-12-2014
Data de venciment:
% realitzat:

100%

Temps previst:
Temps invertit:
2:00 h

Descripció

Hi,

We found a problem with XW images (if not all) a default configured XW
Nanostation, instead of providing DHCP connectivity along the 172.30.X.X
network it gives addresses on the 169.X.x.X invalid network range, which
corresponds to the LAN_RESCUE network, sharing the same interface than LAN.

We have to workarround that by setting the LAN_RESCUE network to a
192.168.X.X network so that the addresses of the 172.x are lower and
thus the first addresses to be assigned are from the LAN range. But I
consider that a kludge.

Regards

Actions
Copy link
 #1

Actualitzat per Roger Pueyo Centelles fa més de 9 anys

I am sorry, I should have to reflash a new one to have the failing
version. I send you a working one just after changing LAN_RESCUE IP.

$ cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd36:faa3:7547::/48'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 5'

config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0t 1'

config interface 'wan_e0_2'
option ifname 'eth0.2'
option proto 'dhcp'

config interface 'lan'
option type 'bridge'
option proto 'static'
option ipaddr '172.30.22.1'
option netmask '255.255.0.0'
option dns '208.67.222.222 208.67.220.220 209.244.0.3'
list ifname 'eth0.1'
option ip6addr 'fd00:1714:1714:1800::1/64'

config interface 'wan_e0_2_rescue_12'
option proto 'none'
option ifname '@wan_e0_2_rescue.12'

config interface 'wan_e0_2_rescue'
option proto 'static'
option ipaddr '169.254.0.1'
option netmask '255.255.255.248'
option ifname 'eth0.2'

config interface 'lan_12'
option ifname '@lan.12'
option proto 'static'
option ip6addr 'FD02:0:0:418:D62B:1800:0:212/128'

config interface 'lan_rescue'
option ifname 'br-lan'
option _orig_ifname 'br-lan'
option _orig_bridge 'false'
option proto 'static'
option ipaddr '192.168.168.1'
option netmask '255.255.255.0'

config interface 'mesh_w0_12'
option ifname '@mesh_w0.12'
option proto 'static'
option ip6addr 'FD02:0:0:418:D62B:1800:0:312/128'

config interface 'mesh_w0'
option proto 'static'
option ipaddr '169.254.0.1'
option netmask '255.255.255.248'

David.

El 12/12/14 a les 12:45, Roger Pueyo Centelles | Routek.net ha escrit:

- Mostra el text citat. -

_______________________________________
qmp-users mailing list

https://mail.dabax.net/cgi-bin/mailman/listinfo/qmp-users

Actions
Copy link
 #2

Actualitzat per Roger Pueyo Centelles fa més de 9 anys

  • Estat ha canviat de Nou a Resolt

Fixed in c1f9ce0b. Some newly added devices (including NanoStation-M5-XW) were being configured by default with the qmp.networks.disable_mesh_dhcp="0" option, which made giving rescue IPv4 addresses from the mesh_w0 network to the LAN interface.

Actions
Copy link
 #3

Actualitzat per Roger Pueyo Centelles fa casi 9 anys

  • Estat ha canviat de Resolt a Tancat
  • % realitzat ha canviat de 0 a 100
Actions
Copy link

També disponible a: Atom PDF