Issues with lamobo-r1 and new distribution

[badrianiulian]

Hello

I had installed on my lamobo-r1 as of this afternoon, armbian 5.20... I then decided to upgrade to 5.23 and after that networking went haywire... nothing worked anymore

 

"swconfig list" showed nothing as if module for the broadcom switch wasn't loaded

 

After the last buggy updates I'm almost afraid to upgrade anymore... what if anything else breaks in the process

 

Right now I'm back to 5.20 with hold on "linux-dtb-next-sunxi linux-firmware-image-next-sunxi linux-headers-next-sunxi linux-image-next-sunxi linux-jessie-root-next-lamobo-r1 linux-u-boot-lamobo-r1-next"

 

Very bad "puttycat"... quite sad actually I was really hoping some improvement since I do get some freezes once in a while... winter is coming and right now I can't hope anymore to rely on the R1 to use as a thermostat ...

 

[Tido]

And what are these for, is this necessary at shutdown ?

Does this improve certain states ?

 

lamobo-r1 routerdown

lamobo-r1 switchdown

[badrianiulian]

I've noticed that when restarting network service (/etc/init.d/networking restart) the network speed slows down... so by deleting the created vlans and recreating them at network init, everything goes as it should

[Esteban Siravegna]

Impressive job!


​Currently testing the router, non ppp versión. I've found several issues so far.

I'm trying to replace and aging TPLink with OpenWRT, which receives Internet from an ancient Scientific Atlanta 2100 cablemodem, via Ethernet (so, the cablemodem acts as a router of sorts, with its own DHCP server).

 

When connecting the Cablemodem to the wan port, I got IP, but it seems I can't connect to anything.

When connecting my notebook to the Lamobo, I got IP, ping trough, and can do an ssh. However, I can't ping FROM the lamobo to the notebook, albeit I can provide a working DHCP server (with DNSMASQ). Nskookup from the lamobo to the notebook Works just fine.

 

When plugging a patchcord from the TPLink into the Lamobo, and setting a different network in the board (thus using the TPLink as a 'cablemodem' from the lamobo perspective), got a valid ip, can connecto to the net, however, my inability to ping anything connected to br0 from the lamobo remains.

 

Any ideas would be most welcomed, thanks!

 

I've noticed that when restarting network service (/etc/init.d/networking restart) the network speed slows down... so by deleting the created vlans and recreating them at network init, everything goes as it should

[badrianiulian]

Impressive job!

 

 

​Currently testing the router, non ppp versión. I've found several issues so far.

I'm trying to replace and aging TPLink with OpenWRT, which receives Internet from an ancient Scientific Atlanta 2100 cablemodem, via Ethernet (so, the cablemodem acts as a router of sorts, with its own DHCP server).

 

When connecting the Cablemodem to the wan port, I got IP, but it seems I can't connect to anything.

When connecting my notebook to the Lamobo, I got IP, ping trough, and can do an ssh. However, I can't ping FROM the lamobo to the notebook, albeit I can provide a working DHCP server (with DNSMASQ). Nskookup from the lamobo to the notebook Works just fine.

 

When plugging a patchcord from the TPLink into the Lamobo, and setting a different network in the board (thus using the TPLink as a 'cablemodem' from the lamobo perspective), got a valid ip, can connecto to the net, however, my inability to ping anything connected to br0 from the lamobo remains.

 

Any ideas would be most welcomed, thanks!

Witch distribuiton are you using? I had the same problems when using Ubuntu Xenial Mainline 4.9.7 image ... even if setting in sysctl.conf the forwarding settings.

Right now I'm on Debian Jessie Mainline 4.9.7 (upgraded from an older version)

[Esteban Siravegna]

Xenial Indeed. Thanks for the tip

[badrianiulian]

As of today 11:31 AM, my uptime reports: up 20 days, 12:26

Due to the fact that my R1 router is also a web server and every three or four days I had to shut it down to get things working again, I'd say that the new dsa config with the new b53 driver works quite well