x-surf100 and AMITCP

[rogersyd]

Hi Amiga Brains...

I am running a x-surf-100 and amitcp3 in my A4KD. I can ping my router, the NIC, and other devices on my network just fine. If i ping external sites i get no response.

When i ping an external domain, the IP address is displayed, so i think that DNS/NAMESERVER settings are fine.

For example pinging google.com displays:

ping google.com (74.125.226.193): 56 data bytes

So it looks like DNS is working ok. Pinging either an external address or an external domain yields 100% packet loss. I have been over the config files a hundred times and everything looks right based on all the info I have found in this forum and others.

I have tried both the standard and enhanced version of the x-surf-100.device files. same result. What stupid simple thing am i missing here? (no issues with other pcs on the same router).

If any other info would be helpful please let me know. I figured i have banged my head against the wall long enough. Someone else must have had this issue before... thanks for the help!

[thomas]

Can you ping your A4K from other devices on the network?

Can you ping google from other devices on the network?

Could it be that the IP you gave to your A4K is duplicate on the network?

[rogersyd]

thanks for the reply...

Can you ping your A4K from other devices on the network? YES

Can you ping google from other devices on the network? YES

Could it be that the IP you gave to your A4K is duplicate on the network?
NO - i reserved the amigas IP in my router via the MAC address to avoid any chance of that. In the connected devices page of my router, i see the Amiga assigned the IP address correctly.

THANKS!

[rogersyd]

Thought i would add my config files...

startnet

setenv HOSTNAME amiga
run >NIL: AmiTCP:AmiTCP
WaitForPort AMITCP
AmiTCP:bin/ifconfig lo0 localhost
AmiTCP:bin/ifconfig eth0 192.200.2.29 netmask 255.255.255.0 
AmiTCP:bin/route >NIL: -v add amiga localhost
AmiTCP:bin/route >NIL: -v add default 192.200.2.1
Assign TCP: Exists >NIL:
IF Warn
  Mount TCP: from AmiTCP:devs/Inet-Mountlist
EndIf
run >NIL: AmiTCP:bin/inetd

netdb-myhost

HOST 192.200.2.29 amiga
NAMESERVER 192.200.2.1

interfaces

# 
# Here is a few examples:
#
# Serial Line IP
#
slip dev=devs:networks/rhslip.device 
# IPTYPE=2048 NOARP P2P IPREQ=8 WRITEREQ=8
#
# SLIP with V. Jacobson header compression 
#
cslip dev=devs:networks/rhcslip.device 
# IPTYPE=2048 NOARP P2P IPREQ=8 WRITEREQ=8
#
# Ethernet adapter A2065
#
eth  dev=devs:networks/x-surf-100.device
# IPTYPE=2048 ARPTYPE=2054 ARPHDR=1 ARPREQ=4 IPREQ=16 WRITEREQ=16 
# 
# Arcnet adapter a2060 
#
arcnet dev=devs:networks/a2060.device NOTRACKING
# IPTYPE=240 ARPTYPE=241 ARPHDR=7 ARPREQ=4 IPREQ=16 WRITEREQ=16 
#
# An X.25 driver by Dave Martin
#
axdm dev=devs:networks/ax25.device +
  IPTYPE=204 ARPTYPE=205 ARPHDR=3 ARPREQ=3 IPREQ=16 WRITEREQ=16

hosts (env and envarc)

amiga

amitcp.config

#
# AmiTCP/IP configuration file. See documentation for usage.
#
useloopback=YES
debugsana=NO
usens=SECOND
gateway=yes

hopefully something idiotic and obvious will jump out at the group.

[thomas]

Nothing wrong at first sight.

Just an irrelevant question: I wonder why you use route -v where -v means verbose output but then throw the output to NIL. Isn't it a waste of bits to produce extra large output and then throw it away? Furthermore you will never see error messages if you send the output to NIL.



Does ping work if you use Miami or Roadshow?

[rogersyd]

Thanks Thomas. Good catch on that - chalk that error up to my (cough) superb amiga scripting skills!

I was hoping to avoid Miami as i have read that it is much slower than AmiTCP but no harm in trying it out. Will give that a go tonight and report back tomorrow. There is also a network boot disk floating around here somewhere that I saw. Will see if I can find that too and give it a shot.

[prowler]

Originally Posted by rogersyd

There is also a network boot disk floating around here somewhere that I saw. Will see if I can find that too and give it a shot.

http://jpv.wmhost.com/NetworkBootDisk/

[rogersyd]

Thanks Prowler!
I gave the NBD a cursory try, less success out the gate there. Even internal pings were reporting 100% packet loss. I haven't spent much time troubleshooting that just yet. If we assume the "Beta 20080826" version name is referring to the built date, I will at least need to update the xsurf drivers since the x-surf-100 is the new model... who knows....

And Thomas,
I have installed roadshow and disabled amitcp. Roadshow worked pretty much out of the box. Just copied over the right driver, rebooted the miggy and I was surfing in no time. At 15 mins a clip the demo version of roadshow isn't going to cut the mustard, but it is super awesome just seeing this card work correctly. This also leads me to believe that something is screwy with my AMITCP config. Armed with this new knowledge my quest to get amiTCP working continues.

Something very satisfying about seeing web pages (sortof) rendering on an amiga.

Thanks again to both for the help and advice!

[prowler]

Originally Posted by rogersyd

I haven't spent much time troubleshooting that just yet. If we assume the "Beta 20080826" version name is referring to the built date, I will at least need to update the xsurf drivers since the x-surf-100 is the new model... who knows....

Yep, the old version was "Beta 20071128"

[rogersyd]

No dice on this one yet. The card vendor has all of my information and will hopefully find a solution to my AMITCP issue. Otherwise looks like I'll need to shell out some coin for the full version of Roadshow. If i find a solution to the AMITCP issue I will post it here for other sad souls in the same predicament.

[rogersyd]

Working now 100% thanks to EasyNet... Next up on the agenda is standing up a telnet bbs...