Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: 3583Bytes on April 07, 2014, 04:24:00 AM
-
I need some help getting my Amiga 2000 on the internet. Currently I am trying to use a Raspberry Pi to connect to the Amiga via a USB to Serial & Null Modem Cable. I then want to use PPPD to provide internet to the Amiga.
Currently there is no clear tutorial on what settings are required on the Pi so I am trying to hobble together information from several different posts.
This one is on the Raspberry Pi but through serial rather then a USB to serial
http://jmp.no/blog/cheap-overkill-amiga-network-adapter
This video achieved exactly what I want but has no information how to setup the Pi with the exception of that pppd command which won't work (but it has all the Miami settings which is great)
https://www.youtube.com/watch?v=fEonOb5SkEg
So far I got as far making the connection between the Amiga and the Pi. Miami states:
Interface 'ppp0' is now online,
But when I ping or do anything I get a 100% packet loss
The command line I am using on the Pi is:
sudo pppd -detach /dev/ttyUSB0 19200 noauth local passive xonxoff persist 192.168.0.130:192.168.0.131
Where 192.168.0.130 is the address of the Raspberry Pi
Where 192.168.0.131 is a random IP address I selected that is not currently being used on the network.
Any other variation of the pppd command does not seem to work. I get an unable to connect message in Miami.
I enabled ip forwarding (at least I think I did) by
Editing:
/etc/sysctl.conf
Running:
sudo sysctl -p /etc/sysctl.conf
What am I missing
Any help would be apreciated
-
Have you read the comments on the blog? Pretty much explained there.
Also use a dedicated subnet for your rpi/amiga network.
-
Have you read the comments on the blog? Pretty much explained there.
Also use a dedicated subnet for your rpi/amiga network.
I have been at this for 2 days, I think I read every single post & comment related to this that google returned in the first 3 pages. I am ready to say that this may be beoynd me. If someone has done this and is willing to post their setup script I would be very greatfull.
Else a tutorial on how to do this would be great.
rewlako, I did not see anything on any of the posts about a deticated subnet, I am not even sure how to set that up on my router. Do you think this is the issue? Is there any way to test that I am at least hitting the Raspberry Pi and its a network issue?
-
You don't need to configure this on your router.
I just noticed that you chose some odd addresses for the rpi/amiga connection which makes me suspect you are using the same subnet as on your network.
Let's say your network is 192.168.0.x
On the Rpi, use IP 192.168.1.1
On the Amiga, use IP 192.168.1.2 with gateway 192.168.1.1
The Rpi will route traffic from 192.168.1.x to 192.168.0.x.
I have spoken with the author earlier and can ask for his assistance if you still can't make it work
-
You don't need to configure this on your router.
I just noticed that you chose some odd addresses for the rpi/amiga connection which makes me suspect you are using the same subnet as on your network.
Let's say your network is 192.168.0.x
On the Rpi, use IP 192.168.1.1
On the Amiga, use IP 192.168.1.2 with gateway 192.168.1.1
The Rpi will route traffic from 192.168.1.x to 192.168.0.x.
I have spoken with the author earlier and can ask for his assistance if you still can't make it work
Thank you so much for responding.
I will try tonight and let you know if it works,
One question, my raspberry Pi's IP address is 192.168.0.130, should I first force DHCP to give it 192.168.1.130?
Thanks
-
I haven't done this in ages, but I would think the Raspberry Pi would need 2 IPs.
It would get an IP from your router that should be in the same subnet that the router is in.
But the Pi should have a different IP/subnet for handing out IPs to devices via the serial (or just talking to them if you are manually assigning the IP on the Amiga).
So, your Pi has a 192.168.0.130 IP address (I am guessing that's a /24 so the whole 192.168.0.x subnet is there..).
Then, you Pi would have another IP in a different subnet, say 192.168.1.1/24.
When the Amiga connects via serial, it gets an address in that network, maybe 192.168.1.10.
The Pi then routes traffic between the 2. So the Amiga's default gateway would be 192.168.1.1.
(Or you could use iptables or ipchains and NAT the Amiga to the other network rather than "route" it...)
This might be pretty old info tho, as I said, it's been ages since I did this..
desiv
-
What desiv said. The Pi will have 2 IPs, one for your Amiga/Rpi network (locally) and one for the network you have the other computers connected to. The Amiga won't be able to tell.
Let me know how it works out
-
What desiv said. The Pi will have 2 IPs, one for your Amiga/Rpi network (locally) and one for the network you have the other computers connected to. The Amiga won't be able to tell.
Let me know how it works out
I don't understand how to give my Pi 2 ip addresses. I mean one IP address is given to the wireless interface by DHCP, I have no idea how to get the router to give it a second IP address to the Pi or even what interface would use it. Or are these just made up number that do not exist on my router but are just used internally within the Pi?
Sorry, networking is not my strength.
-
Haven't done this in ages or tested this, but this page seems to be describing what you want, except it's Win95 instead of an Amiga... But the Linux config should be similar (although it's an older config, and not Pi specific.)
http://totalizator.wordpress.com/2012/10/03/connect-windows-95-to-the-internet-using-linux-box-and-rs-232-serial-port-null-modem-cable/
Interesting side note: i just (yesterday) got a Pi and this is on my list of things to do, so I'll probably be trying this out myself before too long.. ;-)
desiv
-
Haven't done this in ages or tested this, but this page seems to be describing what you want, except it's Win95 instead of an Amiga... But the Linux config should be similar (although it's an older config, and not Pi specific.)
http://totalizator.wordpress.com/2012/10/03/connect-windows-95-to-the-internet-using-linux-box-and-rs-232-serial-port-null-modem-cable/
Interesting side note: i just (yesterday) got a Pi and this is on my list of things to do, so I'll probably be trying this out myself before too long.. ;-)
desiv
Great tutorial, thanks,
However I am still not sure what the IP addresses represent in that tutorial I still don't get if I should just make up a pair for the PPP process or do they somehow have to tie into my router.
If you ever get this going on the Pi please post a tutorial,
Thanks
-
> have to tie into my router
You don't. The RPi will act as a second router and take care of all that traffic.
I've sent a request to the author of the jmp.no blog to make a step-by-step tutorial.
-
However I am still not sure what the IP addresses represent in that tutorial I still don't get if I should just make up a pair for the PPP process or do they somehow have to tie into my router.
In this tutorial, the IP addresses are just for the linux box to client side.
So in your case, that would be your Pi to Amiga network.
Your Pi will still have it's own IP that it gets from your router..
The only thing you need to make sure is that they are in different subnets.
So, if your router is handing out IPs in the 192.168.0.0/24 range, your PPP config'd range should be 192.168.1.0/24. Changing that 3rd octet makes it a different subnet for a /24 (255.255.255.0) range.
Now that I look at it, I'm not sure all of it is totally applicable.. These lines:
192.168.1.201:192.168.1.200
ms-dns 192.168.1.1
The first one says, I believe, your linux boxes (the Pi) IP for this range will be 192.168.1.201 and your client will get 192.168.1.200
The next line sets the DNS server, but you're going to want that to be the IP of your router most likely, and not 192.168.1.1. That IP, being in the same range as the PPP network, but not being the linux host (that would assume your linux host is doing DNS) is confusing.
Of course, that's pretty old documentation, so it will be interesting to see if anything has changed... ;-)
desiv
-
Well this is the command I am running so far:
sudo pppd nodetach /dev/ttyUSB0 19200 noauth local passive ms-dns 192.168.0.1 xonxoff persist 192.168.1.130:192.168.1.131
From the Amiga I can ping 192.168.1.130 which is the PPP ip address I gave the Pi but nothing else. It seems I can ping the pi but not the internet or even my real non PPP network.
-
Did you enable routing on the Pi?
From the tutorial:
echo 1 > /proc/sys/net/ipv4/ip_forward
Also, what does your routing table look like after the connection on both machines.
On the pi in the shell, it's "route -n"
On the Amiga, it depends on your stack.. Hopefully you can tell what it is..
desiv
-
Yes I did, had to do it differently but when I run
sudo sysctl -p /etc/sysctl.conf
I get
kernel.printk = 3 4 1 3
net.ipv4.ip_forward = 1
vm.swappiness = 1
vm.min_free_kbytes = 8192
-
(The more I think about it, the more I think you need that route on your router I mentioned below)
Yes I did, had to do it differently but when I run
Wonder if it needed a sudo, or something else..
Anyway, try a
pi@raspberrypi ~ $ cat /proc/sys/net/ipv4/ip_forward
0
(Mine says 0, as I haven't enabled routing, yours should say 1, as the output from the sysctl shows..)
If that's fine (as it probably is based on the sysctl), then it's probably down to the routing tables..
Possibly the default route on the Amiga not getting set...
If you can manually set the IP on the Amiga, try setting the IP (192.168.1.131), subnet mask (255.255.255.0), DNS server (whatever your router is) AND default route (192.168.1.130) that way.
Also, if we can see your Pi's routing table if it doesn't work..
I suppose it's possible your router doesn't like the new subnet. If your router doesn't know about it, he might not pick it up.
If you can add a route to the routing table of your router manually, try that.
So, in the router, it would be a route to 192.168.1.0 255.255.255.0 (/24) and the gateway to that route would be your Pi's IP address on the router subnet (wasn't that something like 192.168.0.x?).
Or, you can use IP masq on the Pi instead of routing, but that is trickier..
desiv
-
Currently I am trying to use a Raspberry Pi to connect to the Amiga via a USB to Serial
That is a great idea.
maybe one day I'll get around to trying it over my bluetooth serial device.
I originally was trying to get it to connect to Windows back-end and never could get PPP to negotiate property and gave up after awhile.
http://www.amiga.org/forums/showthread.php?p=674035#post674035
-
Update:
No luck yet.
Currently I am running this command:
sudo pppd nodetach /dev/ttyUSB0 19200 noauth local passive xonxoff persist 192.168.0.130:192.168.0.250
Where:
192.168.0.130 is the IP Address of my Raspberry Pi
192.168.0.250 is the IP Address outside of my DHCP range that I want my Amiga to have
Results:
I can ping both 192.168.0.130 & 192.168.0.250 from the Amiga.
I can telnet to 192.168.0.130 (MyPi)
I cannot ping anything else including my router 192.168.0.1
IP forwarding is on.
On the Pi If I run cat /proc/sys/net/ipv4/route I get:
Destination: 192.168.0.250
Gateway: *
Genmask: 255.255.255.255
Flags UH
Metric 0
Ref 0
Use 0
Iface PPP0
Any help would be appreciated, this is driving me nuts