User Tools

Site Tools


technical_logs:401_richmond

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
technical_logs:401_richmond [2009/06/03 13:56]
66.207.208.122
technical_logs:401_richmond [2013/09/28 16:06] (current)
Line 1: Line 1:
 +====== April 27, 2011 ======
 +Ali phoned again today, saying that the POS stopped working soon after I left yesterday. (I had forgotten to disable wifidog on startup.) I already had a new router with me (with a "​broken bridge"​ -- info on how to set that up is now on the router setup instructions page on this wiki), so I popped by and installed it. I had forgotten that Beanfield locks DHCP to the MAC address, so I had to change the MAC address of the WAN interface (instructions below). All working now.
 +
 +====== April 26, 2011 ======
 +Ali phoned today, saying that he got a new POS, but that it can't get online. (This is expected; we're still using a MAC-address-based whitelist.) To get it working quickly, I just turned off the wifidog gateway (wdctl stop), but this is only a temporary solution, because now authentication is off for that node. I told him I'd swap in a new router later this week. I need to figure out how to break the bridge so that we can have authentication on the wifi network and none on the Ethernet ports.
 +
 +====== April 21, 2011 ======
 +Ali phoned me today, saying that the router is cutting out sometimes, and it knocks out the POS machine. I said I'd come in in the afternoon to take a look. I got there at 4:30 and Ali had already left. The wifi seemed to be working fine. It had rebooted a few times today: 2:22pm, 4:08pm and 4:49pm. (This, according to the wifidog logs on auth. To get this, I did: "grep wifidog-201104.log | grep gw_id=23 | grep uptime | tail 500". But Ali phoned me at noon, and the router hadn't rebooted since at least 9am. Staff said the POS machine had been down since sometime yesterday. I plugged my laptop in the POS Ethernet cable, and it worked fine. So the Ethernet is working fine. No-go with the POS, though. The cable connecting the handheld part to the base part is clearly damaged; it's awkwardly wrapped in electrical tape. When you jostle it in the least bit, the machine beeps. The Ethernet cable plugs into the base. I'm guessing that the wires that enable network access to the handheld part are damaged. The POS machine or the cable need to be replaced. ​
 +
 +====== January 10, 2011 ======
 +They got a new debit machine, and Ali called me 'cause it wasn't working. ​ The ideal solution here would be to keep the ethernet ports open, but I need to figure out how to do that and test it.  For now, I just whitelisted the MAC address for the new POS.
 +
 +  #debit machine (pre-Jan 2011), debit machine (Jan 2011), Ali's laptop ​          
 +  TrustedMACList 00:​03:​81:​be:​64:​7d,​00:​0b:​4f:​1c:​ba:​73,​00:​18:​de:​4b:​83:​35
 +
 +
 +====== September 23, 2010 ======
 +They got a debit machine which they want to connect to the Internet, and the momentary switch broke, so some changes were in order. ​ I've been a few times in the past week; today I swapped in a new router (the one before flaked out a lot, and was running old versions of OpenWRT and Wifidog), moved the router (it's now on the wall within reach, not on the ceiling), and removed the momentary switch. ​ Everything seems to be working, but when I had to leave the debit machine hadn't received an IP address from the router. ​ I'll go back to check in later today or tomorrow. ​ I whitelisted the debit machine and Ali's laptop.
 +
 +One trick, though... The new router wasn't getting a DHCP address on the Ethernet interface. ​ I plugged my laptop into it, and it too didn't get a DHCP address. ​ I think the Beanfield network is refusing to assign an address to the unrecognized devices. ​ I changed the MAC address on the new router to match the one on the old router.
 +
 +Old vlan1 address on that router (#85): 00:​23:​69:​B3:​CE:​9D (NOTE: this is the MAC address printed on the bottom of the case PLUS ONE. The MAC address on the bottom of the case ends in 9C.)
 +
 +  ifconfig vlan1 down
 +  ifconfig vlan1 hw ether 00:​14:​BF:​38:​FB:​C6
 +  ifconfig vlan1 up
 +  udhcpc -i vlan1 -r 0.0.0.0 -b -p /​var/​run/​vlan1.pid -R
 +
 +It worked. ​ So then I made the change permanent:
 +
 +  nvram set wan_hwaddr=00:​14:​BF:​38:​FB:​C6
 +  nvram commit
 +
 ====== June 3, 2009 ====== ====== June 3, 2009 ======
  
technical_logs/401_richmond.1244055390.txt.gz ยท Last modified: 2013/09/28 16:06 (external edit)