Anonymous




Register
Login

Amiga Future

Community

Knowledge

Service

Search




Advanced search

Unanswered topics
Active topics

Last Magazine

The Amiga Future 148 was released on the January 11th.

The Amiga Future 148 was released on the January 11th.
The Amiga Future 148 was released on the January 11th.

The Amiga Future 148 was released on the January 11th.
More informations

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube

Advertisement

Amazon

Partnerlinks

Search found 15 matches

by duga
29.10.2020 - 23:18
Forum: Roadshow Support
Topic: Clockport Wi-Fi adapter: useful?
Replies: 1
Views: 1812

Re: Clockport Wi-Fi adapter: useful?

Speed is not important, but it must support WPA2/AES in 2020.

WPA/TKIP is considered legacy by now and should be disabled or at least not used anymore.
by duga
29.10.2020 - 23:16
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 11
Views: 1393

Re: Roadshow MTU and MRU

Perhaps of interest for someone: From the SDK (version 1.5): /* * Default maximum segment size for TCP. * With an IP MSS of 576, this is 536, * but 512 is probably more convenient. * This should be defined as MIN(512, IP_MSS - sizeof (struct tcpiphdr)). */ #define TCP_MSS 512 /* * Internet implement...
by duga
19.09.2020 - 10:08
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 11
Views: 1393

Re: Roadshow MTU and MRU

Can this be related to the 576 minimum datagram size? "The Internet Protocol requires that hosts must be able to process IP datagrams of at least 576 bytes (for IPv4)". The MTU is allowed to be as small as 68 bytes though. https://en.wikipedia.org/wiki/Maximum_transmission_unit You may be...
by duga
02.10.2016 - 23:17
Forum: Roadshow Support
Topic: Support for DHCP offer via unicast instead of broadcast?
Replies: 7
Views: 8634

Re: Support for DHCP offer via unicast instead of broadcast?

Sounds great! A question though, just to make things clear: This extra option for the interface configuration file isn't enough. Roadshow actually has to understand the unicast datagrams too, right? Before it actually has gotten an IP assigned. Quick update: I just tested the DHCP unicast option wi...
by duga
03.01.2016 - 14:22
Forum: Roadshow Support
Topic: Support for DHCP offer via unicast instead of broadcast?
Replies: 7
Views: 8634

Great, looking forward to try.
by duga
19.12.2015 - 21:59
Forum: Roadshow Support
Topic: Support for DHCP offer via unicast instead of broadcast?
Replies: 7
Views: 8634

Re: Support for DHCP offer via unicast instead of broadcast?

Roadshow (68k and OS 4.1 FE) "only" supports DHCP offers via broadcast, not via unicast. Any plans on changing that? Some info here: https://learningnetwork.cisco.com/thread/32255 "At Layer 2, the client's messages are always broadcast, and those of the server's can be unicast or bro...
by duga
05.12.2015 - 21:57
Forum: Roadshow Support
Topic: Support for DHCP offer via unicast instead of broadcast?
Replies: 7
Views: 8634

Support for DHCP offer via unicast instead of broadcast?

Roadshow (68k and OS 4.1 FE) "only" supports DHCP offers via broadcast, not via unicast. Any plans on changing that? Some info here: https://learningnetwork.cisco.com/thread/32255 "At Layer 2, the client's messages are always broadcast, and those of the server's can be unicast or broa...
by duga
14.07.2013 - 17:58
Forum: Roadshow Support
Topic: Is 3c589.device supported?
Replies: 13
Views: 14240

These ClassAct programs works with two different 3COM cards:
AmiFTP
AWeb-II 3.2 demo

DHCP still doesn't work (Software Failure 80000003).


MUI programs doesn't work, maybe some 020 version somewhere is the reason.
by duga
26.06.2013 - 22:56
Forum: Roadshow Support
Topic: Is 3c589.device supported?
Replies: 13
Views: 14240

Update: Made a clean WB 3.1-install instead of Classic WB. The good news: Now ClassAct works, no ramlib crash anymore. The bad news: still "bus error" when trying NCFTP. Guess I have to try another NIC with 3c589.device or cnet.device The Classic WB problem is confirmed to be caused by a ...
by duga
18.05.2013 - 14:25
Forum: Roadshow Support
Topic: Is 3c589.device supported?
Replies: 13
Views: 14240

Update:

Made a clean WB 3.1-install instead of Classic WB.

The good news: Now ClassAct works, no ramlib crash anymore.

The bad news: still "bus error" when trying NCFTP.


Guess I have to try another NIC with 3c589.device or cnet.device