PCUAE Network Mode - Internet Now Available in PCUAE1.9.0b1
Feb 17, 2022 12:25:56 GMT
jj0 and masticman like this
Post by spannernick on Feb 17, 2022 12:25:56 GMT
I have added it now to the Wiki under Point Number 14, ready for its releasee ... projectcarouselusb.online/help-2
It now in PCUAE1.9.0b1 and is released to the wild....

Here is a PCUAENM USB Network Adapters compatibility List, you can add the USB Ethernet/WIFI Adapters/Dongles you have tested with PCUAE Network Mode, if they work or not work so we have a record of what ones are ok and which ones are not, please help filling it in...

docs.google.com/spreadsheets/d/19VruLK59SFVOeYtsTnog4mWo_EKTlwrTQm-_-o4u3Qk/edit?usp=sharing
Its about matching the right adapter with the modules PCUAE Network Mode has already so that why we need you to add the adapter to the spreadsheet cause we do not know what one works and what one does not work, the more you add there the better and helps others to use the right adapter.
Its best to try and get a older network adapter cause how old the kernal is in THEC64, Kernel v3.4.39 - 2012, if you use a new network adapter, it might not have driver modules for it so they can not be added, thats why I say match up the network adapter with the modules.
To get this to work in PCUAE, what you have to do.
=================================
You will need a compatible adapter for it to work and plugged into one of the machines USB Ports on the right of the machine or in a USB 4 Port Hub, you might need it powered.
Look for this chipset rt2800usb - wiki.debian.org/rt2800usb and look for the first one on the list... Ralink RT2070 now look on the internet for it maybe on ebay or Amazon
I found some on ebay... Here and Amazon... Here and Here.
Look on there and match them up with the Debian page then you can get the one that works in PCUAE...

If you are using a USB WIFI Dongle or Adapter then you need to go to PCUAE Network Mode Settings to add the SSID and Password from your router otherwise you will not get a IP Address and will not connect to the WIFI network.
1. You do not need to enable it now, its enabled already, just go to PCUAE Network Settings if you need to check USB Ethernet Adapter/USB WIFI Dongle has a IP Address and if its installed the USB Ethernet Adapter/USB WIFI Dongle Driver, once it has a IP address then you can use VICE Mode.
When plugging in a new USB Network Adapter run option 3: Driver Scanner so it can build a new driver catch file, its a database of all the drivers and adapters aliases, it needs building sometime when you plug in a new USB Network Adapter cause if you don't then it might not see the adapter.
2. Boot into VICE Mode by loading up Mode Changer(CTRL+F5) and picking VICE Mode from the Mode Changer Menu.
3. Once VICE Mode has loaded, then press CTRL+0 to load C64 BBS Mode(Striketerm 2014).
4. Press F5 then pick a BBS board with a,b,c,d,e,f... keys on the keyboard to select one from the list and press Return to load it... Done, you see it say CONNECTING...then it should be loading the BBS board now...

Original post...
For about 3 or 4 days now being working on adding the internet to PCUAE and VICE Mode, I managed it install a network adding the network drivers to PCUAE and a DNS Client.
It finding my WU71RL USB WIFI Dongle and adding the rt2800usb module and connecting it to the internet and getting a IP Address...
Its coming...

I managed to connect to Commodore Server using the V-1514 software and puting its IP address in the RS232 settings in C64 emulator.
Plus with help from jj0...
the Manic Rules Expert..
got it working.
VICE Mode connected to Commodore Server...

Now I am working on getting BBS boards to work, I compiled TCPSER and got it to run in the background when you start VICE Mode, its a TCP to SERIAL Emulator made for VICE so you can communicate the old way via a network to serial, it converts the info from eth0 the network and sends it to the serial device in the VICE Emulator so this should work on any of the other machines too.
TCPSER, Waiting for a connection. info from putty ttyS0, you will not see this screen
This is VICE connecting to Borderlinebbs.dyndns.org
Theses are the LEDs on the modem, what you would see on a modem if your connected or not
Connected
Control Lines: DSR:1 DCD:1 CTS:1
Disconected
Control Lines: DSR:1 DCD:0 CTS:1
Disconnecting...
and a screenshot of VICE Mode loading Borderline BBS in CCGMS

Borderline in BBS STRIKETERM 2014

