Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2806 - DHCP enabled even though not present in config file #7605

Open
openwrt-bot opened this issue Feb 4, 2020 · 0 comments
Open

FS#2806 - DHCP enabled even though not present in config file #7605

openwrt-bot opened this issue Feb 4, 2020 · 0 comments
Labels
flyspray release/19.07 pull request/issue targeted (also) for OpenWrt 19.07 release

Comments

@openwrt-bot
Copy link

jpsollie:

Supply the following if possible:

  • Device problem occurs on : Mikrotik RBM33G
  • Software versions of OpenWrt/LEDE release, packages, etc: OpenWrt 19.07, synced this morning, fully up-to-date
  • Steps to reproduce: no idea
    My "Lan" /etc/config/network:
    config interface 'lan'
    option type 'bridge'
    option ifname 'eth0.1'
    option proto 'static'
    option netmask '255.255.255.0'
    option gateway '10.0.0.254'
    option ipaddr '10.0.0.35'
    list dns '10.0.0.5'
    list dns '10.10.0.5'
    option ip6assign '60'
    My "Lan in /etc/config/dhcp:
    config dhcp 'lan'
    option interface 'lan'
    option ignore '1'

My ip addr list:
25: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether cc:2d:e0:5a:b8:5b brd ff:ff:ff:ff:ff:ff
inet 10.0.0.35/24 brd 10.0.0.255 scope global br-lan
valid_lft forever preferred_lft forever
inet 10.0.0.124/24 brd 10.0.0.255 scope global secondary br-lan
valid_lft forever preferred_lft forever
inet6 2a02:1802:a6:0:8a00:dfc6:fd71:a219/64 scope global dynamic
valid_lft 2591708sec preferred_lft 604508sec
inet6 fe80::6617:aede:f2cc:dd4/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::ce2d:e0ff:fe5a:b85b/64 scope link
valid_lft forever preferred_lft forever

DHCP lease info from DHCP server:
LAN 10.0.0.124 cc:2d:e0:5a:b8:5b 2020/02/04 10:23:54 2020/02/04 18:23:54 ethernet
LAN 10.0.0.125 cc:2d:e0:5a:b8:5b 2020/02/04 10:23:56 2020/02/04 18:23:56 ethernet
... it does not listen to 10.0.0.125, though.

The device also sends traps to the trap server using 10.0.0.124, which is not registered in DNS (the reason why I detected it)

Maybe a bug in the config scripts somewhere?

@aparcar aparcar added the release/19.07 pull request/issue targeted (also) for OpenWrt 19.07 release label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flyspray release/19.07 pull request/issue targeted (also) for OpenWrt 19.07 release
Projects
None yet
Development

No branches or pull requests

2 participants