Roadshow 68K and dd-wrt wifi client

[catohagen]

Hi,

This might me a post mostly to Olsen but maybe others have tried..

I've been using wifi routers as wifi clients for years, I have 5-6 of the legendary WRT54GL linksys routers and you re-flash them with dd-wrt and you get a router much more powerful. Then you can use them as clients to your main wifi router and everything you plug into it gets online and connected to your lan. Its been a great companion with lacking wifi connectivity on amiga/morphos over the years.

As a client, the (dd-wrt)router needs a different subnet and uses its own DHCP server and hands out its own ip addresses. dns and gateway,etc are provided by the main wifi router as the (dd-wrt)router requests this with DHCP.

As these old routers are rather big, I bought a few TP-Link TL-WR703N (they are like 6x6cm square) and flashed dd-wrt on them to use as wifi clients, these are usb powered so I can power them from my Macmini or Powerbook.

As my powerbook and mac mini's have been wired directly to my main router (asus rt-ac66u) i've never used them with wifi clients before until today, and have been sitting for 2 hrs with Roadshow and cant get anything to work. Funny thing is the built in Netstack in Morphos
works perfectly, both in static and dhcp, but Roadshow doesnt seem to get anything, either with stactic settings or dhcp.

And I have no idea how to even begin searching for reasons, assuming when morphos builtin stack works, there is nothing wrong with wifi client settings, Roadshow in static ip gives me no errors, but I can't ping anything on lan or net, in dhcp Roadshow sets a non working 169.x.x ip address and complains the default route or gateway is unreachable.

I could ofcourse just stay with Morphos netstack, but since Roadshow 68K gives me so much faster net, I though I'll compare again with Roadshow and the new and improved netstack that came in recent Morphos releases.

Ideas ?

[aggro_mix]

We used Linksys WRT54GL routers with dd-wrt at work for making cheap outdoor wifi-links but they were all on the same subnet. The remote site was used in bridge mode or something. Not that it might help this case.

[olsen]

Hi,

This might me a post mostly to Olsen but maybe others have tried..

I've been using wifi routers as wifi clients for years, I have 5-6 of the legendary WRT54GL linksys routers and you re-flash them with dd-wrt and you get a router much more powerful. Then you can use them as clients to your main wifi router and everything you plug into it gets online and connected to your lan. Its been a great companion with lacking wifi connectivity on amiga/morphos over the years.

As a client, the (dd-wrt)router needs a different subnet and uses its own DHCP server and hands out its own ip addresses. dns and gateway,etc are provided by the main wifi router as the (dd-wrt)router requests this with DHCP.

Sounds familiar... I used to bridge my DSL connection that way: I didn't want to string an Ethernet cable from the ground floor to the top floor of the house, so I bought two Apple AirPort Express units instead. Both units could be configured to provide for a wireless distribution system (WDS), which means that all clients plugged into the switches connected to the respective units could share the same subnet.

That was in 2003, and the whole setup worked out of the box, without having to change the firmware. Because Apple's network gear cannot be configured through a web interface, you did need a Windows box to set them up, though. This sounds like a drawback, but I've seen much worse solutions in the years since (which did have a web interface), the worst being the Linksys gear. I actually tried the WRT54G and sent it back to the dealer the same day. This was the version which came with a different firmware that could not be replaced.

As these old routers are rather big, I bought a few TP-Link TL-WR703N (they are like 6x6cm square) and flashed dd-wrt on them to use as wifi clients, these are usb powered so I can power them from my Macmini or Powerbook.

As my powerbook and mac mini's have been wired directly to my main router (asus rt-ac66u) i've never used them with wifi clients before until today, and have been sitting for 2 hrs with Roadshow and cant get anything to work. Funny thing is the built in Netstack in Morphos
works perfectly, both in static and dhcp, but Roadshow doesnt seem to get anything, either with stactic settings or dhcp.

And I have no idea how to even begin searching for reasons, assuming when morphos builtin stack works, there is nothing wrong with wifi client settings, Roadshow in static ip gives me no errors, but I can't ping anything on lan or net, in dhcp Roadshow sets a non working 169.x.x ip address and complains the default route or gateway is unreachable.

I could ofcourse just stay with Morphos netstack, but since Roadshow 68K gives me so much faster net, I though I'll compare again with Roadshow and the new and improved netstack that came in recent Morphos releases.

Ideas ?

Funny thing, I just heard about the same problem being reported for Roadshow in the support forum. The gist is this: prism2.device is being used, but neither DHCP nor static IP address seems to work so far.

