Posted: Wed Sep 30, 2015 6:27 Post subject: Cannot set IP address for new bridge
I am trying to create multiple BSSIDs in my WLAN. The problem is that I cannot assign an IP address and netmask to a new bridge. I can enter data into these fields, but when I apply the settings they reset to 0.0.0.0.
Here are the details.
Firmware: DD-WRT v3.0-r27360 (06/18/15) big
RT-N66U
HW Ver: B1
to assign an IP address to a new bridge, it resets There are any number of cookbooks for this; I list a few below. All of these start out by creating a bridge.
(1) Reset to factory defaults, and set some simple defaults (router name, ntp, ssh, https, wireless SSID and address)
(2) Crete a bridge (br1) and apply settings
(3) Set address and netmask, and apply settings
At this point the address and netmask usually reset to 0.0.0.0 -- though sometimes they both change to 255.255.255.0.
Ideally, the setup I want is
Wired:
10.22.40.50 / 255.255.254.0
Wireless
10.23.40.50 / 255.255.255.240
Among other things, I have tried using the "default" IPs (192.168.1.1/24, and 192.168.2.1/24), but it didn't help.
--
For the sake of posterity, here are some of the cookbooks I've attempted to follow.
Posted: Sun Oct 11, 2015 15:21 Post subject: Still no luck creating bridge
Can anyone help? My old router is dying, and I need to figure this out or decide to abandon dd-wrt (which I would hate to do). I've got to be missing something simple, since all I am trying to do is add a bridge.
As noted in the previous message, I click on Add Bridge, name it br1, apply settings, and then try to set the IP address and netmask. When I apply settings again, the IP info is reset to all zeroes.
My next step, I guess, is to figure out the commands for adding a bridge and try it from an SSH session; perhaps it will give me an informative error message.
I enabled syslog to see what I could learn. Interestingly, the syslog messages don't even mention br1. See below. (I shortened the log lines a bit for readability.)
Does anyone have any ideas on this? Thsnks.
15:03:11 kern.info kernel: br0: port 3(eth2) entered disabled state
15:03:11 kern.info kernel: br0: port 2(eth1) entered disabled state
15:03:11 kern.info kernel: br0: port 1(vlan1) entered disabled state
15:03:11 user.info : ttraff : traffic counter daemon successfully stopped
15:03:11 user.info : bridge deleted successfully
15:03:11 user.info : nas : NAS daemon successfully stopped
15:03:11 kern.warn kernel: Hooks already unregistered
15:03:11 kern.warn kernel: Hooks already unregistered
15:03:11 user.info : interface deleted successfully
15:03:11 kern.info kernel: device vlan1 left promiscuous mode
15:03:11 kern.info kernel: br0: port 1(vlan1) entered disabled state
15:03:11 kern.info kernel: device eth2 left promiscuous mode
15:03:11 kern.info kernel: br0: port 3(eth2) entered disabled state
15:03:11 kern.info kernel: device eth1 left promiscuous mode
15:03:11 kern.info kernel: br0: port 2(eth1) entered disabled state
15:03:11 user.info : bridge deleted successfully
15:03:11 user.info : interface deleted successfully
15:03:11 kern.warn kernel: Interface br0 doesn't exist
15:03:11 kern.warn kernel: Hooks already unregistered
15:03:11 kern.warn kernel: Hooks already unregistered
15:03:11 user.info : interface deleted successfully
15:03:11 kern.warn kernel: Interface br0 doesn't exist
15:03:12 user.info : udhcpc : udhcp client process successfully stopped
15:03:12 kern.info kernel: device eth0 left promiscuous mode
15:03:12 user.info : bridge added successfully
15:03:12 user.info : bridge added successfully
15:03:12 kern.info kernel: using kernel STP
15:03:12 user.info : bridge added successfully
15:03:12 kern.info kernel: device br0 entered promiscuous mode
15:03:12 user.info : interface added successfully
15:03:12 kern.info kernel: device vlan1 entered promiscuous mode
15:03:12 kern.info kernel: device eth0 entered promiscuous mode
15:03:12 kern.info kernel: br0: port 1(vlan1) entered forwarding state
15:03:12 kern.info kernel: br0: port 1(vlan1) entered forwarding state
15:03:12 user.info : interface added successfully
15:03:12 kern.info kernel: device eth1 entered promiscuous mode
15:03:12 kern.info kernel: br0: port 2(eth1) entered forwarding state
15:03:12 kern.info kernel: br0: port 2(eth1) entered forwarding state
15:03:13 user.info : interface added successfully
15:03:13 kern.info kernel: device eth2 entered promiscuous mode
15:03:13 kern.info kernel: br0: port 3(eth2) entered forwarding state
15:03:13 kern.info kernel: br0: port 3(eth2) entered forwarding state
15:03:13 kern.info kernel: device br0 left promiscuous mode
15:03:13 kern.info kernel: device br0 entered promiscuous mode
15:03:13 kern.info kernel: device br0 left promiscuous mode
15:03:13 kern.info kernel: device vlan2 entered promiscuous mode
15:03:14 kern.info kernel: br0: port 1(vlan1) entered forwarding state
15:03:14 kern.info kernel: device vlan2 left promiscuous mode
15:03:14 user.info : dnsmasq : dnsmasq daemon successfully stopped
15:03:14 user.info : ttraff : traffic counter daemon successfully started
15:03:14 kern.info kernel: br0: port 2(eth1) entered forwarding state
15:03:15 user.debug : ttraff: data collection started
15:03:15 user.info : NAS : NAS lan (wl0 interface) successfully started
15:03:15 user.info : dnsmasq : dnsmasq daemon successfully started
15:03:15 kern.info kernel: br0: port 3(eth2) entered forwarding state
15:03:16 user.info : cron : cron daemon successfully stopped
15:03:16 user.info : cron : cron daemon successfully started
15:03:16 cron.info cron[2114]: (CRON) STARTUP (fork ok)
15:03:16 cron.info cron[2114]: (crontabs) ORPHAN (no passwd entry)
15:03:18 user.info : httpd : http daemon successfully stopped
Posted: Tue Oct 13, 2015 20:20 Post subject: Re: Still no luck creating bridge
ptfnet wrote:
I click on Add Bridge, name it br1, apply settings, and then try to set the IP address and netmask. When I apply settings again, the IP info is reset to all zeroes.
Sorry to add what will be probably useless help, but just to make sure, are you clicking 'Save' and then 'Apply'? Likely not an issue, as you've changed other settings, but doesn't hurt to verify. Next, have you tried a newer build? 27858 is well regarded; do -not- use 27944.
The CFE check would be easy to do right from the GUI Command window, per PYB's link:
2) No, I generally don't save until I need to. That is: after I've done a lot of work, if I'm about to do something drastic, or if I need to reboot. In the case of the bridge settings, I could not save until I entered a valid IP. At that point, neither save nor apply would hold onto the IP address.
Thanks once again; maybe I can finally get rid of my (slowly dying) old router.
