Hey, are you still able to access the router remotely? I'm not seeing
any open ports from home. Unable to SSH, or get
https://door.sudoroom.org, or access the router at 50.0.83.158:8443.
Nmap sees nothing either. Is this a firewall problem? Or could
something have changed since you logged in before?
On Wed, May 29, 2013 at 3:58 PM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> I get paid finally on Friday. I have been literally to broke to make it out
> and I feel painfully bad about it …
[View More]:(
Aww please don't feel bad! We miss you but everything is ok otherwise. :)
[View Less]
> What is the new public IP?
door.sudoroom.org should resolve to it: 50.0.83.158
On Wed, May 29, 2013 at 3:52 PM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> If you changed the Static IP you have to change the Default Route, otherwise
> known as the "Gateway"
Right but we are literally in the same subnet with the same gateway.
Obviously if the gateway was wrong we'd have zero connectivity at all.
On Tue, May 28, 2013 at 8:24 AM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> The modem should be provided by the ISP and shouldn't require any config
> minus occasionally needing to disable the built in firewall. The Pix Device
> is the Firewall and Router. You only need to mess with firewall settings
> with mucking about with the port forwards. The rules in the firewall
> reference the "Outward facing Interface" so their IP information should
> adjust once the IP settings …
[View More]are changed.
So, I've followed all your instructions - we are on the exact same
subnet with the same default route, so all I had to change was our
static IP. I also noticed that the firewall rules referred to
"TheInternet-Interface" which still had our old IP, so I changed that
too. Right now we have connectivity through LMI, but it is relatively
slow, and there is a bizarrely recurring service outage of exactly 1
minute every 3 minutes, so no connectivity at these times:
2:39:38 until 2:40:38
2:42:38 until 2:43:38
......
3:09:38 until 3:10:48
... and so on.
I don't know enough about this machine to troubleshoot a whole lot.
I'm not even sure how to reboot it...
[View Less]
On Tue, May 21, 2013 at 12:13 PM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> It will.
> If you plug the modem into the other Ethernet port and give me the
> configuration i can do it from home. If not i can provide instructions, not
> sure if i'll be able to make it out this week tho :( still havn't gotten
> paid from my new job, stupid monthly paychecks...
I would love instructions on how to use our firewall. Thanks!
On Mon, May 20, 2013 at 3:13 PM, Yardena Cohen <yardenack(a)gmail.com> wrote:
>> Does anybody know how our router works? Does anybody have access to
>> it? I have been asking around for weeks and it is still not clear to
>> me...
>>
>> We are about to switch from Sonic.net to LMI. They are both running
>> concurrently at the moment, but Sonic service will end soon. They are
>> both static IP, so we need to access the router before we can start
…
[View More]>> using the new service.
On Tue, May 21, 2013 at 11:41 AM, Matthew Meier <wolfy(a)wlfy.it> wrote:
> I have access to the router, but the AP password has been changed since I
> set it.
Thanks for getting back!
Does anybody know who changed the AP password?
What else needs to change in order for us to switch WAN IPs? Does the
firewall need to be reconfigured as well?
[View Less]
Does anybody know how our router works? Does anybody have access to
it? I have been asking around for weeks and it is still not clear to
me...
We are about to switch from Sonic.net to LMI. They are both running
concurrently at the moment, but Sonic service will end soon. They are
both static IP, so we need to access the router before we can start
using the new service.
Ping Wolfy? :)
Hey all,
Upgraded MediaWiki to the latest version, installed a couple more
extensions (fancy editor like Wikipedia, and LiquidThreads for better
"Discussion" and "Talk" pages).
I tried to get the AuthWP extension (WPMW) to work again, but to no avail :(
Will revisit later.
// Matt
I'm trying to rename tamale.sudoroom.org to door.sudoroom.org. It
already works fine from outside the space. From within the space,
however:
tamale.sudoroom.org resolves to 192.168.1.2
door.sudoroom.org resolves to 50.0.83.116
This means packets to "tamale" get through but packets to "door" just
time out. I've already tried changing its hostname and rebooting, but
I suspect that a local DNS server is involved here and that we need
access to it.
It looks like DNS is being served by the …
[View More]Cisco AP running dd-wrt at
192.168.1.49 - is that true?
Does anybody have the user/password for that machine?
[View Less]