I do not know exactly what configurations the user tried, but he seems to have experimented with "configure=auto" (which will make Roadshow pick an IP address from the 169.254.0.0/16 range -- this is useful for Zeroconf networking only and is not the same as DHCP) and "configure=dhcp", neither of which worked. It appears that the Amiga cannot send or receive any data at all through the wireless interface.

I suspect that the authentication to the WiFI access point may not have worked out, but it's really hard to tell what is going on. Which hardware and driver are you using? How can you tell that the access point accepted your login and password?

Note that you need to perform that authentication before you tell Roadshow to use your wireless network interface. If that interface configuration file is in "DEVS:NetInterfaces", Roadshow will attempt to start it when the system boots, and because the interface has not yet been authenticated to the access point, it will act like an Ethernet card with the network cable removed. If you want to test this, move the interface configuration file to "SYS:Storage/NetInterfaces", reboot your Amiga, perform the access point authentication and then use the AddNetInterface command to start the network.

[catohagen]

@aggro_mix

Yes, the WRT54GL uses broadcom chipset and the client bridge is a feature on that chipset only, the client router is invisible then and the main router sends dchp requests directly to the wired client(s), a fantasic setup if you ask me

@Olsen, yeah, the WRT54G or WRT54GS used either a closed source driver chipset or had too little flash memory to reflash dd-wrt.

the authentication is already done by the client router, the main wifi router is setup with WPA2 security mode and xbox360 and another pc is already connected with no entering passwords. If by hardware/driver you mean with Roadshow, its both a Macmini with Morphos and a Powerbook G4 with Morphos, and both work with builtin Morphos netstack on sungem_eth.device(with dhcp and static ip)

a simple graph would look like:
_______________________________________________________________________________________port1-wired-xbox
---wired--- - - - -wifi 40 meters- - - - port2-wired-win7 box
_______________________________________________________________________________________port3-wired-morphos with Roadshow

so both the xbox and win7 gets their ip address by dhcp or I set static ip's and is connected to internet. Morphos too with builtin netstack

its just Roadshow that refuses to play nice i've tried changing firmware to OpenWRT on the client and same result so it cant be firmware spesific either.

[Matt_H]

In the past, I somewhat successfully used dd-wrt to bridge 2 Linksys routers in the manner you're describing. It was in the pre-Roadshow days, however. I say somewhat because I found that if there was *any* other traffic on the bridged router (i.e., the one not connected to the main modem) the bridge connection would fail and every machine after the first to transmit would be effectively offline. I use static IPs.

I remember setup being incredibly difficult - half a dozen very similar settings that all sound like they would do what I wanted them to, but only one of them did, properly, consistently. And I can't recall the right one. dd-wrt's abysmal documentation didn't help the situation either. Can you maybe post some screencaps of your config?

I've since replaced my wireless infrastructure with last-generation Apple gear, which took about 3 minutes to configure. The boost to wireless N was a nice perk, too. You could probably get similar or older equipment for a decent price now.

[olsen]

@aggro_mix

Yes, the WRT54GL uses broadcom chipset and the client bridge is a feature on that chipset only, the client router is invisible then and the main router sends dchp requests directly to the wired client(s), a fantasic setup if you ask me

It is showing its age by now, I suppose? 802.11g speed may be sufficient for some applications, especially given the robustness of 802.11g, but not for everything.

As for me, the less time I have to spend chasing after network problems, especially if individual components need a bit of extra love for them to work properly, the better ;-)

@Olsen, yeah, the WRT54G or WRT54GS used either a closed source driver chipset or had too little flash memory to reflash dd-wrt.

the authentication is already done by the client router, the main wifi router is setup with WPA2 security mode and xbox360 and another pc is already connected with no entering passwords. If by hardware/driver you mean with Roadshow, its both a Macmini with Morphos and a Powerbook G4 with Morphos, and both work with builtin Morphos netstack on sungem_eth.device(with dhcp and static ip)

OK, that sounds like a standard-ish setup. I was worried that this might be a hairy WiFi issue which requires specific hardware to test, which I do not have.

a simple graph would look like:
_______________________________________________________________________________________port1-wired-xbox
---wired--- - - - -wifi 40 meters- - - - port2-wired-win7 box
_______________________________________________________________________________________port3-wired-morphos with Roadshow

so both the xbox and win7 gets their ip address by dhcp or I set static ip's and is connected to internet. Morphos too with builtin netstack

its just Roadshow that refuses to play nice i've tried changing firmware to OpenWRT on the client and same result so it cant be firmware spesific either.

Well... let's debug the DHCP negotiation as performed by Roadshow. Before we bring out the big guns (tcpdump), one simple first step would be to put "debug=yes" into your interface configuration file (it's proably in there, just commented out), and look at what happens when you start the network with the AddNetInterface command.

