I have some problems with the MorphOS 2.0 TCP/IP stack.

First, DHCP doesn't seem to work. Doesnt seem able to find the DNS Server, even when configured correctly. Ok, so switched over to static connection. Worked fine...untill now. DNS problems, tries to load/find pages but can't connect. Thing is, MOSNet works fine (DHCP).

Any ideas/suggestions?

I think I manage to solve the problem
using "viarhine-wakeup" (attached)

type in the user-startup
System:C/viarhine-wakeup >NIL:

or copy viarhine-wakeup in WBStartup

Thanks for the suggestion, but I'm pretty sure it's not related to that via_rhine prob.

I'm wondering if my problems might be down to my Sitecom NextHub (or at least in combination with the MorphOS 2.0 TCP/IP stack). More suggestions/tips/hints/solutions anyone?

As was said elsewhere - I was connected through the Marvell Gigabit port of my Pegasos 2 and couldn't get network access until I disabled the 10/100 Via-Rhine connector by removing its check box in the network prefs (the topmost entity in the list). Then everything worked just fine, DHCP and all...

Thanx for the suggestion, but no sigar: I get identical problems.

I'm getting the idea that the stack is at fault here because a) MOSNet does work (DHCP and all) and it seems that my setup is kinda weird. I have a cable modem, and a hub (Sitecom NextHub, 5-port 10Base-T hub) sitting between my laptop/peg2 and the cable modem...and my ISP hands out two different WAN IP's, one for my Peg2 and one for my laptop. Might this be throwing the MorphOS 2.0 TCP/IP stack off? I'll try a direct connection with the cable modem later today to see if DHCP works this way.

ps. Another thing: after trying DHCP with the 2.0 stack, I can't get static to work on 2.0 no matter what I do untill I use MOSNet, almost like it's resetting something hub-wise.

[ Edited by Stevo on 2008/7/5 10:42 ]

The plot thickens: tried connecting directly to my cable modem (no no hub and only one computer connected to modem)...and the problem stays, identical to those experienced before.

*bump*

Running the following command in a shell might help diagnose your problem:

netconfig autoconfig debug >t:netconfig.log

K, added log

edit: here's the printout, since the attached files aren't always visible:

