Re: [Dorset] OpenWRT
On Sun, 10 Feb 2019 13:23:38 +, Tim wrote: > First, I found the passphrase for my wifi stored on the router in > plain text format It's certainly not the first router operating system to do that. I found a feature request asking for Ubiquity access points to stop storing WiFi passwords in plain text: https://community.ubnt.com/t5/UniFi-Feature-Requests/Hashing-the-remaining-passwords-do-not-store-in-plain-text/idi-p/1590658#comments Someone please correct me if I'm wrong, but my understanding is that the mutual authentication feature of WPA2-PSK means that the access point must store either the plain text passphrase or the plain text secret that gets computed from it, either of which can be used to authenticate to the network if stolen. It seems to me that the best defence is therefore to avoid using the passphrase for anything except that one WiFi network, or else to use WPA2 Enterprise instead (which does not rely on a pre-shared key). > Secondly, when you login into the router via ssh you do so as root It is definitely possible to change that. You can add a less privileged user, enable key-based authentication for SSH and install sudo. I wonder if the default was a compromise made in order to limit the amount of software included in the base installation, due to the limited amount of flash memory found in router hardware. > to be fair when you login into the router via the web interface you > also do so as root. I never really liked that, especially since HTTPS is not enabled by default. I don't so much mind having to authenticate as root to perform administrative actions, but it does seem poor form to run the entire web server as root. Patrick -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT
I suspect the router would need to decrypt the wireless key if it were encrypted, so the configuration would have to have all the details required to decrypt it. I'm not sure I'd worry too much about people getting access to my WLAN key if they already have root access to the router. I doubt any non-OpenWRT routers are better. BT routers for example have the wireless key stored in plain text on a sticker on the router. Then there's those routers where the default SSID and key are based on the MAC address... which it broadcasts! -- Andrew. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-03-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT
On 29/01/2019 16:55, Tim wrote: On 27/01/2019 19:13, Tim wrote: On 27/01/2019 12:57, Patrick Wigmore wrote: On Mon, 14 Jan 2019 17:59:30 +, Tim wrote: If anybody has any stories regarding OpenWRT I would interested to hear them On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: Every time I'm in the market for a new broadband modem, like now, I consider buying one supported by OpenWRT, but never manage it. The last I checked, the only available ADSL or VDSL modem that OpenWRT appeared to actually have a driver for was the one inside the BT Home Hub 5 type A (a.k.a. Plusnet Hub One or BT Business Hub 5). It is not a badly specified device given how cheaply available they are. 802.11ac, 128MB RAM, 128MB flash, 500MHz CPU. I bought one and put OpenWRT on it. The main downsides I see are: * Though it has gigabit network interfaces, it is not capable of actually routing traffic at gigabit speeds. (I don't care about that: it's fast enough for me.) * It is too easy to press the prominently-located restart button while handling the device, causing an unwanted reboot. Presumably the stock firmware requires regular rebooting so they decided to make a feature out of it. * It makes a quiet ticking noise like a laptop hard drive when it is transceiving WiFi traffic. (This seems to be the power supply circuitry responding to the varying load, because connecting a USB- powered device that uses PWM to fade some LEDs up and down causes the Home Hub to provide an audible rendition of the PWM signal, providing many minutes of entertainment.) * Unlike the radio in my previous, lower-spec Buffalo device (also running OpenWRT), the WiFi radios don't seem to support operating simultaneously as both a client and an access point. Though, since it's dual band and has two radios, the unit as a whole can do this, provided you don't mind dedicating a whole frequency band (2.4GHz or 5GHz) to each of these functions. * It doesn't have many indicator LEDs (but all three are RGB, so you can squeeze quite a bit of information out through them). * No option for external WiFi antennae (it works well without them, but some people might have a specific reason why they need or want them). Its been very stable for me. The only unplanned downtime has been due to power failures. I've only tried the xDSL modem itself for an hour or two, to test it. Therefore, I can't vouch for the xDSL modem's long-term stability, but I was satisfied that it would probably do the job if I wanted it to. The modem took a loong time to make a connection on the first attempt: about half an hour. I put that down to the DSLAM on the other end of the line being surprised to see a different modem, but not before I went on a wild goose chase tweaking the configuration to see if anything would make it work. After the initial connection, it appeared capable of reconnecting much more quickly. On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: I realise their specialised devices, but I'm surprised that projects like OpenWRT don't settle on a collection of chips that they support very well, e.g. good quality Linux kernel drivers, and then see if they can crowdfund a device built around them. If you are acquiring new hardware, it seems to me that the only product category where there really seems to be a lack of OpenWRT compatibility is modems. If you just want a router or a WiFi access point, there are plenty of options. I speculate that it would be difficult to compete with the existing choice in those categories, but the xDSL modem-router category would be more fertile ground for a crowd-funded product. Patrick Wigmore It is a strange position that had I spent more time researching the router I purchased (Linksys WRT1900ACS) I may never have purchased it. To start with I can not block ports and this afternoon I found that snmp is not available and I can find no where to enable snmp within its current config (it does not reply to snmpwalk command). Googling seem to return plenty of replies regarding requests for new features (like SNMP). I guess this is the downside that a router is now seen as a consumer product and the average bod on the street is just interested in plug and play and not worried about blocking ports or checking your bandwidth usage. Had the funds been available I would have gone for a Draytec (I have used them at work in the past and quite happy with them) but I thought I was doing alright buying a Linksys, I had used Linksys routers many years ago just after getting cable Internet. I thought they were still owned by Cisco but found out after the purchase that they were sold on and bought by Belkin who's network products I have used in the past and found them to be rubbish. I blame nobody else but myself, I should of done my homework before the purchase. I will have to start planning the firmware upgrade to OpenWRT and pray that it gives me what I want as the
Re: [Dorset] OpenWRT
On 27/01/2019 19:13, Tim wrote: On 27/01/2019 12:57, Patrick Wigmore wrote: On Mon, 14 Jan 2019 17:59:30 +, Tim wrote: If anybody has any stories regarding OpenWRT I would interested to hear them On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: Every time I'm in the market for a new broadband modem, like now, I consider buying one supported by OpenWRT, but never manage it. The last I checked, the only available ADSL or VDSL modem that OpenWRT appeared to actually have a driver for was the one inside the BT Home Hub 5 type A (a.k.a. Plusnet Hub One or BT Business Hub 5). It is not a badly specified device given how cheaply available they are. 802.11ac, 128MB RAM, 128MB flash, 500MHz CPU. I bought one and put OpenWRT on it. The main downsides I see are: * Though it has gigabit network interfaces, it is not capable of actually routing traffic at gigabit speeds. (I don't care about that: it's fast enough for me.) * It is too easy to press the prominently-located restart button while handling the device, causing an unwanted reboot. Presumably the stock firmware requires regular rebooting so they decided to make a feature out of it. * It makes a quiet ticking noise like a laptop hard drive when it is transceiving WiFi traffic. (This seems to be the power supply circuitry responding to the varying load, because connecting a USB- powered device that uses PWM to fade some LEDs up and down causes the Home Hub to provide an audible rendition of the PWM signal, providing many minutes of entertainment.) * Unlike the radio in my previous, lower-spec Buffalo device (also running OpenWRT), the WiFi radios don't seem to support operating simultaneously as both a client and an access point. Though, since it's dual band and has two radios, the unit as a whole can do this, provided you don't mind dedicating a whole frequency band (2.4GHz or 5GHz) to each of these functions. * It doesn't have many indicator LEDs (but all three are RGB, so you can squeeze quite a bit of information out through them). * No option for external WiFi antennae (it works well without them, but some people might have a specific reason why they need or want them). Its been very stable for me. The only unplanned downtime has been due to power failures. I've only tried the xDSL modem itself for an hour or two, to test it. Therefore, I can't vouch for the xDSL modem's long-term stability, but I was satisfied that it would probably do the job if I wanted it to. The modem took a loong time to make a connection on the first attempt: about half an hour. I put that down to the DSLAM on the other end of the line being surprised to see a different modem, but not before I went on a wild goose chase tweaking the configuration to see if anything would make it work. After the initial connection, it appeared capable of reconnecting much more quickly. On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: I realise their specialised devices, but I'm surprised that projects like OpenWRT don't settle on a collection of chips that they support very well, e.g. good quality Linux kernel drivers, and then see if they can crowdfund a device built around them. If you are acquiring new hardware, it seems to me that the only product category where there really seems to be a lack of OpenWRT compatibility is modems. If you just want a router or a WiFi access point, there are plenty of options. I speculate that it would be difficult to compete with the existing choice in those categories, but the xDSL modem-router category would be more fertile ground for a crowd-funded product. Patrick Wigmore It is a strange position that had I spent more time researching the router I purchased (Linksys WRT1900ACS) I may never have purchased it. To start with I can not block ports and this afternoon I found that snmp is not available and I can find no where to enable snmp within its current config (it does not reply to snmpwalk command). Googling seem to return plenty of replies regarding requests for new features (like SNMP). I guess this is the downside that a router is now seen as a consumer product and the average bod on the street is just interested in plug and play and not worried about blocking ports or checking your bandwidth usage. Had the funds been available I would have gone for a Draytec (I have used them at work in the past and quite happy with them) but I thought I was doing alright buying a Linksys, I had used Linksys routers many years ago just after getting cable Internet. I thought they were still owned by Cisco but found out after the purchase that they were sold on and bought by Belkin who's network products I have used in the past and found them to be rubbish. I blame nobody else but myself, I should of done my homework before the purchase. I will have to start planning the firmware upgrade to OpenWRT and pray that it gives me what I want as the alternative is asking the wife for an
Re: [Dorset] OpenWRT
You might have to sell off some of the bits in the stockroom to fund a new router. If she is in to decluttering that will please her. Peter I blame nobody else but myself, I should of done my homework before the purchase. I will have to start planning the firmware upgrade to OpenWRT and pray that it gives me what I want as the alternative is asking the wife for an increase in the IT budget (for a new router) will not go down very well. Tim H -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT
On 27/01/2019 12:57, Patrick Wigmore wrote: On Mon, 14 Jan 2019 17:59:30 +, Tim wrote: If anybody has any stories regarding OpenWRT I would interested to hear them On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: Every time I'm in the market for a new broadband modem, like now, I consider buying one supported by OpenWRT, but never manage it. The last I checked, the only available ADSL or VDSL modem that OpenWRT appeared to actually have a driver for was the one inside the BT Home Hub 5 type A (a.k.a. Plusnet Hub One or BT Business Hub 5). It is not a badly specified device given how cheaply available they are. 802.11ac, 128MB RAM, 128MB flash, 500MHz CPU. I bought one and put OpenWRT on it. The main downsides I see are: * Though it has gigabit network interfaces, it is not capable of actually routing traffic at gigabit speeds. (I don't care about that: it's fast enough for me.) * It is too easy to press the prominently-located restart button while handling the device, causing an unwanted reboot. Presumably the stock firmware requires regular rebooting so they decided to make a feature out of it. * It makes a quiet ticking noise like a laptop hard drive when it is transceiving WiFi traffic. (This seems to be the power supply circuitry responding to the varying load, because connecting a USB- powered device that uses PWM to fade some LEDs up and down causes the Home Hub to provide an audible rendition of the PWM signal, providing many minutes of entertainment.) * Unlike the radio in my previous, lower-spec Buffalo device (also running OpenWRT), the WiFi radios don't seem to support operating simultaneously as both a client and an access point. Though, since it's dual band and has two radios, the unit as a whole can do this, provided you don't mind dedicating a whole frequency band (2.4GHz or 5GHz) to each of these functions. * It doesn't have many indicator LEDs (but all three are RGB, so you can squeeze quite a bit of information out through them). * No option for external WiFi antennae (it works well without them, but some people might have a specific reason why they need or want them). Its been very stable for me. The only unplanned downtime has been due to power failures. I've only tried the xDSL modem itself for an hour or two, to test it. Therefore, I can't vouch for the xDSL modem's long-term stability, but I was satisfied that it would probably do the job if I wanted it to. The modem took a loong time to make a connection on the first attempt: about half an hour. I put that down to the DSLAM on the other end of the line being surprised to see a different modem, but not before I went on a wild goose chase tweaking the configuration to see if anything would make it work. After the initial connection, it appeared capable of reconnecting much more quickly. On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: I realise their specialised devices, but I'm surprised that projects like OpenWRT don't settle on a collection of chips that they support very well, e.g. good quality Linux kernel drivers, and then see if they can crowdfund a device built around them. If you are acquiring new hardware, it seems to me that the only product category where there really seems to be a lack of OpenWRT compatibility is modems. If you just want a router or a WiFi access point, there are plenty of options. I speculate that it would be difficult to compete with the existing choice in those categories, but the xDSL modem-router category would be more fertile ground for a crowd-funded product. Patrick Wigmore It is a strange position that had I spent more time researching the router I purchased (Linksys WRT1900ACS) I may never have purchased it. To start with I can not block ports and this afternoon I found that snmp is not available and I can find no where to enable snmp within its current config (it does not reply to snmpwalk command). Googling seem to return plenty of replies regarding requests for new features (like SNMP). I guess this is the downside that a router is now seen as a consumer product and the average bod on the street is just interested in plug and play and not worried about blocking ports or checking your bandwidth usage. Had the funds been available I would have gone for a Draytec (I have used them at work in the past and quite happy with them) but I thought I was doing alright buying a Linksys, I had used Linksys routers many years ago just after getting cable Internet. I thought they were still owned by Cisco but found out after the purchase that they were sold on and bought by Belkin who's network products I have used in the past and found them to be rubbish. I blame nobody else but myself, I should of done my homework before the purchase. I will have to start planning the firmware upgrade to OpenWRT and pray that it gives me what I want as the alternative is asking the wife for an increase in the IT budget (for a new
Re: [Dorset] OpenWRT
On Mon, 14 Jan 2019 17:59:30 +, Tim wrote: > If anybody has any stories regarding OpenWRT I would interested to > hear them On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: > Every time I'm in the market for a new broadband modem, like now, > I consider buying one supported by OpenWRT, but never manage it. The last I checked, the only available ADSL or VDSL modem that OpenWRT appeared to actually have a driver for was the one inside the BT Home Hub 5 type A (a.k.a. Plusnet Hub One or BT Business Hub 5). It is not a badly specified device given how cheaply available they are. 802.11ac, 128MB RAM, 128MB flash, 500MHz CPU. I bought one and put OpenWRT on it. The main downsides I see are: * Though it has gigabit network interfaces, it is not capable of actually routing traffic at gigabit speeds. (I don't care about that: it's fast enough for me.) * It is too easy to press the prominently-located restart button while handling the device, causing an unwanted reboot. Presumably the stock firmware requires regular rebooting so they decided to make a feature out of it. * It makes a quiet ticking noise like a laptop hard drive when it is transceiving WiFi traffic. (This seems to be the power supply circuitry responding to the varying load, because connecting a USB- powered device that uses PWM to fade some LEDs up and down causes the Home Hub to provide an audible rendition of the PWM signal, providing many minutes of entertainment.) * Unlike the radio in my previous, lower-spec Buffalo device (also running OpenWRT), the WiFi radios don't seem to support operating simultaneously as both a client and an access point. Though, since it's dual band and has two radios, the unit as a whole can do this, provided you don't mind dedicating a whole frequency band (2.4GHz or 5GHz) to each of these functions. * It doesn't have many indicator LEDs (but all three are RGB, so you can squeeze quite a bit of information out through them). * No option for external WiFi antennae (it works well without them, but some people might have a specific reason why they need or want them). Its been very stable for me. The only unplanned downtime has been due to power failures. I've only tried the xDSL modem itself for an hour or two, to test it. Therefore, I can't vouch for the xDSL modem's long-term stability, but I was satisfied that it would probably do the job if I wanted it to. The modem took a loong time to make a connection on the first attempt: about half an hour. I put that down to the DSLAM on the other end of the line being surprised to see a different modem, but not before I went on a wild goose chase tweaking the configuration to see if anything would make it work. After the initial connection, it appeared capable of reconnecting much more quickly. On Sat, 26 Jan 2019 13:13:02 +, Ralph Corderoy wrote: > I realise their specialised devices, but I'm surprised that projects > like OpenWRT don't settle on a collection of chips that they > support very well, e.g. good quality Linux kernel drivers, and then > see if they can crowdfund a device built around them. If you are acquiring new hardware, it seems to me that the only product category where there really seems to be a lack of OpenWRT compatibility is modems. If you just want a router or a WiFi access point, there are plenty of options. I speculate that it would be difficult to compete with the existing choice in those categories, but the xDSL modem-router category would be more fertile ground for a crowd-funded product. Patrick Wigmore -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT
Hi Paul, > One thing to check carefully is the version of the router you have. > I bought a second Netgear WNDR3700 and ended up getting a version 5, > which unfortunately is totally different hardware and incompatible > with OpenWRT Every time I'm in the market for a new broadband modem, like now, I consider buying one supported by OpenWRT, but never manage it. It's partially the difficulty in asserting that the box being bought will still have the compatible innards, like your version 4 v. 5 problem, and also the general lack of modern devices available due to the lag in volunteer effort. I realise their specialised devices, but I'm surprised that projects like OpenWRT don't settle on a collection of chips that they support very well, e.g. good quality Linux kernel drivers, and then see if they can crowdfund a device built around them. I'd expect the manufacturers' reference designs, published to flog their chips, would be a help. There'd naturally be a bit of bike-shedding over what bells and whistles it needs, but some of that might easily fall out from the main SoC choice, etc. Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT (was Network connectivity issues)
On 15/01/19 17:52, Paul Tansom wrote: If you want to play there are plenty of budget routers to experiment with and some are even easily available through things like Freecycle / Freegle / Gumtree / etc.. My first one, which admittedly was with DD-WRT not OpenWRT, was a D-Link DIR615 that I picked up for free as it was badged as a Virgin router. It was only custom firmware on standard hardware, so could be re-flashed with the stock firmware (much like the Netear DG834 units used by Sky some years ago - I did well with free ones of those reflashed too stock allowing an easy VPN to parents and in-laws for IT support - there was an odd date bug in the log email code though that jumped the month back a couple of months at the end of the year). That I setup as a wireless access point with a straight forward install of DD-WRT. This was a handy cheap way of extending my wifi coverage. Actually, two of the access points (original post) are WRT54G running DD-WRT. Tim -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT (was Network connectivity issues)
** Tim [2019-01-14 17:59]: > > I see that sometimes with my access point. It seems to pass traffic fine on > > the > > wired connections, and several existing wireless connections work fine, but > > new > > ones and the odd existing one and indicate they are working, but completely > > fail when it comes to actually using anything on the network. After a while > > they stop picking up DHCP leases (likely beause my AP doesn't handle that > > as my > > config is beyond its capabilities - or was historically). After a while (if > > I > > leave it that long) other devices start failing to route traffic too. > > > > I have found the same issue with my the Billion BiPAC 7800N, the replacement > > Netgear WNDR3700, the next replacement TP-Link TL-WDR3600 and the current > > Netgear WNDR3700 with OpenWRT installed (which is actually much better, but > > still not perfect). > > > > The Netgear was aimed at improving performance, but was replaced because > > there > > were two features on it that I needed that couldn't be used at the same time > > (from memory VPN and IPv6). The TP-Link was replaced because it seems that > > it > > doesn't support IPv6 with the majority of ISPs in the UK (hard coded a /64 > > when > > most supply a /56). I'm still working on IPv6 on OpenWRT. I've got a tunnel > > with Hurricane Electric working, but not my native addresses from my ISP (I > > must have a decent conversation with them to confirm their setup). > > Comparing to > > the old Billion isn't helpful because that just had a tick box to enable > > IPv6 > > which 'just worked'! > > > > Anyhoo, I've strayed off the original thread! > > > I am considering putting WRT on my router, have to say that I am appalled at > the level of ability in its standard firmware, ever heard of a router that > can not block a port. > > If anybody has any stories regarding OpenWRT I would interested to hear them ** end quote [Tim] I was suprised how easy OpenWRT was to install, and have settled quite nicely into using an SSH connection to connect in and update packages (remembering to update the list as it isn't stored - understandably). This actually gives the option to automate it with Ansible, which only requires an SSH connection to work. If you want to play there are plenty of budget routers to experiment with and some are even easily available through things like Freecycle / Freegle / Gumtree / etc.. My first one, which admittedly was with DD-WRT not OpenWRT, was a D-Link DIR615 that I picked up for free as it was badged as a Virgin router. It was only custom firmware on standard hardware, so could be re-flashed with the stock firmware (much like the Netear DG834 units used by Sky some years ago - I did well with free ones of those reflashed too stock allowing an easy VPN to parents and in-laws for IT support - there was an odd date bug in the log email code though that jumped the month back a couple of months at the end of the year). That I setup as a wireless access point with a straight forward install of DD-WRT. This was a handy cheap way of extending my wifi coverage. One thing to check carefully is the version of the router you have. I bought a second Netgear WNDR3700 and ended up getting a version 5, which unfortunately is totally different hardware and incompatible with OpenWRT (annoyingly I knew this and when I added it to my eBay watch list it was listed as a v4, but when I checked after it arrived the listing had been changed with no way to track when the version was modified). The v4 is the best option with this model as it has more flash & ram and a faster processor). I should probably dig out the slides for my talk and get them up on the PLUG (http://portsmouth.lug.org.uk) website really! -- Paul Tansom | Aptanet Ltd. | https://www.aptanet.com/ | 023 9238 0001 Vice Chair, FSB Portsmouth & SE Hampshire Branch | http://www.fsb.org.uk/ = Registered in England | Company No: 4905028 | Registered Office: Ralls House, Parklands Business Park, Forrest Road, Denmead, Waterlooville, Hants, PO7 6XP -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT (was Network connectivity issues)
Hi, On Mon, Jan 14 at 05:59, Tim wrote: > > > I am considering putting WRT on my router, have to say that I am > appalled at the level of ability in its standard firmware, ever heard of > a router that can not block a port. > > If anybody has any stories regarding OpenWRT I would interested to hear them I run OpenWRT on a brace of Netgear WNR3500L v1. First time I installed (was running Tomato previously) it "just worked". These days because the routers are 9 years old the official firmware images on the openWRT website don't seem to be updated in a timely manner. So now I compile my own firmware from the GIT sources. It gives me more control on what's installed as well, I want IPv6 etc not silly printer apps which shouldn't be on a firewall in my opinion. Building from GIT was straight forward once I worked out that you have to follow the command ordering in the instructions exactly, don't invent smart shortcuts. I suspect some of the build dependencies ain't quite there breaking the shortcuts. Other good tip is invest in a USB/serial cable (or equivalent for your router) so you can plug into the serial console. Great for when you eventually come up with a firmware combo that doesn't run. Exact details of debug and debricking varies from router to router. -- Bob Dunlop -- Next meeting: BEC, Bournemouth, Tuesday, 2019-02-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] OpenWRT (was Network connectivity issues)
On 14/01/2019 12:23, Paul Tansom wrote: ** Tim [2019-01-13 16:39]: On 13/01/2019 14:47, t...@ls83.eclipse.co.uk wrote: Hi Ralph On 13/01/19 11:31, Ralph Corderoy wrote: Hi Tim, I'll just ask lots of questions in the hope it strikes lucky. I have a puzzling issue here, in that I can't see a laptop on my network from my own computer (normally I can ssh into the laptop just fine). Both are connected via Wifi. The laptop has a static IP. So both Computer and Laptop are *only* connected by Wi-fi. Yes. Computer's IP address is from the router's DHCP server. The Laptop's IP address is static. Is that last one done by having the DHCP server always dish out the same IP address for Laptop's MAC address, or the Laptop has it configured directly? If the latter, does the DHCP server know to steer clear of the static addresses when allocating dynamically? IP addresses are from third machine (server), which is running dhcpd dishing out addresses to Laptop and Computer. Laptop gets same IP address 192.168.2.8 from its MAC address, Computer gets its from a pool, 192.168.2.205. The DHCP server pool is well clear of the static IP's. Can Laptop see Computer, e.g. ping(1), when Computer can't see Laptop? No. All devices are on the same IP network, including the network mask? Yes. However, I can ssh into a third computer on the network How is Third connected? Also Wi-fi only? Static or dynamic IP address? Cabled, static IP 192.168.2.2. and from there can ping (and ssh into) the laptop. When Computer SSH's into Third, does w(1) show you've come from the Computer IP address you expect? Does `arp' show Computer's MAC address or that of an access point? w(1) shows 192.168.2.205 as expected. arp shows the MAC address of Computer, not an access point. Can Laptop SSH into Third? Ditto above WRT w(1). Haven't got SSH set up for SSH logins from Laptop to Third, although I expect it to work as these machines can see each other on the network. arp lists the laptop HWaddess as incomplete. There's also ip-neighbour(8) that gives `ip neigh' to show the table, and allows an entry to be added. When it's not working, you could try explicitly adding an ARP table entry to Computer for Laptop and see if that makes it work. OK, tried #ip neigh add 192.168.2.8 lladdr 00:24:d2:94:35:16 dev wlp1s0 RTNETLINK answers: File exists Further tests: Disconnecting both Computer and Laptop from the access point and then reconnecting both to a different access point. Now Computer cannot see Laptop /or/ Third computer. So disconnect Computer again and get physically close to the access point. Reconnect and now can see both. Repeat with original access point, ensuring in close proximity. Again can now see Laptop and Third from Computer. So looks like a poor Wifi signal on original connect may be a factor. I have seen something similar previously in terms of getting an IP address from the DHCP server. I appear to be connected to the network but have no IP address assigned to Computer. I am using Network Manager of XFCE and suspect that under weak Wifi conditions I'm only getting a partial connection. I have seen with some WiFi access point the have the "the lights are on but nobody is an home" syndrome, they look like they are working (lights etc) but seemed to get stuck in a loop, you can not talk to them you can not see them they are either limited in what they do or just don't do it at all. Turn the power off to them. wait 10 seconds and then turn it back on again and everything works as normal. Is there a firmware update available for your access point? ** end quote [Tim] I see that sometimes with my access point. It seems to pass traffic fine on the wired connections, and several existing wireless connections work fine, but new ones and the odd existing one and indicate they are working, but completely fail when it comes to actually using anything on the network. After a while they stop picking up DHCP leases (likely beause my AP doesn't handle that as my config is beyond its capabilities - or was historically). After a while (if I leave it that long) other devices start failing to route traffic too. I have found the same issue with my the Billion BiPAC 7800N, the replacement Netgear WNDR3700, the next replacement TP-Link TL-WDR3600 and the current Netgear WNDR3700 with OpenWRT installed (which is actually much better, but still not perfect). The Netgear was aimed at improving performance, but was replaced because there were two features on it that I needed that couldn't be used at the same time (from memory VPN and IPv6). The TP-Link was replaced because it seems that it doesn't support IPv6 with the majority of ISPs in the UK (hard coded a /64 when most supply a /56). I'm still working on IPv6 on OpenWRT. I've got a tunnel with Hurricane Electric working, but not my native addresses from my ISP (I must have a decent conversation with them to confirm their setup). Comparing to the old Billion
