Joined: 08 May 2018 Posts: 14222 Location: Texas, USA
Posted: Tue Nov 30, 2021 18:00 Post subject:
So, this is about manually starting the lighttpd server, not enabling it through the webUI and configuring from there... which is what we should probably concern ourselves with, perhaps? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Both guest network wikis need to be edited; not sure what you mean by "defeats the purpose of an unbridged VAP" - what purpose?
Sorry, it is just me grumbling about the level of research & debugging that was required to get guest network(aka VAP) running. My EA2700 with much older dd-wrt revision died. I bought a cheap EA6700 some time ago, and converted it over to DD-WRT with r37xxx and let it sit on a shelf. The EA2700 died suddenly, so I setup the EA6700 as a gateway with AP to avoid having to deal with the complexities of WAP and guest. PostTurkey time was spent learning about "unbridged", and switching over to WAP with a guest network; which is what I was grumbling about.
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Thu Dec 02, 2021 12:36 Post subject:
kernel-panic69 wrote:
So, this is about manually starting the lighttpd server, not enabling it through the webUI and configuring from there... which is what we should probably concern ourselves with, perhaps?
The WEBUI should use /tmp/lighttpd.conf. By starting Lighttpd manually while specifying the config file, you can test your config file for errors and... warnings.
I did use the WEBUI, Lighttpd will run but after a few browse hits, it stopped working. I think I need to re-test to confirm this. In the end, I am using my custom config file /jffs/etc/lighttpd.conf.
BTW, those are warnings not errors. Sorry!
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 26 Mar 2013 Posts: 1857 Location: Hung Hom, Hong Kong
Posted: Thu Dec 02, 2021 12:44 Post subject:
ZenInTexas wrote:
Sorry, it is just me grumbling about the level of research & debugging that was required to get guest network(aka VAP) running. My EA2700 with much older dd-wrt revision died. I bought a cheap EA6700 some time ago, and converted it over to DD-WRT with r37xxx and let it sit on a shelf. The EA2700 died suddenly, so I setup the EA6700 as a gateway with AP to avoid having to deal with the complexities of WAP and guest. PostTurkey time was spent learning about "unbridged", and switching over to WAP with a guest network; which is what I was grumbling about.
VAP and Guest Nework of DD-WRT definitely needs some work! They are not as simple as clicking a few buttons in the end.
Patience and tolerance ... _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 08 May 2018 Posts: 14222 Location: Texas, USA
Posted: Thu Dec 02, 2021 17:12 Post subject:
mwchang wrote:
ZenInTexas wrote:
Sorry, it is just me grumbling about the level of research & debugging that was required to get guest network(aka VAP) running. My EA2700 with much older dd-wrt revision died. I bought a cheap EA6700 some time ago, and converted it over to DD-WRT with r37xxx and let it sit on a shelf. The EA2700 died suddenly, so I setup the EA6700 as a gateway with AP to avoid having to deal with the complexities of WAP and guest. PostTurkey time was spent learning about "unbridged", and switching over to WAP with a guest network; which is what I was grumbling about.
VAP and Guest Nework of DD-WRT definitely needs some work! They are not as simple as clicking a few buttons in the end.
Patience and tolerance ...
This is a known issue that has been tossed around for some time. I have not reviewed the most recent ticket about it to see if there are any new clues as to what needs to be done. Last I knew, BS was out of ideas of what to do to fix it. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Sorry, it is just me grumbling about the level of research & debugging that was required to get guest network(aka VAP) running. My EA2700 with much older dd-wrt revision died. I bought a cheap EA6700 some time ago, and converted it over to DD-WRT with r37xxx and let it sit on a shelf. The EA2700 died suddenly, so I setup the EA6700 as a gateway with AP to avoid having to deal with the complexities of WAP and guest. PostTurkey time was spent learning about "unbridged", and switching over to WAP with a guest network; which is what I was grumbling about.
VAP and Guest Nework of DD-WRT definitely needs some work! They are not as simple as clicking a few buttons in the end.
Patience and tolerance ...
This is a known issue that has been tossed around for some time. I have not reviewed the most recent ticket about it to see if there are any new clues as to what needs to be done. Last I knew, BS was out of ideas of what to do to fix it.
With this revision, I have an EA6700 that has been working for at least 1 week. It is configured for a single unbridged VAP-wl0.1(2.4) with the EA6700 running a WAP(WAN disabled) the rest of the private network has another DD-WRT gateway which has services for DHCP & DNS. The EA6700 dnsmasq is serving up DHCP address & acting as a DNS for the VAP subnet. The EA6700 has firewall rules to keep the VAP subnet isolated & happy. However, I did not use a vlan in my configuration; if the chip based vlan is more efficient, I might give it a try.