For best results, shut down the network with the NetShutdown command first. Also make sure that there is exactly one line in the interface configuration file which begins with "configure=", and it should read "configure=dhcp" before you start the network again.

If everything is set, a debug window should pop up as soon as you enter the AddNetInterface command, showing what Roadshow is currently trying to get out of the DHCP server, if that is possible.

One more thing: do things work out differently if you swap the connectors between ports 1 and 3?

[catohagen]

Here's the logs from Roadshow.

This is with configure=dhcp only, configure=auto and configure=fastauto is disabled

19-May-14 14:43:25 [Debug] Unknown Interface 'powerbook' hardware address = xx:xx:xx:xx:D8:EC.
19-May-14 14:43:27 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:27 [Debug] Unknown Sent initial DHCPDISCOVER request for 'powerbook'; transaction ID=0x476672C9, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
19-May-14 14:43:31 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:31 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:31 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x2592F1D1, retry timeout=0:00:09 hours.
19-May-14 14:43:40 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:40 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:40 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x3B6CC8B2, retry timeout=0:00:16 hours.
19-May-14 14:43:57 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:57 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:57 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x26374C78, retry timeout=0:00:33 hours.


This is with configure=dhcp and configure=auto
Mon May 19 14:45:42 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:45:42 2014 [debug]: Announcing that interface 'powerbook' will use IP address 169.254.103.69...
Mon May 19 14:45:44 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:45:44 2014 [debug]: Setting interface 'powerbook' address to 169.254.103.69.
Mon May 19 14:45:44 2014 [debug]: Setting interface 'powerbook' net mask to 255.255.0.0.
Mon May 19 14:45:44 2014 [debug]: Interface 'powerbook' IP address is now set to 169.254.103.69/255.255.0.0.
Mon May 19 14:45:45 2014 [debug]: Interface 'powerbook' address successfully changed to 169.254.103.69/255.255.0.0.
Mon May 19 14:45:45 2014 [error]: Could not add route from "DEVS:Internet/routes", line 15 (Network is unreachable).


This is with configure=dhcp and configure=fastauto

