Amiga Unix Wiki

Because AmigaOS just isn't obscure enough today!

User Tools

Site Tools


networking

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
networking [2018/08/30 22:24]
127.0.0.1 external edit
networking [2018/12/29 19:58] (current)
wiki_admin
Line 15: Line 15:
 Out of the box, Amiga UNIX doesn'​t do DNS lookups but looks at local files (/​etc/​hosts) only. To enable DNS access: Out of the box, Amiga UNIX doesn'​t do DNS lookups but looks at local files (/​etc/​hosts) only. To enable DNS access:
  
 +<​code>​
 ln -f /​usr/​lib/​libsockdns.so /​usr/​lib/​libsocket.so ln -f /​usr/​lib/​libsockdns.so /​usr/​lib/​libsocket.so
  
Line 20: Line 21:
  
 ln -f /​etc/​netconfig.DNS /​etc/​netconfig ln -f /​etc/​netconfig.DNS /​etc/​netconfig
 +</​code>​
  
 If you put your nameserver into /​etc/​resolv.conf this will get DNS working for at least some applications,​ like ping. Others such as nslookup appear to expect a nameserver to be running on the local system. To easily configure your system, download the attachments to this page, below. Place named.boot in /etc, and everything else into /var/named. Edit /​etc/​named.boot and replace the IP address on this line with the DNS server you use for your net connection: If you put your nameserver into /​etc/​resolv.conf this will get DNS working for at least some applications,​ like ping. Others such as nslookup appear to expect a nameserver to be running on the local system. To easily configure your system, download the attachments to this page, below. Place named.boot in /etc, and everything else into /var/named. Edit /​etc/​named.boot and replace the IP address on this line with the DNS server you use for your net connection:
Line 31: Line 33:
 You can verify this is working by using nslookup to find google.com'​s IP: You can verify this is working by using nslookup to find google.com'​s IP:
  
 +<​code>​
 nslookup www.google.com nslookup www.google.com
 Server: ​ localhost Server: ​ localhost
Line 39: Line 42:
 Address: ​ 74.125.67.147 Address: ​ 74.125.67.147
 Aliases: ​ www.google.com Aliases: ​ www.google.com
 +</​code>​
  
 You've now got DNS working as well as I can get it to work, currently. You've now got DNS working as well as I can get it to work, currently.
Line 46: Line 50:
 The route is set in the file /​etc/​inet/​rc.inet. Assuming your gateway is 192.168.1.1,​ you need to add the following to this file: The route is set in the file /​etc/​inet/​rc.inet. Assuming your gateway is 192.168.1.1,​ you need to add the following to this file:
  
 +<​code>​
 /​usr/​sbin/​route add default 192.168.1.1 1 /​usr/​sbin/​route add default 192.168.1.1 1
 +</​code>​
  
 Don't forget the extra "​1"​ at the end, that's the metric and it's required. Don't forget the extra "​1"​ at the end, that's the metric and it's required.
Line 65: Line 71:
  
 Notes: some NAS/network gear let you adjust the MTU (maximum transmission unit) to enhance transfer speeds. At least one user reported that raising this value (from the default value of 1500) caused problems with Amix: a mount was possible but any access to files on the NFS share caused "NFS not responding, still trying"​ errors. Putting back the default value restored operation. Notes: some NAS/network gear let you adjust the MTU (maximum transmission unit) to enhance transfer speeds. At least one user reported that raising this value (from the default value of 1500) caused problems with Amix: a mount was possible but any access to files on the NFS share caused "NFS not responding, still trying"​ errors. Putting back the default value restored operation.
 +
 +For those interested, there is also a short tutorial on [[http://​amigadev.elowar.com/​read/​ADCD_2.1/​AmigaMail_Vol2_guide/​node0100.html|using Amix as a NFS file server]]
  
 ===== Remote connections ===== ===== Remote connections =====
networking.1535660649.txt.gz ยท Last modified: 2018/08/30 22:24 by 127.0.0.1