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 [2011/04/26 14:52]
gabe
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 ====== ====== 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. 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.
Line 17: Line 20:
 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. 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+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 down
technical_logs/401_richmond.1303847564.txt.gz ยท Last modified: 2013/09/28 16:06 (external edit)