Mon May 19 14:47:35 2014 [debug]: Interface 'powerbook' hardware address = xx:xx:xx:xx:D8:EC.
Mon May 19 14:47:35 2014 [debug]: Waiting 0.001762 seconds before trying to assign an address to interface 'powerbook'.
Mon May 19 14:47:35 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:35 2014 [debug]: Initial delay for interface 'powerbook' has elapsed.
Mon May 19 14:47:35 2014 [debug]: Sending probe for IP address 169.254.103.69 on interface 'powerbook'...
Mon May 19 14:47:35 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:35 2014 [debug]: Sending another probe for IP address 169.254.103.69 on interface 'powerbook' (attempt #1)...
Mon May 19 14:47:35 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:35 2014 [debug]: Sending another probe for IP address 169.254.103.69 on interface 'powerbook' (attempt #2)...
Mon May 19 14:47:35 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:35 2014 [debug]: Sending another probe for IP address 169.254.103.69 on interface 'powerbook' (attempt #3)...
Mon May 19 14:47:36 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:36 2014 [debug]: Announcing that interface 'powerbook' will use IP address 169.254.103.69...
Mon May 19 14:47:36 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:36 2014 [debug]: Announcing that interface 'powerbook' will use IP address 169.254.103.69...
Mon May 19 14:47:36 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:47:36 2014 [debug]: Setting interface 'powerbook' address to 169.254.103.69.
Mon May 19 14:47:36 2014 [debug]: Setting interface 'powerbook' net mask to 255.255.0.0.
Mon May 19 14:47:36 2014 [debug]: Interface 'powerbook' IP address is now set to 169.254.103.69/255.255.0.0.
Mon May 19 14:47:37 2014 [debug]: Interface 'powerbook' address successfully changed to 169.254.103.69/255.255.0.0.
Mon May 19 14:47:37 2014 [error]: Could not add route from "DEVS:Internet/routes", line 15 (Network is unreachable).

switching ports 1-4 doesnt change Roadshow results

[catohagen]

a screenshot of the router client status page and its dhcp given ip to Morphos netstack

[catohagen]

more logs, this time i tried tcpdump while starting

with configure=dhcp, enable the interface and do tcpdump
MorphOS:C> tcpdump -v
tcpdump: listening on powerbook, link-type EN10MB (Ethernet), capture size 68 bytes
18:18:01.621306 IP (tos 0x0, ttl  64, id 19155, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
18:18:08.648088 IP (tos 0x0, ttl  64, id 19172, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
18:18:23.705681 IP (tos 0x0, ttl  64, id 19173, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]

with configure=auto, enable the interface and do tcpdump
MorphOS:C> tcpdump -v
tcpdump: listening on powerbook, link-type EN10MB (Ethernet), capture size 68 bytes
18:19:37.449038 arp who-has 169.254.103.69 tell 0.0.0.0
18:19:39.477586 arp who-has 169.254.103.69 tell 0.0.0.0
18:19:41.504527 arp who-has 169.254.103.69 tell 0.0.0.0
18:19:43.532082 arp reply 169.254.103.69 is-at 00:11:24:73:d8:ec
18:19:45.542339 arp reply 169.254.103.69 is-at 00:11:24:73:d8:ec
18:19:47.568168 arp who-has 169.254.103.69 (00:11:24:73:d8:ec) tell 169.254.103.69
18:19:48.591125 arp who-has 169.254.103.69 (00:11:24:73:d8:ec) tell 169.254.103.69

with static ip set to 192.168.1.10, enable the interface and do tcpdump and ping 192.168.1.1 (didnt get reply from 192.168.1.1)
MorphOS:C> tcpdump -v
tcpdump: listening on powerbook, link-type EN10MB (Ethernet), capture size 68 bytes
18:22:56.677941 arp who-has 192.168.1.1 tell 192.168.1.10
18:22:57.437703 arp who-has 192.168.1.1 tell 192.168.1.10
18:22:58.719683 arp who-has 192.168.1.1 tell 192.168.1.10
18:22:59.743689 arp who-has 192.168.1.1 tell 192.168.1.10
18:23:00.767401 arp who-has 192.168.1.1 tell 192.168.1.10

with Roadshow set as static 192.168.1.10, I can only ping its own address and get a reply

in all attempts with dhcp and static, devs:internet/name-resolution and routes is set to 192.168.1.1 (nameserver 192.168.1.1 and DEFAULT 192.168.1.1)

[catohagen]

just for reference, i've enabled debug output on Morphos netstack and configured to DHCP. Same dd-wrt router(client) with ip 192.168.1.1

main: SocketBase 0x23BC7FB4
main: autoconfig
main: reset netconfig library
main: clear interface database
iface_reset:
Delete
iface_reset: errno 49
main: < HOSTNAME=POWERBOOK
>
main: readargs worked
config_setconfigargs:
config_setconfigargs: Hostname
config_interfaces:
config_interfaces: interface
config_interfaces: name type 1
config_interfaces: get flags
config_interfaces: flags 0
config_interfaces: get metric
config_interface: name
config_interface: error 0
iface_init: ifname
iface_init: IFCT_SANA
iface_init: sanatype 1
iface_init: Opened Sana2 device DEVS:Networks/sungem_eth.device (unit: 0).
iface_getlinkinfo: iface 0x23BBF308
iface_getlinkinfo: SUICGIFCONF
iface_getlinkinfo: ifrp 0x20B4D7F0 ifend 0x20B4D858
iface_getlinkinfo: ifrp 0x20B4D7F0 iface_name ifr_name
iface_getlinkinfo: ifrp 0x20B4D824 iface_name ifr_name
iface_getlinkinfo: match
iface_getlinkinfo: htype 6 hlen 6
iface_init: driver is needed online, try to configure & put it online...
iface_configinterface: iface 0x23BBF308 conf 0x23BB3EA8
iface_configinterface: get station address
iface_configinterface: using configured hwaddr xx:xx:xx:xx:D8:EC
iface_configinterface: S2_CONFIGINTERFACE using hwaddr xx:xx:xx:xx:D8:EC
iface_configinterface: configure interface
iface_configinterface: interface configured ok
iface_configinterface: update iface->iface_haddr to xx:xx:xx:xx:D8:EC
iface_configinterface: return success
Put Sana2 device DEVS:Networks/sungem_eth.device (unit: 0) online.
Closing Sana2 device DEVS:Networks/sungem_eth.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
Current interface configuration is:
          interface name:
                   flags: 4822
           hardware type: 6
        hardware address: <0:xx:xx:xx:d8:ec>
              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: 0.0.0.0
broadcast IP address: 0.0.0.0
netmask: 0.0.0.0
gateway: 0.0.0.0
MTU: 0
bootpserver: 0.0.0.0
Host name: POWERBOOK
Domain name:
Flags: use_bootp=0, use_dhcp=1, use_hwtype=1, do_gateway=1, do_loopback=0, do_dial=1
config_dhcp: use dhcp
iface_prepare_bootp: Setting iface address to 0.0.0.0.
iface_setaddr: <0.0.0.0>
iface_getdstaddr:
iface_getdstaddr: request 0xC0206923
iface_getdstaddr: <0.255.255.255>
iface_getnetmask:
iface_getnetmask: <255.0.0.0>
iface_prepare_bootp: Get dstaddr address <0.255.255.255>.
iface_prepare_bootp: Get netmask <255.0.0.0>.
Set socket to allow broadcasts.
Set socket to bypass routing.
iface_prepare_bootp: iface_flags 0x4822
iface_prepare_bootp: Broadcast
iface_prepare_bootp: Set netmask as IP is 0.0.0.0 or netmask was specified
iface_setnetmask: <0.0.0.0>
iface_prepare_bootp: use dstaddr <255.255.255.255>
iface_setdstaddr: <255.255.255.255>
iface_setdstaddr: Broadcast interface, request SIOCSIFBRDADDR
iface_setdstaddr: request 0x80206913
config_dhcp: IP 192.168.1.10
config_dhcp: Mask 255.255.255.0
config_dhcp: Gateway 192.168.1.1
config_dhcp: ignore DHCP Hostname, was already predefined
config_dhcp: domainname <>
config_dhcp: Lease 86400
config_dhcp: Lease T1 43200
config_dhcp: Lease T2 75600
config_dhcp: dns <192.168.1.1>
config_dhcp: free DNS entry 0
config_dhcp: dns <0.0.0.0>
config_dhcp: INADDR_ANY, skip
config_dhcp: cleanup dhcp
iface_cleanup_dhcp: iface 0x23BBF308 conf 0x23BB3EA8
iface_cleanup_bootp:
iface_cleanup_bootp: no p2p interface
iface_cleanup_dhcp: done
Configuration information after DHCP is:
IP address: 192.168.1.10
broadcast IP address: 0.0.0.0
netmask: 255.255.255.0
gateway: 192.168.1.1
MTU: 0
bootpserver: 0.0.0.0
DNS server #0: 192.168.1.1
Host name: POWERBOOK
Domain name:
Flags: use_bootp=0, use_dhcp=1, use_hwtype=1, do_gateway=1, do_loopback=0, do_dial=1
config_dhcp: done
Configuring interface according to following information:
IP address: 192.168.1.10
broadcast IP address: 0.0.0.0
netmask: 255.255.255.0
gateway: 192.168.1.1
MTU: 0
bootpserver: 0.0.0.0
DNS server #0: 192.168.1.1
Host name: POWERBOOK
Domain name:
Flags: use_bootp=0, use_dhcp=1, 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 192.168.1.1
config_hostname: Hostname Domain <>
config_hostname: Host name does not include domain! Domain NOT set!
NetStack ARexx Command: ADD START HOST 192.168.1.10 POWERBOOK
config_interface: done
config_interfaces: interface
config_interfaces: name type 16
config_loopback: interface
iface_init: ifname
iface_init: LOOPBACK is not in the database
iface_getlinkinfo: iface 0x23BBF308
iface_getlinkinfo: SUICGIFCONF
iface_getlinkinfo: ifrp 0x20B4D7E0 ifend 0x20B4D868
iface_getlinkinfo: ifrp 0x20B4D7E0 iface_name ifr_name
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 configurated
config_interfaces: done
main: free rda 0x243CD924
main: free ncbuffer 0x23BC77AC
main: close NetConfigBase
main: exit

[catohagen]

More fiddling..

I restored the router(TP Link 703n) to defaults, it became a wifi router with a default accesspoint that phones and clients can connect to, so it have no internet but you can access the http config pages. Roadshow still gets no DHCP ip address but Morphos netstack gets 192.168.1.110 from the default DHCP settings and I can surf the router settings page on 192.168.1.1

Found another small router, ASUS WL-330N3G with OpenWRT, Roadshow gets no ip and Morphos netstack gets ip and surfs both http config page in router and internet when the router gets configured as wifi client.

So I wonder if my Roadshow settings or files are totally %&$#?@!%&$#?@!%&$#?@!%&$#?@!ed up, unplugs everything from the G4 Powerbook, shutdown the machine and bring with me a network cable and walk over to my main wifi router (ASUS RT-N66u with TomatoUSB) and powerup the powerbook with Roadshow enabled with DHCP :

19-May-14 19:54:36 [Debug] Unknown Interface 'powerbook' hardware address = xx:xx:xx:xx:D8:EC.
19-May-14 19:54:40 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 19:54:40 [Debug] Unknown Sent initial DHCPDISCOVER request for 'powerbook'; transaction ID=0x32049F6E, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
19-May-14 19:54:42 [Debug] Unknown Received BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Picking up BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:42 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 19:54:42 [Debug] Unknown Setting up DHCP packet for 'powerbook' with transaction ID = 0x32049F6E, server address = 192.168.0.1, client address = 192.168.0.75.
19-May-14 19:54:42 [Debug] Unknown Responding to DHCP offer; sent DHCPREQUEST request for 'powerbook'; transaction ID=0x32049F6E, retry timeout=0:00:03 hours.
19-May-14 19:54:42 [Debug] Unknown Received BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Picking up BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Server has responded to address allocation request for 'powerbook'. Suggested IP address is 192.168.0.75.
19-May-14 19:54:42 [Debug] Unknown Checking if the IP address 192.168.0.75 proposed for 'powerbook' is already in use.
19-May-14 19:54:42 [Debug] Unknown Configuration information for 'powerbook': Server hardware address = xx:xx:xx:xx:DF:C0.
19-May-14 19:54:44 [Debug] Unknown IP address verification timeout for 'powerbook' has elapsed.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address lease time = 1 day(s), 0:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address renewal time = 0 day(s), 12:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address rebind time = 0 day(s), 21:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Subnet mask = 255.255.255.0.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Domain name system server = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Router = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Binding address of 'powerbook'.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server IP address = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Setting interface 'powerbook' address to 192.168.0.75.
19-May-14 19:54:44 [Debug] Unknown Setting interface 'powerbook' net mask to 255.255.255.0.
19-May-14 19:54:44 [Debug] Unknown Interface 'powerbook' IP address is now set to 192.168.0.75/255.255.255.0.
19-May-14 19:54:45 [Debug] Unknown Interface 'powerbook' address successfully changed to 192.168.0.75/255.255.255.0.

*scratches head*

c:netshutdown and runs a tcpdump after bringing interface up again :

20:00:42.843466 IP (tos 0x0, ttl  64, id 14624, offset 0, flags [none], length: 328) 192.168.0.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300, xid:0x45399efb, flags: [Broadcast]
          Your IP: 192.168.0.75
          Server IP: 192.168.0.1 [|bootp]
20:00:42.845691 IP (tos 0x0, ttl  64, id 25345, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
20:00:42.853536 IP (tos 0x0, ttl  64, id 34608, offset 0, flags [none], length: 328) 192.168.0.1.bootps > 192.168.0.75.bootpc: BOOTP/DHCP, Reply, length: 300, xid:0x45399efb, flags: [none]
          Your IP: 192.168.0.75
          Server IP: 192.168.0.1 [|bootp]
20:00:42.854626 arp who-has 192.168.0.75 tell 0.0.0.0
20:00:42.948448 arp who-has 192.168.0.1 tell 192.168.0.77
20:00:43.229127 arp who-has 192.168.0.112 tell 192.168.0.15
20:00:43.554230 arp who-has 192.168.0.66 tell 192.168.0.15
20:00:43.982747 arp who-has 192.168.0.3 tell 192.168.0.15
20:00:44.230203 arp who-has 192.168.0.66 tell 192.168.0.15

If firmware matters, TomatoUSB is also 'homebrew' firmware and shares much with DD-Wrt firmware and OpenWRT firmware, sometimes you can flash
Tomato firmware directly over DD-Wrt firmware on the same router and stuff stays configured as before and workds as they usally use same nvram variables as they are based on the same sources from the opensource community.

Still it would be great to find some solution to this..

[olsen]

Here's the logs from Roadshow.

This is with configure=dhcp only, configure=auto and configure=fastauto is disabled

19-May-14 14:43:25 [Debug] Unknown Interface 'powerbook' hardware address = xx:xx:xx:xx:D8:EC.
19-May-14 14:43:27 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:27 [Debug] Unknown Sent initial DHCPDISCOVER request for 'powerbook'; transaction ID=0x476672C9, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
19-May-14 14:43:31 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:31 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:31 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x2592F1D1, retry timeout=0:00:09 hours.
19-May-14 14:43:40 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:40 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:40 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x3B6CC8B2, retry timeout=0:00:16 hours.
19-May-14 14:43:57 [Debug] Unknown DHCP retry timeout for 'powerbook' has elapsed.
19-May-14 14:43:57 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 14:43:57 [Debug] Unknown Resent DHCPDISCOVER request for 'powerbook'; transaction ID=0x26374C78, retry timeout=0:00:33 hours.

The DHCP server is not responding, does not receive the packets sent by Roadshow, or does not succeed in sending the responses to Roadshow.

This is with configure=dhcp and configure=auto
Mon May 19 14:45:42 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:45:42 2014 [debug]: Announcing that interface 'powerbook' will use IP address 169.254.103.69...
Mon May 19 14:45:44 2014 [debug]: Automatic allocation probe timeout for 'powerbook' has elapsed.
Mon May 19 14:45:44 2014 [debug]: Setting interface 'powerbook' address to 169.254.103.69.
Mon May 19 14:45:44 2014 [debug]: Setting interface 'powerbook' net mask to 255.255.0.0.
Mon May 19 14:45:44 2014 [debug]: Interface 'powerbook' IP address is now set to 169.254.103.69/255.255.0.0.
Mon May 19 14:45:45 2014 [debug]: Interface 'powerbook' address successfully changed to 169.254.103.69/255.255.0.0.
Mon May 19 14:45:45 2014 [error]: Could not add route from "DEVS:Internet/routes", line 15 (Network is unreachable).

Um, configure=auto is not useful in this context and should be used only if you can live with the fact that neither DNS nor Internet routing will work ;-)

This is with configure=dhcp and configure=fastauto
...

Wait -- the configure line instructs Roadshow to pick a specific interface and network configuration method. You cannot combine these.

switching ports 1-4 doesnt change Roadshow results

That at least suggests it might not be a simple layer 1 problem ;-)

[olsen]

more logs, this time i tried tcpdump while starting

with configure=dhcp, enable the interface and do tcpdump
MorphOS:C> tcpdump -v
tcpdump: listening on powerbook, link-type EN10MB (Ethernet), capture size 68 bytes
18:18:01.621306 IP (tos 0x0, ttl  64, id 19155, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
18:18:08.648088 IP (tos 0x0, ttl  64, id 19172, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
18:18:23.705681 IP (tos 0x0, ttl  64, id 19173, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]

I had hoped that tcpdump would show the DHCP server's response in more detail, but there is nothing to be seen here :-(

Incidentally, if there were a response, you'd have to tell tcpdump to read more packet data and decode it, e.g. "tcpdump -s1500 -vvv".

with Roadshow set as static 192.168.1.10, I can only ping its own address and get a reply

in all attempts with dhcp and static, devs:internet/name-resolution and routes is set to 192.168.1.1 (nameserver 192.168.1.1 and DEFAULT 192.168.1.1)

If you want to use DHCP, you should not have anything configured as the name server and the route. The contents of these files take precedence over what the DHCP server suggests, and if that doesn't match the DHCP server's idea, you'll have a problem :-(

[olsen]

More fiddling..

I restored the router(TP Link 703n) to defaults, it became a wifi router with a default accesspoint that phones and clients can connect to, so it have no internet but you can access the http config pages. Roadshow still gets no DHCP ip address but Morphos netstack gets 192.168.1.110 from the default DHCP settings and I can surf the router settings page on 192.168.1.1

Found another small router, ASUS WL-330N3G with OpenWRT, Roadshow gets no ip and Morphos netstack gets ip and surfs both http config page in router and internet when the router gets configured as wifi client.

So I wonder if my Roadshow settings or files are totally %&$#?@!%&$#?@!%&$#?@!%&$#?@!ed up, unplugs everything from the G4 Powerbook, shutdown the machine and bring with me a network cable and walk over to my main wifi router (ASUS RT-N66u with TomatoUSB) and powerup the powerbook with Roadshow enabled with DHCP :

19-May-14 19:54:36 [Debug] Unknown Interface 'powerbook' hardware address = xx:xx:xx:xx:D8:EC.
19-May-14 19:54:40 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 19:54:40 [Debug] Unknown Sent initial DHCPDISCOVER request for 'powerbook'; transaction ID=0x32049F6E, retry timeout=0:00:04 hours, allocation timeout=0:01:00 hours.
19-May-14 19:54:42 [Debug] Unknown Received BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Picking up BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:42 [Debug] Unknown Setting up BOOTP packet for 'powerbook' with hardware address xx:xx:xx:xx:D8:EC.
19-May-14 19:54:42 [Debug] Unknown Setting up DHCP packet for 'powerbook' with transaction ID = 0x32049F6E, server address = 192.168.0.1, client address = 192.168.0.75.
19-May-14 19:54:42 [Debug] Unknown Responding to DHCP offer; sent DHCPREQUEST request for 'powerbook'; transaction ID=0x32049F6E, retry timeout=0:00:03 hours.
19-May-14 19:54:42 [Debug] Unknown Received BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Picking up BOOTP/DHCP server message for 'powerbook'.
19-May-14 19:54:42 [Debug] Unknown Server has responded to address allocation request for 'powerbook'. Suggested IP address is 192.168.0.75.
19-May-14 19:54:42 [Debug] Unknown Checking if the IP address 192.168.0.75 proposed for 'powerbook' is already in use.
19-May-14 19:54:42 [Debug] Unknown Configuration information for 'powerbook': Server hardware address = xx:xx:xx:xx:DF:C0.
19-May-14 19:54:44 [Debug] Unknown IP address verification timeout for 'powerbook' has elapsed.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address lease time = 1 day(s), 0:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address renewal time = 0 day(s), 12:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Address rebind time = 0 day(s), 21:00:00 hour(s).
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Subnet mask = 255.255.255.0.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Domain name system server = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Router = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Binding address of 'powerbook'.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server identifier = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Configuration information for 'powerbook': Server IP address = 192.168.0.1.
19-May-14 19:54:44 [Debug] Unknown Setting interface 'powerbook' address to 192.168.0.75.
19-May-14 19:54:44 [Debug] Unknown Setting interface 'powerbook' net mask to 255.255.255.0.
19-May-14 19:54:44 [Debug] Unknown Interface 'powerbook' IP address is now set to 192.168.0.75/255.255.255.0.
19-May-14 19:54:45 [Debug] Unknown Interface 'powerbook' address successfully changed to 192.168.0.75/255.255.255.0.

*scratches head*

c:netshutdown and runs a tcpdump after bringing interface up again :

20:00:42.843466 IP (tos 0x0, ttl  64, id 14624, offset 0, flags [none], length: 328) 192.168.0.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length: 300, xid:0x45399efb, flags: [Broadcast]
          Your IP: 192.168.0.75
          Server IP: 192.168.0.1 [|bootp]
20:00:42.845691 IP (tos 0x0, ttl  64, id 25345, offset 0, flags [DF], length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request [|bootp]
20:00:42.853536 IP (tos 0x0, ttl  64, id 34608, offset 0, flags [none], length: 328) 192.168.0.1.bootps > 192.168.0.75.bootpc: BOOTP/DHCP, Reply, length: 300, xid:0x45399efb, flags: [none]
          Your IP: 192.168.0.75
          Server IP: 192.168.0.1 [|bootp]
20:00:42.854626 arp who-has 192.168.0.75 tell 0.0.0.0
20:00:42.948448 arp who-has 192.168.0.1 tell 192.168.0.77
20:00:43.229127 arp who-has 192.168.0.112 tell 192.168.0.15
20:00:43.554230 arp who-has 192.168.0.66 tell 192.168.0.15
20:00:43.982747 arp who-has 192.168.0.3 tell 192.168.0.15
20:00:44.230203 arp who-has 192.168.0.66 tell 192.168.0.15

If firmware matters, TomatoUSB is also 'homebrew' firmware and shares much with DD-Wrt firmware and OpenWRT firmware, sometimes you can flash
Tomato firmware directly over DD-Wrt firmware on the same router and stuff stays configured as before and workds as they usally use same nvram variables as they are based on the same sources from the opensource community.

Still it would be great to find some solution to this..

Just checking: when reset your router wants to use subnet 192.168.0.0/24 and the DHCP server will assign addresses from that subnet. When in normal operations mode, however, your DHCP server is supposed to assign addresses from the 192.168.1.0/24 subnet?

The DHCP client code in Roadshow uses broadcast mode when sending packets to the DHCP server, and the server's responses will be sent in broadcast mode, too. Which means that regardless of which subnet you are using (192.168.0.0/24 or 192.168.1.0/24) , the packets should be delivered to the server, and find their way from the server to Roadshow.

The funny thing is that there is no response at all. Not even tcpdump shows broadcast packets coming back to Roadshow. I'd say something is either blocking packet delivery or is discarding them.

[catohagen]

Just checking: when reset your router wants to use subnet 192.168.0.0/24 and the DHCP server will assign addresses from that subnet. When in normal operations mode, however, your DHCP server is supposed to assign addresses from the 192.168.1.0/24 subnet?

The main router uses subnet 192.168.0.0/24, thats why wifi clients uses 192.168.1.0/24 as its required to use different subnets, but I also tried setting wifi client to 192.168.0.1 but same behaviour occur.

It does looks like something is blocking traffic, but since xbox360, a win7 box and Morphos netstack seems to communicate unblocked, what does these send to a router that Roadshow doesnt ?
And the different approach of setting a static ip seems to keep Roadshow in the dark aswell as pinging anything on the known network doesnt work, only Roadshow's ip.

As for the aging setup aspect, its not limited to G speeds, you can setup two AC routers and brigded toghether they exchange data at ~600 Mbit/s in good conditions, with a gigabit port as in this Powerbook with Morphos, a remote desktop connection to a pc is bearly noticable being networked, you can watch videos or youtube with that