>> - While brands have value, you can change a name without losing all the
>> brand recognition. I'm thinking here of cases like XBMC->Kodi or
>> OpenOffice-> LibreOffice.
> I would point at OpenOffice -> LibreOffice as a failure of name changes.
There are several aspects in a name change. E.g.
> Yocto. If lede were to succeed in meeting its other goals, coherently,
> preserving "lede" and moving forward as a separate project does make
> sense.
I don't have a clear opinion either way, but I think there are several
points to take into account:
- OpenWRT indeed has a fair bit of positive
> RFC6303 specifies reverse dns zones that ideally should not be forwarded
> to upstream (root) servers and create unnecessary load upon them.
Shouldn't this be done upstream (i.e. in dnsmasq directly) rather than
in our config?
Stefan
___
AFAICT OpenWRT comes with some support for the Hame MPR-A1 thingy
(although its 16MB of RAM and 4MB of flash probably prevent it from
being fully supported).
I had no trouble building an image for it, but now I'm wondering how to
install that image. I went to
This option group includes the `libanl' library which
Back before XFree86 consolidated misc-fixed and other such fonts to
cover (a small subset of) Unicode, these two chars where typically
rendered under X11 as symmetric quotes (the '
Why do you want GitHub to close so bad !!!
I don't. There are indeed many other cases where you may want to move
to something else. The problems stay the same.
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
We use git, the day github closes, or asks for money, or ..., we move.
Notice how right after suggesting github, you suggested using
its bugtracker. It's only when github closes your access that you
realize you didn't stick to just using Git.
Stefan
you want, using tun devices (ssh -w), without the recursive TCP issues.
The -w switch has the exact same TCP-over-TCP issue.
But don't worry: TCP-over-TCP is used everyday by lots of people.
It's not perfect, but it works well enough for many uses.
That's why ssh provides -w and that's also why
I'm not sure if I can adequately address all of your concerns, but I
may be able to clear up some confusion.
It seems that there was no confusion at all. The problem is that
Belkin/Linksys lied about its involvement with the OpenWRT community and
what you're saying confirms it.
The
With new values: 9.1 MB/s
Sounds amazingly high for a noisy environment (I'm no specialist, but
I've never gotten such high bandwidth over wifi).
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
I'd like to use a Samsung GT-B3740 USB LTE modem together with OpenWRT.
To get it to build just add a declaration to
Another option is to compile it directly into your kernel, via
make kernel_menuconfig
-- Stefan
___
openwrt-devel mailing list
[ Previously posted on openwrt-users, but now that it failed halfway,
I figure that installing via httpd isn't really an option at all. ]
I finally got my Gigaset back, so I can get back at installing OpenWRT
on it. I have replaced the secondary bootloader, so I get the HTTP
server requesting
is that danube or amazon based board?
Danube.
In case that is danube board please use openwrt/v2013.07 branch to get
u-boot going:
https://github.com/danielschwierzeck/u-boot-lantiq/commits/openwrt/v2013.07
Is that required to install OpenWRT?
How do I install that u-boot?
Stefan
Except that when I submit that firmware, the request never ends.
[ See below my sig for the story of what happens in more details. ]
After trying a few more times with various machines, it finally worked
right (without those long waits). So now I managed to install the
attitude adjustment
Has anyone figured out to install OpenWRT on something like a Hame
MPR-A1 without opening the device and connecting a serial line?
Most of those devices offer a plain busybox shell via telnet and support
for usb-storage, so it should be possible to install OpenWRT via
/dev/mtd*, but AFAIK the few
NAK. Journaling is disabled on purpose, as it wears out flash based
devices faster.
I don't know of any non-anecdotal evidence showing that the difference
is significant. OTOH the added reliability afforded by journaling
(especially for the kind of boxes that typically run OpenWRT where
and allows you to start and start the daemon.
(with-smartypants-mode But what if I want to start it instead?)
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I did this on my boxes, but it does not help.
Again a device is _pingable_, but all daemons are
not responding anymore:
So either:
- watchdog was killed and this just disabled the watchdog timer altogether.
- watchdog was not killed for some reason (e.g. because the kernel
considered that it
Just a thought. The directory reserved for uci should have been named
something like /etc/uci-config.
Or maybe just /etc/uci since /etc means config.
But it's much too late to change any of it.
OTOH maybe sysupgrade should handle /etc differently: instead of only
preserving a few specific
I'm curious about this box, it looks very interesting as a replacement
for my current ADSL modem/router which is one of the last non-Free
computer I use daily. Is the ADSL modem working well under OpenWRT?
And what about the FXO/FXS ports?
Stefan
Ian Add an initscript to the rsync package for use as a daemon, and a
Ian sample rsyncd.conf to show a simple setup.
Ian Signed-off-by: Ian Leonard antonla...@gmail.com
Split rsyncd into a separate package
Make rsyncd a separate config option so that people who don't want an
rsync daemon
I note that the file /tmp/state/network contains the interface, ip address,
and expiration time of the WAN DHCP lease... I'm wondering what's
involved in writing that information into somewhere persistent where it
can be reused on reboot?
You may want to start by replacing the /var symlink
Picky, picky. ;-)
No, no, just picky.
Well other than binaries that depend on the kernel like iptables you
should be right about the uClibc binaries. But the normal case (i.e.
not custom) is to load the modules after extroot, so that's what we
build extroot for. If you really care and
the disabling is being done deliberately to give users a chance /
force them to clean up the overlay after a reflash.
So this test is only for the `overlay' case, not the new option
target / case, right?
No, it's for both because the option target / case still has the same
problem, namely
the disabling is being done deliberately to give users a chance / force
them to clean up the overlay after a reflash.
So this test is only for the `overlay' case, not the new option
target / case, right?
Stefan
___
openwrt-devel mailing
- clean code (not obfuscated)
Obviously agreed. But there are likely disagreements about what is
clean and what is obfuscated. Turning a oneliner sed into
a 10-liner read/while/case/set loop is usually not an improvement in my
book (as discussed previously). If you want to avoid forking a sed
1) More space for packages is needed than available flash storage (we
may also want more data storage, but generally that doesn't depend on
having a larger rootfs, as it can easily go somewhere other than root)
I can think of 2 separate cases:
a) the extra flash space is owned: it's expected
The p910nd driver provides a bidirectional network interface to USB
connected printers.
Actually, it can be either unidirectional or bidirectional. And I don't
know of a case where the bidirectional code is useful (I'm partly to
blame for its existence, because I thought it would let the
it is always a bad idea to mix up different languages
in one environment.
I don't accept this is a valid starting point. I agree that it is
useful to limit the number of tools/languages you use, but you should
still try and use the right tool/language for the right job.
now we use
I was never satisfied with the ugly hack, how kernel-modules
were loaded in openwrt, but it works since the beginning. here
is a proposal to do it clean and also fast with ash-builtins.
As an outsider, I'd just like to say that I find this new code more
complex for very little benefit.
As an outsider, I'd just like to say that I find this new code more
complex for very little benefit.
really? more lines maybe, but straightforward and not hacky.
I guess it's a question of taste, but to me that current code is clean,
straightforward, and concise. About as good as it gets.
I want the flexibility of the former. I want my extroot device to be
the entire root filesystem of my system and not require a particular
flashed image because it relies on files in the flashed image's
root filesystem.
Exactly like everybody else, indeed. That's why there's no need for
to make alone. I think pivot_root is better than chroot for the
purposes of running init and in general for avoiding gotchas, but that
can be done without an overlay, if that is the consensus.
As someone who uses an external root (tho using a hand-made patch
rather than your extroot, mostly
Why not have the implementation look at what's on the extroot device
and if it's an overlay filesystem format then execute the overlay
codepath(s) and otherwise assume it's a standalone filesystem and
mount it and pivot_root to it.
I'm not sure there's a way to tell the difference: the
extend the life of the device... in theory. A colleague of mine was using
PGP encryption on his SSD boot drive and had it fail after a couple of
thousand writes.
That's just an early drive failure, unrelated to the fact that flash
memory wears out.
Stefan
Question: How should I do that? Should I create a new set of packages,
called, say, avahi-with-dbus...? Or should I just put some kind of a
flag in the Makefile of the existing avahi package?
How 'bout following the example of hostapd, and rename the current avahi
to avahi-mini or some such?
I apoligize ahead of time. I am hardly a developer, but I've been
mucking around with the WRTU54G-TM since March. I was told to port to
2.6 to get included in trunk, and I did! I have tarball at
http://wrt.scottn.us/openwrt-trunk-adm8668.tar.gz
That's very interesting. But I can't find
So: how can I configure OpenWRT to always do a DHCP request upon
wifi-(re)connection, even when it already has a valid IP-lease?
Ping?
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
When I reboot my AP/router, my print server (running OpenWRT) ends up
being unknown: I can still connect to it via its IP address, but its DNS
name is lost.
This is simply due to the fact that the DNS name comes from the DHCP
registration and that when the AP/router is rebooted, OT1H the
Once you telnet into it try to type uname -a and see if it is Linux ! :)
No, the telnet daemon doesn't give me a normal shell. It gives me some
kind of text-based interactive configuration system (that somewhat
mirrors what the web pages provide).
Stefan
I inherited from a DSL modem+router whose firmware describe as a Solos
4610 RD / Solos 461x CSP v1.0, and telnet shows me a big
`conexant' banner.
Just going from the hardware, this seems to be a Connexant CX96410
based device. There is no OpenWRT port, but there are linux sources
for a
I'm getting the above error message on a WL-500g, with a firmware
compiled a couple days ago from a fresh checkout of
svn://svn.openwrt.org/openwrt/branches/backfire.
It seems to be related to
https://dev.openwrt.org/ticket/6425
(and https://dev.openwrt.org/ticket/7059), which claims to be
OK, if you interpret it like that, one doesn't need to deblob the kernel
source. We only need a configuration value that avoids installing the
non-free stuff.
Of course, that's just my opinion, I don't speak for the LibreWRT guys.
I personally would really like it if OpenWRT labelled each
The user that builds its own firmware from scratch either knowns which
packages are free or he/she does not care.
How would a user (who cares) know which package is Free and which isn't?
I'm fairly well versed in those matters, and yet, even I don't know for
sure for all packages.
And most
In other words, I wonder why one would like to deblob. As long as you
don't install the blobs in the image, you are not using it. So if you
already downloaded it, what is the use of removing it above just not
installing and using it.
IIUC the issue is not whether to download this or not, but
Did you attach anything to the GPIO? A Capacitor?
Do you have a serial cable?
Yes, I have a serial cable now? (part of the reason was to debug this
problem, as well as some others, but it didn't help)
Compare the bootlogs. (reboot hard reset.)
Thanks,
I'll do that next time (will be a
My wrtsl54gs running Backfire 10.03 has the following problem:
If I unplug replug the power cable, it boots fine except that the WAN
connection (using DHCP) is not up (i.e. I have to log in and say ifup
wan, after which it all works fine).
Interestingly, rather than iup wan I can also do reboot
My wrtsl54gs running Backfire 10.03 does not bring up the firewall
correctly at boot. I have to /etc/init.d/firewall restart to make
it work. I.e. the following script works around the problem:
$ cat /etc/rc.d/S97sm-firewall
#!/bin/sh /etc/rc.common
START=97
start () {
#
Did you attach anything to the GPIO? A Capacitor?
Do you have a serial cable?
Yes, I have a serial cable now? (part of the reason was to debug this
problem, as well as some others, but it didn't help)
Stefan
___
openwrt-devel mailing list
I think this is directly related to your wan issue. Creation of the
missing rules is triggered when wan is brought up.
Hmm... good to know. Note that this problem appears regardless if
I reboot or if I power-cycle (i.e. the firewall is wrong regardless of
whether the WAN is brought up or not).
And now with the new WRT54G3Gv2-VF the box will be bricked
if the nvram is *not* fixed up...
So *this* particular fixup should be applied without human intervention.
Most of the others shouldn't.
Stefan
___
openwrt-devel mailing list
- nvram settings are bad, but the machine is still able to boot and we
can login remotely.
/etc/init.d/nvram would execute here and fix the critical vars.
Or it might brick the machine instead. And since remote login is
possible, there was no urgency that justified taking such a risk.
The init script mostly reset the cpu clock and the sdram configs. Some
idiots over clocked there routers are caused problems, linksys also
bumped the clock to 216 in one update to cover up a instability. SDRAM
settings have to do with early version of DD-WRT and I think one
specific version
I.e. it seems the reboot part is failing. Does anybody know this
problem or has some idea what it might come from? Has anybody managed
to get the watchdog to work on such a machine (or a similar one, maybe
wl500gp or some such)?
We add an emergency_restart(); I attach a patch
Thanks. Does
I.e. it seems the reboot part is failing. Does anybody know this
problem or has some idea what it might come from? Has anybody managed
to get the watchdog to work on such a machine (or a similar one, maybe
wl500gp or some such)?
We add an emergency_restart(); I attach a patch
Thanks.
I've been having non-reproducible hangs with my wrtsl54gs for a while
now (after finally installing a serial console I got to see that these
are caused by CPU 0 Unable to handle kernel paging request at virtual
address Any idea what that can come from?).
While trying to track down this
I have added a patch that should fix the problem:
https://dev.openwrt.org/changeset/21497
sdram_init was changed because some ASUS WL-500GP showed only 16MB RAM
and not 32MB. That script fixed that problem.
I really don't think that patching a suboptimal nvram setting is worth
the risk to
Less file system overhead on the flash side and no memory used to manage
the structures needed to insmod / rmmod.
Exactly. Maybe also a tighter memory layout since each module doesn't
have to be in its own set of ELF sections, IIUC.
Also, the linkage would be (presumably) static rather than
While I have seen the size listed in lsmod and /proc/modules, I don't
really know what it represents. I am assuming that it means code size
and not memory.
I suspect so as well. Still, it may point to an opportunity.
Make sure that you are counting the size of the files in /lib/modules
but wouldn't the increase in the kernel image actually equal the
decrease in the squash image and therefore the size of the rootfs_data
stay the same? Both are lzma compressed.
I expect that a kernel with some modules built-in will be smaller
(both in terms of flash space and in terms of RAM
Put all kmods (2) I needed into the kernel.
How?
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Tried to create an OpenWrt of a small VoIP proxy for a friend.
Unfortunately the source itself does not have a Makefile.
It just says Use: gcc -o mjproxy md5.c mjproxy.c.
You've had answers to your question, but I'll point out that a better
answer might be to provide a Makefile.
jdonohue654-openwrt == jdonohue654-openwrt
jdonohue654-open...@yahoo.com writes:
This proposed patch updates lvm2 build script to 2.02.63 ... the previous
version (2.02.60) is no longer available for download. this update also
necessitated some minor changes to
Highlights and changes since last stable release:
[...]
* New web server uhttpd (busybox httpd now disabled, as default)
Other than being different, what does it bring?
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
So please do not hesitate to submit patches in the future, it should be
quite a bit more pleasurable than it may have been previously.
Definitely. I wasn't so much complaining as rejoicing at the fact that
patch submission seems to be working now. As Emacs maintainer, I know
full well that
I've never needed to really get into the startup scripts much but now
I need to try and understand how the mini_fo union gets set up so I'm
trying to learn the startup scripts like preinit.
When I ad to fiddle with this part of the code, I'd add some
echo blabla /tmp/mydebug
in those
When I /etc/init.d/ntpd stop one of the two openntpd processes is
still left running. Apparently killall ntpd is not sufficient.
So I use the patch below which seems to work.
Applied in r20317, thanks!
Thank you for finally installing my patches.
Many of them were going through their third
Simple typo.
Stefan
Index: net/dhcp-forwarder/files/dhcp-fwd.init
===
--- net/dhcp-forwarder/files/dhcp-fwd.init (révision 19649)
+++ net/dhcp-forwarder/files/dhcp-fwd.init (copie de travail)
@@ -4,7 +4,7 @@
When I /etc/init.d/ntpd stop one of the two openntpd processes is
still left running. Apparently killall ntpd is not sufficient.
So I use the patch below which seems to work.
Stefan
Index: net/openntpd/files/ntpd.init
===
The patch below makes /etc/init.d/mpd start the MusicPlayerDaemon in
a more normal way:
1- it stops it from rebuilding the database at every start (which can take
a very very long time on large databases).
2- it stops it from going through the trouble to create the music
database directory
Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-beta/
Is there some equivalent Svn revision, branch, or the trunk rev-number
from which it was branched?
Stefan
___
openwrt-devel mailing list
This patch allows multiple listen ports to be configured for dropbear in
/etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
will break existing configs.
Shouldn't this be sent to the dropbear upstream maintainers? It doesn't
seem specific to OpenWRT at all.
No, as his patch only modifies OpenWrt scripts and uci.
The functionality of multiple ports with only one DropBear instance is
already in DropBear.
Duh... sorry for being so dense,
Stefan
___
openwrt-devel mailing list
Certainly a label or uuid is possible, but the problem isn't convincing
OpenWRT to boot into a rootfs, but making sure the rootfs has the
appropriate binaries.
Indeed. Part of the solution is to reduce as much as possible the
linkage between the squashfs/jffs2 part of the boot and the rest of
The Asus WL520GC I just bought is running Linux. It has 2MB of flash.
Wow, I assumed that out of the box, these devices with a small amount of
flash did not run Linux. That was true in the past at least. Things have
changed since I last checked...
obviously. DD-WRT micro images also run on
Still, you need jffs2 there (both the jffs2 partition and the jffs2
modules). That's a lot of flash space for something that's not
actually needed. And of course, it's also an added step when
installing upgrading the firmware.
Having a fallback jffs2 is something most people have said they
config mount
option 'uuid' 'some-uuid-here' OR
option 'label' 'fs-label' OR
option 'device' '/dev/device'
option 'target' '/usb'
option 'fstype' 'ext3'
option 'enabled' '1'
option 'enabled_fsck' '1'
option 'is_rootfs' '1'
Why not
As such I think it would be very useful to have a minimum build (just
enough to bring up interfaces and install additional packages)
Agreed.
Stefan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Linux can hardly fit in a 2MB flash device, once you have opened the
Yes, but this text was written in the old times (2004?)
I've been using OpenWRT on my WL-700gE for a while now. That machine
has a 2MB flash, so OpenWRT is quite usable there. But yes, it also has
a IDE interface, so the 2MB
This has to be manually configured after the first
boot (and requires a reboot after a sysupgrade first boot).
H... that's a problem. It means that you can't just have
squashfs+extroot but need a jffs2 inbetween just for this
little cconfig.
Actually the squashfs/jffs2 is a fallback
Here is the first part of the rootfs on external (i.e. not the squashfs,
jffs, or boot root) rootfs (right not just usb, but can easily be
extended to others).
Thanks, this is a needed feature, indeed.
This has to be manually configured after the first
boot (and requires a reboot after a
Note: The brcm47xx still won't work for those of you needing broadcom
wifi, stick to brcm-2.4. We will tell you when it does work.
I need to know. How much may take time before we can use the b43 driver?
One month? Half year?
IIUC the above note is conservative: the b43 driver in brcm47xx
I will commit your patches later today. I also need the username you
want to use, a ssh public key for svn, and the hash created by
'htdigest -c passwdfile openwrt username' for trac and I will get you
setup with access to LVM. I also request that you fill in
Oh, and did I say I *hate* Reply-To?
Stefan
Stefan == Stefan Monnier monn...@iro.umontreal.ca writes:
I will commit your patches later today. I also need the username you
want to use, a ssh public key for svn, and the hash created by
'htdigest -c passwdfile openwrt username
We are looking for people that want to maintain and update individual
packages. If you are interested please contact me with what package you want
to maintain.
I'd be happy to maintain the LVM package.
I guess that presumes it gets accepted first ;-)
Stefan
To be honest I'm not sure how useful the unmount in hotplug really is
anyway...usually if it's called it mean the device has already been
removed, I think.
But if you don't unmount, then you're left with some zombie mount,
which still refers to the device name and can lead to problems (minor
Swap comes last because I plan to enable swapfile support, which rely on
the filesystem to be mounted first. Any idea for a swapfile name?
/swapfile, /swap.swp ...
Is that really designed for swap on a hotplugged device?
Is that a good idea?
I use hotplugged swap. It is not a bad idea per
As for improving the docs...While docs can always be better, I prefer
development, and I think I've already greatly improved the state of
documentation compared to what it was, as far as preinit goes.
I'm sorry if my posts came thorugh as requests for you to improve the
doc. I haven't looked
I have just a request from the documentation point of view: can anyone
formalize a document with the init sequence, the hooks that can be used and
any other useful information to customize the init process. I know that the
source code is better a document... but I formal document can be
See, http://cshore.is-a-geek.com/openwrt/preinit_mount.html
It's fully documented along with an example.
Thanks. It's much better, but it still leaves several questions open:
- where is the failsafe code (it has its own subsection in the doc,
but it doesn't say to which file it
What do the rest of you think, of making the /lib move for a)
functions.sh and b) preinit?
100% agreement. You'll probably want to keep compatibility symlinks in
place, tho (and maybe /etc/functions.sh won't be a symlink but a file
that loads all the files into which functions.sh has been
What do the rest of you think, of making the /lib move for a)
functions.sh and b) preinit?
Sounds like a good idea to me. Might as well move /etc/init.d and
rc.common while we're at it - but not without compatibility symlinks,
both for users and for applications that rely on the old layout.
I posted a bug on the sourceforge tracker almost two weeks ago:
http://sourceforge.net/tracker/index.php?func=detailaid=2872760group_id=48978atid=454719
and since I haven't seen any answer (although it even contains a patch
which seems to work well, at least for me), I'm wondering if that's the
Sorry, wrong list,
Stefan
Stefan == Stefan Monnier monn...@iro.umontreal.ca writes:
I posted a bug on the sourceforge tracker almost two weeks ago:
http://sourceforge.net/tracker/index.php?func=detailaid=2872760group_id=48978atid=454719
and since I haven't seen any answer
The OpenVPN package uses `list' in its /etc/config/openvpn file.
In most cases, this works just fine.
But when you run /etc/init.d/openvpn restart, the decomposition
of restart into stop and start causes the config file
to be processed twice, so the list elements get added twice.
E.g. if in the
I am having a hard time to find the place where mounting root / really
happens ..
It's in /sbin/mount_root. And yes, it is not exactly trivial to find
(although in retrospect I had to admit that the name should have made it
pretty obvious).
See below the patch I use on my WL-700gE to mount
2. How to take part in the development, and how to become an OpenWrt
developer? Again, the direction to walk down, is to
participate. A good direction is to start maintaining a package,
discuss issues on irc #openwrt-devel etc.
I've sent several patches here, and I didn't get much feedback
Update the hotplug2 package from hotplug2-0.9 to hotplug2-1.0-beta.
hotplug2-1.0 no longer needs the udevtrigger, so remove that
dependency from target.mk.
That would be a welcome upgrade.
Some changes are needed to the rules. Help on that would be appreciated.
Among other things,
Has someone managed to build a kernel for use on the WL-700gE?
I tried to update my kernel and first noticed that the aec62xx module
was missing. `packages/kernel/modules/block.mk' seemed to explain that
some renaming break the kmod-ide-core package. So looking at the files
)
@@ -0,0 +1,12 @@
+#!/bin/sh /etc/rc.common
+# Copyright (C) 2009 Stefan Monnier
+START=15
+
+start () {
+ /sbin/lvm vgscan --ignorelockingfailure --mknodes || :
+ /sbin/lvm vgchange -aly --ignorelockingfailure || return 2
+}
+
+stop () {
+/sbin/lvm vgchange -aln --ignorelockingfailure || return 2
1 - 100 of 130 matches
Mail list logo