ain: SocketBase 0x23E2E1A8
main: autoconfig
main: reset netconfig library
main: clear interface database
iface_reset:
Delete <lo0>
Delete <lo0>
iface_reset: errno 49
Delete <eth0>
Delete <eth0>
iface_reset: errno 49
main: < NS1=83.80.1.236 HOSTNAME="53518989.cable.casema.nl"
>
main: readargs worked
config_setconfigargs:
config_setconfigargs: Hostname <53518989.cable.casema.nl>
config_setconfigargs: DNS1 <83.80.1.236>
config_interfaces:
config_interfaces: interface <eth0 Device="DEVS:Networks/via_rhinepci.device" Unit=0 DoOnline IP=83.81.164.206 Mask=255.255.254.0 GATEWAY=83.81.164.1>
config_interfaces: name <eth0> type 1
config_interfaces: get flags
config_interfaces: flags 0
config_interfaces: get metric
config_interface: name <eth0>
config_interface: error 0
iface_init: ifname <eth0>
iface_init: IFCT_SANA
iface_init: Opened Sana2 device DEVS:Networks/via_rhinepci.device (unit: 0).
iface_init: sanatype 1
iface_getlinkinfo: iface 0x23E2DBA8
iface_getlinkinfo: SUICGIFCONF
iface_getlinkinfo: ifrp 0x23E497F0 ifend 0x23E49858
iface_getlinkinfo: ifrp 0x23E497F0 iface_name <eth0> ifr_name <lo0>
iface_getlinkinfo: ifrp 0x23E49824 iface_name <eth0> ifr_name <eth0>
iface_getlinkinfo: match
iface_getlinkinfo: htype 6 hlen 6
iface_init: driver is needed online, try to configure & put it online...
iface_configinterface: iface 0x23E2DBA8 conf 0x243CE4F8
iface_configinterface: get station address
iface_configinterface: using configured hwaddr 00:0B:2F:5B:A6:F0
iface_configinterface: S2_CONFIGINTERFACE using hwaddr 00:0B:2F:5B:A6:F0
iface_configinterface: configure interface
iface_configinterface: interface configured ok
iface_configinterface: update iface->iface_haddr to 00:0B:2F:5B:A6:F0
iface_configinterface: return success
Put Sana2 device DEVS:Networks/via_rhinepci.device (unit: 0) online.
Closing Sana2 device DEVS:Networks/via_rhinepci.device (unit: 0).
iface_getflags:
iface_getaddr:
iface_getdstaddr:
iface_getdstaddr: request 0xC0206923
iface_getdstaddr: request failed 49
iface_getdstaddr: <0.0.0.0>
iface_getnetmask:
iface_getnetmask: use <0.0.0.0>
iface_getmtu:
iface_init: ok
iface_findprimary:
config_setconfigargs:
config_setconfigargs: Hostname <53518989.cable.casema.nl>
config_setconfigargs: DNS1 <83.80.1.236>
Current interface configuration is:
interface name: <eth0>
flags: 4863
hardware type: 6
hardware address: <0:b:2f:5b:a6:f0>
IP address: <0.0.0.0>
broadcast IP address: 0.0.0.0
netmask: 0.0.0.0
MTU: 1500
Configuration information after parsing args is:
IP address: 83.81.164.206
broadcast IP address: 0.0.0.0
netmask: 255.255.254.0
gateway: 83.81.164.1
MTU: 0
bootpserver: 0.0.0.0
DNS server #0: 83.80.1.236
Host name: 53518989.cable.casema.nl
Domain name:
Flags: use_bootp=0, use_dhcp=0, use_hwtype=1, do_gateway=1, do_loopback=0, do_dial=1
Configuring interface according to following information:
IP address: 83.81.164.206
broadcast IP address: 0.0.0.0
netmask: 255.255.254.0
gateway: 83.81.164.1
MTU: 0
bootpserver: 0.0.0.0
DNS server #0: 83.80.1.236
Host name: 53518989.cable.casema.nl
Domain name: cable.casema.nl
Flags: use_bootp=0, use_dhcp=0, use_hwtype=1, do_gateway=1, do_loopback=0, do_dial=1
route_add:
NetStack ARexx Command: RESET RESOLV
NetStack ARexx Command: ADD START NAMESERVER 83.80.1.236
config_hostname: Hostname <53518989.cable.casema.nl> Domain <cable.casema.nl>
NetStack ARexx Command: ADD START HOST 83.81.164.206 53518989.cable.casema.nl
config_interface: done
config_interfaces: interface <lo0 Type=loopback DoOnline>
config_interfaces: name <lo0> type 16
config_loopback: interface <lo0>
iface_init: ifname <lo0>
iface_init: LOOPBACK is not in the database
iface_getlinkinfo: iface 0x23E2DBA8
iface_getlinkinfo: SUICGIFCONF
iface_getlinkinfo: ifrp 0x23E497E0 ifend 0x23E49868
iface_getlinkinfo: ifrp 0x23E497E0 iface_name <lo0> ifr_name <lo0>
iface_getlinkinfo: match
iface_getlinkinfo: htype 24 hlen 0
iface_getflags:
iface_getaddr:
iface_getdstaddr:
iface_getdstaddr: no destination available use <0.0.0.0>
iface_getnetmask:
iface_getnetmask: use <0.0.0.0>
iface_getmtu:
iface_init: ok
config_loopback: set address
iface_setaddr: <127.0.0.1>
config_loopback: interface <lo0> configurated
config_interfaces: done
main: free rda 0x23E2DCE4
main: free ncbuffer 0x25285C4C
main: close NetConfigBase
main: exit


[ Edited by Stevo on 2008/7/8 20:45 ]

Heh, it took me some time to realize that posting a log from a (working) static connection wouldn't do much good, so tried it with dhcp enabled...and after some messing around I came to the following findings:

A) "netconfig autoconfig" wont get a dhcp lease and quits
B) "netconfig autoconfig debug" tries again when it wont get a dhcp lease and gets it
C) but only when run for the first time
D) and sometime later than when mossys:s/network-startup gets executed.

In short: DHCP works here when I disable the network-startup script at boot but run it afterwards, and only with the "debug" variable added to "netconfig autoconfig"

Does this make any sense to someone?

Edit:

Well, "Works here"...still a hit and miss affair: sometimes it connects, sometimes it wont.

[ Edited by Stevo on 2008/7/13 1:49 ]