Dumb question: Should either modem make noise?

[hawkzer0]

I'm confused by your DMZ setup I guess. The address your pi gives you on boot up isn't the DC's address. They will both show up on your router's screen once the DC connects online.

[TheGrandPubaa]

Right now, nothing is DMZ'd, and since I reflashed DreamPi, the Pi's IP changed back to 192.168.0.14. I'll try again, but I don't see the Dreamcast showing an IP on the Router when it connects to the Pi either on the "DHCP Lease Table" or "Translated Address." I've noticed I get the following log output a few minutes after connecting the DC to the Pi:

Feb 23 15:02:17 dreampi Couldn't update Dreamcast Now!#012Traceback (most recent call last):#012 File "/home/pi/dreampi/dcnow.py", line 69, in run#012 post_update()#012 File "/home/pi/dreampi/dcnow.py", line 65, in post_update#012 urllib2.urlopen(req) # Send POST update#012 File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen#012 return _opener.open(url, data, timeout)#012 File "/usr/lib/python2.7/urllib2.py", line 401, in open#012 response = self._open(req, data)#012 File "/usr/lib/python2.7/urllib2.py", line 419, in _open#012 '_open', req)#012 File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain#012 result = func(*args)#012 File "/usr/lib/python2.7/urllib2.py", line 1219, in https_open#012 return self.do_open(httplib.HTTPSConnection, req)#012 File "/usr/lib/python2.7/urllib2.py", line 1181, in do_open#012 raise URLError(err)#012URLError: <urlopen error [Errno -2] Name or service not known>

I took a screenshot of my router's DHCP leases page with some stuff whited out.

[SEGA RPG FAN]

Doesn't the Pi try to request certain IP addresses (192.168.0.99 and .98)? I'm not sure why it would be giving you 192.168.0.14. Delete its current lease in your config. Go to the LAN >DHCP server config tab of the motorola and change the number of DHCP users to something less than 96. The default of 253 covers 192.168.0.98 and 99. I've found that some routers don't like when a client requests an IP inside its DHCP range. Also, verify that your LAN subnet mask is 255.255.255.0.

[pcwzrd13]

Doesn't the Pi try to request certain IP addresses (192.168.0.99 and .98)? I'm not sure why it would be giving you 192.168.0.14.

192.168.0.14 would be the IP of the Pi which is acquired via DHCP. The IP of the Dreamcast is statically assigned 192.168.0.98.

[SEGA RPG FAN]

Doesn't the Pi try to request certain IP addresses (192.168.0.99 and .98)? I'm not sure why it would be giving you 192.168.0.14.

192.168.0.14 would be the IP of the Pi which is acquired via DHCP. The IP of the Dreamcast is statically assigned 192.168.0.98.

Ok, got it. I would still try reducing the number of DHCP users.

[Xerxes3rd]

Yeah, the DreamPi uses arping to try and detect if 192.168.x.99 and 192.168.x.98 are in-use. If they're not in-use, it'll assign them to its own PPP adapter and the Dreamcast (respectively). If those IPs are taken, it starts decrementing the last octet until it finds available IPs or runs out.

I had considered adding proper DHCP support to DreamPi (there are a couple Python DHCP client libraries that could be pretty easily dropped in), but having the Dreamcast get assigned 192.168.x.98 in most (if not all) cases makes troubleshooting and DMZing a lot easier.

[TheGrandPubaa]

Success.

So, basically everything I tried(port forwarding, reducing the number of DHCP users, hooking the Pi directly to the Router, etc.) had no effect on my Dreamcast's ability to load a page once it connected to the internet. The trick was the gaming DMZ, naturally, even for the web browser to work. If you'll recall earlier in this thread, I mentioned that I couldn't set the Dreamcast as DMZ because my Motorola SBG900 Router/Cable Modem required a MAC address for the IP that was to be the gaming DMZ, and of course, the Dreamcast doesn't have one.

Eventually, I randomly generated a MAC address using a website, inputted it as the fake address for the Dreamcast, used 192.168.0.98 for the IP, checked the bypass firewall option, named it DreamcastModem, applied it, and then set DreamcastModem as the gaming DMZ which is when it finally worked. I haven't tested anything but XDP Browser yet, but this is working well so far.

TL;DR: For Motorola SBG900 Routers/Cable Modems, set 192.168.0.98 as the gaming DMZ with a randomly generated MAC address to successfully connect to the internet - at least in the browser.

[hawkzer0]

nice! glad you got it working! yea its almost always something with the router when a dreampi doesnt work. that seems like a bit of a process but good to know for anyone in the future that might use that router.

what games do you have?

[TheGrandPubaa]

As far as physical copies go, I have PSOV2, 4x4 Evolution, and I used to have but subsequently lost Starlancer. I've got a GDEmu installed in my Dreamcast as well, and an SD card adapter for the serial port.