Re: [PATCH] ubifs: Handle re-linking of inodes correctly while recovery

g Reported-by: Russell Senior Reported-by: Rafał Miłecki Signed-off-by: Richard Weinberger Tested-by: Russell Senior --- Russel, Rafał, please give this patch another testing. I'll also run it on different test systems before merging. Thanks, //richard --- fs/ubifs/rep

Re: [PATCH] ubifs: Handle re-linking of inodes correctly while recovery

g Reported-by: Russell Senior Reported-by: Rafał Miłecki Signed-off-by: Richard Weinberger Tested-by: Russell Senior --- Russel, Rafał, please give this patch another testing. I'll also run it on different test systems before merging. Thanks, //richard --- fs/ubifs/rep

Re: [LEDE-DEV] DHCP via bridge in case of IPv4

abled I may see that > wireless client sends "DHCP >> Discover" then server replies with "DHCP Offer" but > that offer >> never reaches wireless client. >> >> >> Do you have WDS enabled? If not, DHCP has issues in that scenario: >> https://wiki.openwrt.org/doc/howto/clientmode If the Dumb AP's wireless interface is in ap-mode, then this shouldn't be an issue. It's only client-mode interfaces that have trouble with bridging. I'd suggest running tcpdump on the Dumb AP's wireless interface and the client's wireless interface and see which of them sees the various parts of the DHCP handshake. -- Russell Senior, President russ...@personaltelco.net

Re: [LEDE-DEV] DHCP via bridge in case of IPv4

iscover" then server replies with "DHCP Offer" but > that offer >> never reaches wireless client. >> >> >> Do you have WDS enabled? If not, DHCP has issues in that scenario: >> https://wiki.openwrt.org/doc/howto/clientmode If the Dumb AP's wireless interface is in ap-mode, then this shouldn't be an issue. It's only client-mode interfaces that have trouble with bridging. I'd suggest running tcpdump on the Dumb AP's wireless interface and the client's wireless interface and see which of them sees the various parts of the DHCP handshake. -- Russell Senior, President russ...@personaltelco.net

tulip: no link beat, media switching to 10Base2

kernel (2.4.1) using TULIP_DEFAULT_MEDIA and TULIP_NO_MEDIA_SWITCH, but I noticed in the ChangeLog for 2.4.4 that these features were removed. How do I get reliable 10BaseT operation inspite of possible cabling disconnections. -- Russell Senior ``The two chiefs turned to each other

tulip: no link beat, media switching to 10Base2

kernel (2.4.1) using TULIP_DEFAULT_MEDIA and TULIP_NO_MEDIA_SWITCH, but I noticed in the ChangeLog for 2.4.4 that these features were removed. How do I get reliable 10BaseT operation inspite of possible cabling disconnections. -- Russell Senior ``The two chiefs turned to each other