On Sat, 19 Jul 2014, Gert Doering wrote:
On Fri, Jul 18, 2014 at 04:08:02PM -0700, David Lang wrote:
go do a tcpdump of your WAN interface some time, look at all the
attacks that are going on there (especially with an ISP that's not
blocking it for you)
I'm well aware of all the bullshit
On Thu, 17 Jul 2014, Gui Iribarren wrote:
On 17/07/14 21:03, David Lang wrote:
I know that IPv6 designers pine for the good old days of the Internet
when no security was needed.
But the reality is that hackers and worms have shown that leaving
systems exposed to the Internet is just a Bad
by the way, link local addresses are not going to be used for these devices,
because they will all have some 'cloud' feature that will require they have a
way to phone home.
David Lang
On Fri, 18 Jul 2014, David Lang wrote:
Every IPv4 home router I have seen defaults to 'block all incoming
On Fri, 18 Jul 2014, Benjamin Cama wrote:
Le jeudi 17 juillet 2014 à 17:03 -0700, David Lang a écrit :
But the reality is that hackers and worms have shown that leaving systems
exposed to the Internet is just a Bad Idea.
Do you mean, all the hackers and worms we see today despite all
that has been exploited in the past, especially
with the very expensive, high-end printer/copiers sold to businesses.
Again from companies that should know better
David Lang
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https
.
But that's not the world we live in.
David Lang
On Wed, 16 Jul 2014, Lyme Marionette wrote:
- Original Message -
On Wednesday, July 16, 2014 2:10:53 PM Gui Iribarren g...@altermundi.net
wrote:
Benjamin is giving some great examples of real-world scenarios where
an
default-open firewall
can actually knock you off the network
due to broken ISPs, cerowrt has spent a lot of time over the last couple of
months working on this. I would suggest at least reading through the issues
they've been having making things work in the real world before enabling this.
David Lang
Also
On Fri, 9 May 2014, John Crispin wrote:
(maybe i should start to only send the acks for this series, it will
save us a lot of time)
no, giving the reasons for each nack is valuable.
David Lang
___
openwrt-devel mailing list
openwrt-devel
are beginning.
David Lang
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
On Fri, 28 Mar 2014, Alan.Hoo wrote:
Hello Everyone
how can I remove the nf_conntrack kernel module from OpenWRT System ?
creating a build config without it is hard, there are a huge number of indirect
dependencies that trigger it, and most of them won't show up until you disable
some
to the squashfs code to allow it to deal with badblocks.
has this been done? was I misinformed on what the problem is? or is this still a
problem and devices with nand flash can work, but only if they avoid squashfs?
David Lang
___
openwrt-devel mailing list
.
There are so many ways in that modifying the source code you download in a way
that will still compile on a project that changes as rapidly as openwrt is a
very daunting task, and you should expect that they have far better uses of
their time.
David Lang
At minimum, I'd suggest maybe it'd
As I understand it, lawyers are looking over the situation with this driver
before it gets included in the upstream kernel.
David Lang
On Fri, 29 Nov 2013, Wojciech Kromer wrote:
Date: Fri, 29 Nov 2013 14:34:44 +0100
From: Wojciech Kromer wojciech.kro...@dgt.com.pl
Reply-To: OpenWrt
of it working for people?
do you need someone to sponsor reviews of it?
There are a lot of people out there who would like to run OpenWRT on their ADSL
router (myself included), so I would think that there's interest in adding
support for these sorts of devices.
David Lang
On Fri, 8 Nov 2013, Martijn
-then-tftp process. I just get timeouts on
the tftp.
Any suggestions?
David Lang
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
else, there is support for new hardware all the time.
A lot of people get really nervous about installing from a dev tree onto their
one and only router. They really should be able to install from a release before
the hardware is discontinued.
David Lang
new radio sections get created, with the
MAC address in them, default SSID, and disabled.
How can I work around this without having to gather all the MAC addresses ahead
of time and putting them in the config files that I push out to the routers?
David Lang
with lots of networks. I'll look into it though.
David Lang
- Felix
On 2013-02-10 11:25 AM, Mitch Kelly wrote:
Hi,
Removing option disabled 1 into 'wireless' and adding in the SSID etc before
you build should do the trick, You should not need to add the MAC address
into the config file
On Sun, 10 Feb 2013, Felix Fietkau wrote:
On 2013-02-10 12:05 PM, David Lang wrote:
On Sun, 10 Feb 2013, Felix Fietkau wrote:
Newer OpenWrt versions put the device path in the wifi sections
instead of the MAC address.
This is a recent build from Trunk, could you give me an example
loaded to move forward with this.
If someone can coach me through the process, I would be happy to work on getting
this up.
David Lang
P.S. I also purchased a wndr4300 and wndr4500 to work on if the 4700v4 ends up
being a dud.
___
openwrt-devel mailing
101 - 120 of 120 matches
Mail list logo
