On Sun, 14 Feb 2016 08:08:07 +0100 John Crispin wrote:
> NAK, it is a general pattern of daemons to be installed in disabled
> state, to prevent a default config causing security or other issues.
I understand it, but, for example, igmpproxy is not disabled by default.
Besides udpxy is not access
On Mon, 15 Feb 2016 09:27:04 +0100 Rafał Miłecki wrote:
> >> NAK, it is a general pattern of daemons to be installed in disabled
> >> state, to prevent a default config causing security or other issues.
> >
> > I understand it, but, for example, igmpproxy is not disabled by default.
> > Besides u
Hello,
it is similar to NBG-419N but has Atheros AR8316 4+1 GbE switch. I enabled
CONFIG_AR8216_PHY=y in target/linux/ramips/rt305x/config-3.18, rebuilt and
loaded openwrt-ramips-rt305x-nbg-419n-initramfs-uImage.bin to SDRAM via TFTP.
Now /sys/bus/mdio_bus/drivers/Atheros AR8216!AR8236!AR8/ exis
On Sat, 19 Sep 2015 12:11:06 +0200 John Crispin wrote:
> > it is similar to NBG-419N but has Atheros AR8316 4+1 GbE switch. I enabled
> > CONFIG_AR8216_PHY=y in target/linux/ramips/rt305x/config-3.18, rebuilt and
> > loaded openwrt-ramips-rt305x-nbg-419n-initramfs-uImage.bin to SDRAM via
> > TFT
On Sat, 19 Sep 2015 12:11:06 +0200 John Crispin wrote:
> rt305x has a rgmii that the switch connects to. however we dont have
> support in the driver for that rgmii port. you will need to first atch
> the driver to support the rgmii interface and then hook up the switch
> driver.
As I don't know
On Fri, 11 Sep 2015 12:08:19 +0200 Rafał Miłecki wrote:
> If you're doing a sysupgrade, please note you will likely end up with
> outdated opkg.conf. This may stop you from installing modules
>
> To fix this please execute manually:
> cp /rom/etc/opkg.conf /etc/opkg.conf
I've just updated TP-Li
On Thu, 1 Oct 2015 00:21:12 +0300 Nerijus Baliunas
wrote:
> # opkg install zabbix-agentd
> Installing zabbix-agentd (2.4.6-1) to root...
> Downloading
> http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/zabbix-agentd_2.4.6-1_ar71xx.ipk.
> C
Hello,
Linksys WRT300N v2.0 has Marvell 88e6060 switch. But ixp4xx arch does not have
its driver enabled (ar71xx has it). I added CONFIG_NET_DSA_MV88E6060=m,
but when I modprobe mv88e6060.ko, nothing happens. It seems driver does not hook
on any hardware:
# lsmod|grep mv
dsa_core76
On Sun, 23 Jul 2017 11:38:02 -0700 Florian Fainelli
wrote:
> > How do I configure vlan? Here I changed eth0 to eth0.1:
> >
> > config interface 'lan'
> > option type 'bridge'
> >option ifname 'eth0.1'
> >option proto 'static'
> >option ipaddr '192.168.1.1'
> >
On Thu, 27 Jul 2017 21:31:01 +0300 Sergey Ryazanov
wrote:
> > Tried the latest LEDE. Now I see in the boot log:
> > [6.507617] NPE-B: firmware's license can be found in
> > /usr/share/doc/LICENSE.IPL
> > [6.515168] NPE-B: firmware functionality 0x2, revision 0x2:1
> > [6.523171] eth
On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov
wrote:
> >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel
> >> messages log? If not then the mwswitch driver did not attached and
> >> you should fix this first. And only then go to the interface
> >> confi
On Fri, 28 Jul 2017 01:03:16 +0300 Nerijus Baliunas
wrote:
> On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov
> wrote:
>
> > >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel
> > >> messages log? If not then the mwsw
On Fri, 8 Sep 2017 22:50:13 +0300 Sergey Ryazanov
wrote:
> >> >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel
> >> >> messages log? If not then the mwswitch driver did not attached and
> >> >> you should fix this first. And only then go to the interface
>
On Tue, 3 Oct 2017 03:27:21 +0300 Sergey Ryazanov
wrote:
> After these lines, I carefully examine available data about WRT300Nv2
> and related code and found several interesting things.
>
> Usually SoC in the router have only one ethernet interface and vendors
> pair it with manageable switch I
On Sun, 8 Oct 2017 23:44:58 +0300 Sergey Ryazanov
wrote:
> > I assigned IP with a command
> > ip a a 192.168.0.10/24 dev eth0
> >
> > but ping from PC does not answer.
>
> Have you bring eth0 UP? I mean, could you do "ifconfig eth0
> 192.168.0.10 up" and try pinging again?
Just tried:
# ifconfi
On Mon, 9 Oct 2017 01:31:29 +0300 Sergey Ryazanov
wrote:
> > Just tried:
> > # ifconfig eth0 192.168.0.10 up
> > ifconfig: SIOCSIFFLAGS: Out of memory
> > # dmesg|grep eth
> > [0.998445] eth0: MII PHY 32 on NPE-B
> > [1.005134] eth1: MII PHY 1 on NPE-C
> > [6.540687] eth0: link up, s
On Wed, 11 Oct 2017 02:07:00 +0300 Sergey Ryazanov
wrote:
> Ok. I am starting to run out of ideas. Let's start guessing.
>
> eth0 works at least during preinit. You could check your switch
> functioning in the failsafe mode:
> 1. Power on router
> 2. When the "Press the [f] key and hit [enter]"
On Wed, 11 Oct 2017 14:53:16 +0300 Sergey Ryazanov
wrote:
> Ok. At least we know now that the switch functioning (even without a
> dedicated driver). One question left: what happens to the Ethernet
> driver?
>
> Can you boot your router in failsafe mode again, and try to toggle
> eth0 down/up?
On Wed, 11 Oct 2017 18:53:40 +0300 Sergey Ryazanov
wrote:
> A-ha! The interface survives the down/up circle but does not survive
> the init procedure.
>
> Try to completely avoid bridge usage, e.g.:
> 1. boot in normal mode
> 2. disable bridge usage on "lan":
> # uci delete network.lan.type
On Wed, 11 Oct 2017 22:50:40 +0300 Sergey Ryazanov
wrote:
> Khm, according to wikidevi your router is equipped with 16MB of RAM,
> the ethernet driver for xscale SoCs attempts to allocate almost a 1 MB
> of memory for buffers, so may be there are really no free memory for
> them.
Yes, RAM is 16
On Wed, 11 Oct 2017 23:28:00 +0300 Sergey Ryazanov
wrote:
> > root@LEDE:/# cat /proc/meminfo
> > MemTotal: 12232 kB
> > MemFree: 996 kB
>
> Looks like this ^^^ is the cause of the "ifconfig up" failure. Your
> board really have not free RAM.
>
> As a quick test, can you un
On Thu, 12 Oct 2017 00:15:15 +0300 Sergey Ryazanov
wrote:
> >> As a quick test, can you unload all kernel modules and try to set eth0 UP
> >> again?
> >
> > Unfortunately rmmod with a list of modules does not work:
> > # rmmod ip_tables ip6_tables ip6t_REJECT ...
> > Usage:
> > rmmod mo
On Thu, 12 Oct 2017 01:30:35 +0300 Sergey Ryazanov
wrote:
> Try this patch, it should reduce the memory demand of the ethernet
> driver, so it will have the change to get started on your router.
>
> Just put it to target/linux/ixp4xx/patches-4.4 along with the previous
> one and rebuild your fi
On Thu, 12 Oct 2017 03:11:21 +0300 Sergey Ryazanov
wrote:
> > I assume the new board type should be added to the config file,
> > for which this patch should be enabled?
>
> I do not think so. These two patches are just a quick hacks to fix
> common underlying issues.
>
> The first patch compl
On Sat, 14 Oct 2017 17:48:12 +0300 Nerijus Baliunas
wrote:
> Thank you. Another question about wifi - there is no /etc/config/wireless
> file, and even if I create it and reboot the device, wifi is not working
> and there is no wlan0 interface. ath5k module is loaded.
WRT300N v2 h
Hello,
Wifi MAC is correct, corresponds to one of the MACs written on the box, but all
other
MAC addresses (br-lan, eth0, eth0.1, eth0.2) are 00:11:22:33:44:55.
Regards,
Nerijus
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lis
Hello,
I have a problem that all MAC addresses are 00:11:22:33:44:55 except wlan0,
which is correct. Should this patch help me? I added "nbg-419n" to the case
line:
case $(ramips_board_name) in
bc2 | nbg-419n | nw718)
extract_and_set_mac "factory" 4 "02:00:00:00:00
On Fri, 2 Dec 2011 15:51:44 +0200 Roman Yeryomin wrote:
> > I have a problem that all MAC addresses are 00:11:22:33:44:55 except wlan0,
> > which is correct. Should this patch help me? I added "nbg-419n" to the case
> > line:
> > case $(ramips_board_name) in
> > bc2 | nbg-419n | nw
On Mon, 5 Dec 2011 03:20:54 +0200 Nerijus Baliunas
wrote:
> > if you will look at my or Alexander's patch you'll see that the mac
> > can potentially be anywhere.
> > For example on belkin board it's here -> "u-boot" 262148.
> > So you just h
On Mon, 5 Dec 2011 20:36:47 +0200 Nerijus Baliunas
wrote:
> Then modified target/linux/ramips/base-files/lib/preinit/06_set_iface_mac as
> written above,
> make clean, make and flashed firmware. Any ideas why didn't it work? My board
> is
> ZyXEL NBG-419N.
Latest svn f
lifire is a trademark owned by CCS
>
>
> On 25/11/2011, at 11:35 AM, Nerijus Baliunas
> wrote:
>
> > Hello,
> >
> > Wifi MAC is correct, corresponds to one of the MACs written on the box, but
> > all other
> > MAC addresses (br-lan,
Hello,
Latest trunk, the client is re-requesting its IP addr continuously every 5-20
seconds:
Jan 1 01:00:35 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:1e:92:bf IEEE
802.11: authenticated
Jan 1 01:00:35 OpenWrt daemon.info hostapd: wlan0: STA 18:f4:6a:1e:92:bf IEEE
802.11: associated (
On Mon, 02 Jan 2012 16:00:26 +0100 Jo-Philipp Wich wrote:
> It seems to correlate with the WPA rekeying. You could try to lower the
> group rekey interval and see if it helps.
Do you mean wpa_group_rekey? It seems to be 600 by default, what should I set
it to?
Regards,
Nerijus
On Tue, 3 Jan 2012 02:08:42 +0200 Nerijus Baliunas
wrote:
> > It seems to correlate with the WPA rekeying. You could try to lower the
> > group rekey interval and see if it helps.
>
> Do you mean wpa_group_rekey? It seems to be 600 by default, what should I set
> it to
Hello,
I've updated from svn trunk and udpxy package no longer compiles:
mipsel-openwrt-linux-uclibc-gcc -Os -pipe -mips32r2 -mtune=mips32r2
-fno-caller-saves -fhonour-copts -msoft-float
-I/a/openwrt/kamikaze/staging_dir/target-mipsel_r2_uClibc-0.9.33/usr/include
-I/a/openwrt/kamikaze/staging
35 matches
Mail list logo
