DreamPi Software (DC <> Pi)

I'm not sure if there was a response but the router said the packets were received. This was in router menu, not cmd

 

I'm not really sure why it's not working then - if the DC is responding to pings

@TerdFerguson I've been meaning to make the IP detection code better (it currently uses "arp" which doesn't work, it should "arping" instead), but I won't have time to do that for a while

 

Since it was working before i'm going to try formatting the SD card and reinstalling the image

Edit: No change. I'll keep trying things. I'll probably make a new line voltage with a different cable when my other 9v battery clips finally show up

Update: Made second inducer, cleaner this time, no change. It's either the Pi's ethernet port or something in the network

Update: Factory reset router, no change. It must be the Pi's ethernet port

 

This build works 100% of the time on Dell RD02 (and other) modems and US Dreamcasts with voltage inducers or a phone line simulator, AND it includes Dreamcast Now:
https://onedrive.live.com/redir?resid=D4C0AF674C4148FE!157667&authkey=!ACE96mStjMjPTn8&ithint=file,img

I've never claimed to be part of any sort of development team for DreamPi.
In fact, there clearly is no team. Best of luck, all!

 

I've just pushed version 1.2: http://blog.kazade.co.uk/2016/01/dreampi-12-released.html

This uses a fixed and lower baud speed to communicate with the modem, I'm hoping this is the underlying issue that requires Jon's workaround.

 

Have you tried accessing the outside world from the Pi itself? e.g. log into the Pi, and run "wget www.google.com" or something?

 

I think the issue is the DreamPi is making DCHP requests on 255.255.255.255 instead of 255.255.255.0 (my subnet). This is probably why the DreamPi's IP can be seen as active and the Dreamcast can connect but cannot communicate with the outside network because it's running on an improper subnet


Is there a file I can edit to correct the subnet to prevent me from waiting for a new release or something?

 

I've no idea what's going on there?! Basically the DreamPi image is set up to use DHCP over Ethernet, the problem seems to be that for some reason it's trying and failing to lease 192.168.1.98 on boot and I have no idea why..

The .98 and .99 IPs that I was referring to don't get used until you dial into a game. At that point the Dreamcast gets 192.168.1.98 (on your subnet) and the Raspberry Pi uses an additional IP address (192.168.1.99) to the one it's allocated on boot.

But your issue is happening far earlier. Have you changed the network settings on the Pi at all? Is there something in your routers configuration that tries to do something special with 192.168.1.98?

One possibility is that somehow your router has a really restrictive IP range for DHCP (e.g. only a few IP addresses around the .98 mark) and it's just running out - but that's a pretty far fetched possibility...

EDIT: Hold up! It's not receiving any DHCP offers at all?! It apparently can't reach the DHCP server on your router... maybe the ethernet port is just broken!

 

That is a possibility but my subnet is 255.255.255.0 (that's what my PC uses and what I use on BBA config at least) not 255.255.255.255. Or does this not matter?

But it was working before so it may just be the Ethernet port was defective and went bad quickly

Is there a way to manually change the subnet the Pi uses?

 

*Wrong Thread HerpBerp*

 

I cannot believe I posted this on the wrong thread lol I'll get a mod to delete it

 

I'm pretty sure that subnet mask is fine. It's just basically saying it's broadcasting discovery across the whole network range (I think).

There's definitely something funky going on, either the Ethernet is borked or it just can't see your router for some reason... it *is* connected to your network properly right?

 

Well considering it was working fine for a short time and nothing changed in the way it's setup, it's probably likely it is the ethernet port then. I ordered a wifi dongle yesterday

 

Alright, PROGRESS, thats what happens when you miss one step of the equation, only to find it later, and still do it wrong, i forgot to customize my settings in web browser so i could actually have something happen, i set everything to the information i found here:https://newagesoldier.com/getting-your-dreamcast-back-online-without-a-broadband-adapter/ to the letter, and depending on a single character i get one of two responses:
going of his screenshots, and setting my modem int to AT&F, after about 30 seconds to a minute of waiting, it says the ISP wont answer
going of the information on the site, and setting my modem int to AT&FO, the dreampi just sits there trying to dial for a very, very long time, i am typing this as i wait for a response, and its been at least 10-15 minutes,

i'll update IF it ever answers, if i wait more than a few more minutes with no further progress, im restarting the pi and dreamcast

this is using 1.2, by the way

EDIT: after about 20 minutes, i gave up and tried Q3A, and set my DNS to 46.101.91.123 witch i heard you had to put in to play Quake online, and that said there was no dial tone!, prehaps its the 9V batteries?

 

I don't usually post but I have to chime in here. The only modem that worked for me was this one listed on ebay: http://www.ebay.com/itm/NEW-Dell-Co...373865?hash=item2eea6af5a9:g:tVIAAOSw7hRWO5rR

I've tried the one that kazade linked to in his tutorial, but that one never worked for me. I've used a model A and B Dreamcast modem and they both needed power. I was using a cheap .79 battery which worked fine, but just decided to attach a 9v ac adapter to the line instead which works great. Every supported game works, with no errors whatsoever with this setup. Just get the above modem!

To know if your usb modem is the problem, log into your raspberry pi and type wvdialconf. If it says 'no modem detected' than your modem is the problem.

 

The Dell one should be linked on his site

It seems there's multiple branches of conexant modem chipsets. Mine is a DGC Conexant, works fine, another variant is HCF. However there is HSF, which is a softmodem (whatever the difference is, I know mine is a software modem, but maybe softmodem and software modem are two separate things). HSF does not work

It's hard to tell which one you're buying because they're generic. The best bet is to go with the Dell modems, or contact the eBay seller and ask which drivers for linux are on the CD, DGC, HCF, or HSF

The bright side of the issues you guys are having is other people are less likely to encounter them as they will be well documented once solved

-http://www.linuxant.com/drivers/

 

It's possible your line voltage inducer was not made properly. If something becomes disconnected in the inducer there will be no dial tone. That may be the cause of your issues. Because if there is not enough voltage for dial tone, then there is not enough voltage to transfer packets back and forth

It's also possible your modem is not compatible

Try that

 

well, the modem is the problem, it gave me the message "no modem detected, is it in use on another program?" ill probably get another and try again, or just set up a PC to DC server

 

http://www.amazon.com/Dell-Conexant...34128&sr=8-1&keywords=Dell+Conexant+RD02-D400

http://www.amazon.com/Dell-NW147-Ex...34128&sr=8-2&keywords=Dell+Conexant+RD02-D400

either should work... I really hope you can get online... I plan to build mine with my tax money if i have any left... but these two modems are the 2 people have had success with... also JON uses the NW147 in his prebuilt DreamPis

 

FWIW Jon had some problems with that modem, but I've also had plenty of people have had success with it, I wish I knew why! I've got one of those modems on order but apparently it's shipping from China so it might be a while

Hopefully 1.2 fixed it. Is anyone using one of Jon's kits with my 1.2 release? Does it work?