So the next version of PCUAE will have Internet Access, oh and it works to in LINUX(X Windows Mod) Mode too..
For about 3 or 4 days now being working on adding the internet to PCUAE and VICE Mode, I managed it install a network adding the network drivers to PCUAE and a DNS Client.
It finding my WU71RL USB WIFI Dongle and adding the rt2800usb module and connecting it to the internet and getting a IP Address...
#-------------------------------------------
Searching for a network, eth0 or wlan0...
#-------------------------------------------
usb:v05E3p0610d0654dc09dsc00dp01ic09isc00ip00 -> v05E3p0610d
v05E3p0610d -> No driver found, no driver module included.
usb:v0BDAp0306d0117dc00dsc00dp00ic08isc06ip50 -> v0BDAp0306d
v0BDAp0306d -> No driver found, no driver module included.
usb:v148Fp3070d0101dc00dsc00dp00icFFiscFFipFF -> v148Fp3070d
v148Fp3070d -> rt2800usb.ko
insmod /tmp/pcuae_network/bin/../Maxi/lib/modules/3.4.39/mac80211.ko
insmod /tmp/pcuae_network/bin/../Maxi/lib/modules/3.4.39/rt2x00lib.ko
insmod /tmp/pcuae_network/bin/../Maxi/lib/modules/3.4.39/rt2800lib.ko
insmod /tmp/pcuae_network/bin/../Maxi/lib/modules/3.4.39/rt2x00usb.ko
insmod /tmp/pcuae_network/bin/../Maxi/lib/modules/3.4.39/rt2800usb.ko
wpa_supplicant v2.4
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/tmp/pcuae_network/bin/../network/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/tmp/pcuae_network/bin/../network/wpa_supplicant.conf' -> '/tmp/pcuae_network/bin/../network/wpa_supplicant.conf'
Reading configuration file '/tmp/pcuae_network/bin/../network/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=8):
53 4b 59 39 31 37 37 31 SKY91771
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='SKY19765'
nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory)
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0xb6f914b0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=040a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=040b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=040c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=040d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=090a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=090b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=090c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=090d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=0409506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=7f506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0xb6f914b0 match=0505
netlink: Operstate: ifindex=6 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory)
nl80211: driver param='(null)'
Add interface wlan0 to a new radio phy0
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 40 MHz 20 mBm (no IR)
nl80211: 5735-5835 @ 40 MHz 20 mBm (no IR)
nl80211: Added 802.11b mode based on 802.11g information
wlan0: Own MAC address: 00:06:4f:97:67:bd
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlan0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan0: Setting scan request: 0.100000 sec
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
TDLS: Driver does not support TDLS channel switching
wlan0: WPS: UUID based on MAC address: 00375ed4-7106-5133-8f4c-53e001580e35
ENGINE: Loading dynamic engine
ENGINE: Loading dynamic engine
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Daemonize..
udhcpc: started, v1.25.1
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending select for 192.168.0.50
udhcpc: lease of 192.168.0.50 obtained, lease time 86400
deleting routers
adding dns 192.168.0.1
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
No action as either wlan0 or eth0 already exists
#--------------------------------------
Turning on the SCP Server now...
#--------------------------------------
Use SCP only: user: root pass: miniR00t!
Use WinSCP and SCP to connect not SFTP.
[553] Jan 01 05:56:11 Running in background
Done... SCP Server ready.
#-----------------------------------
All Done... PCUAE Network Mode
is now running in the background.
#-----------------------------------
Its coming...

I managed to connect to Commodore Server using the V-1514 software and puting its IP address in the RS232 settings in C64 emulator.
Plus with help from jj0...


VICE Mode connected to Commodore Server...

Now I am working on getting BBS boards to work, I compiled TCPSER and got it to run in the background when you start VICE Mode, its a TCP to SERIAL Emulator made for VICE so you can communicate the old way via a network to serial, it converts the info from eth0 the network and sends it to the serial device in the VICE Emulator so this should work on any of the other machines too.
TCPSER, Waiting for a connection. info from putty ttyS0, you will not see this screen
1970-01-01 02:28:48:-1225326064:INFO:Server socket bound to port
1970-01-01 02:28:48:-1225326064:INFO:Server socket listening for connections
1970-01-01 02:28:48:-1225326064:INFO:Opening ip232 device
1970-01-01 02:28:48:-1225326064:INFO:Server socket bound to port
1970-01-01 02:28:48:-1225326064:INFO:Server socket listening for connections
1970-01-01 02:28:48:-1225326064:INFO:ip232 device configured
1970-01-01 02:28:48:-1235348368:INFO:Control Lines: DSR:1 DCD:0 CTS:1
1970-01-01 02:28:48:-1235348368:INFO:Disconnecting modem
1970-01-01 02:28:48:-1235348368:INFO:Disconnecting
1970-01-01 02:28:48:-1235348368:INFO:Control Lines: DSR:1 DCD:0 CTS:1
This is VICE connecting to Borderlinebbs.dyndns.org
1970-01-01 02:19:32:-1234889616:INFO:Control Lines: DSR:1 DCD:0 CTS:1
1970-01-01 02:19:39:-1234889616:INFO:taking modem off hook
1970-01-01 02:19:39:-1234889616:INFO:Connecting
1970-01-01 02:19:40:-1234889616:INFO:Connection to BORDERLINEBBS.DYNDNS.ORG established
1970-01-01 02:19:40:-1234889616:INFO:Control Lines: DSR:1 DCD:1 CTS:1
Theses are the LEDs on the modem, what you would see on a modem if your connected or not
Connected
Control Lines: DSR:1 DCD:1 CTS:1
Disconected
Control Lines: DSR:1 DCD:0 CTS:1
Disconnecting...
1970-01-01 02:28:21:-1253051280:INFO:No socket data read, assume closed peer
1970-01-01 02:28:21:-1234889616:INFO:Disconnecting modem
1970-01-01 02:28:21:-1234889616:INFO:Disconnecting
1970-01-01 02:28:21:-1234889616:INFO:Control Lines: DSR:1 DCD:0 CTS:1
and a screenshot of VICE Mode loading Borderline BBS in CCGMS

Borderline in BBS STRIKETERM 2014

So the next version of PCUAE will have Internet Access, oh and it works to in LINUX(X Windows Mod) Mode too..
