Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
Hi, On Mon, Aug 20, 2018 at 3:28 PM dmccunney wrote: > > On Mon, Aug 20, 2018 at 10:31 AM, Karen Lewellen > wrote: > > really? > > If sshdos no longer connects, then how am I sending this e-mail? > > Karen, the point to SSH is an *encrypted* connection to the other end. > Flaws have been identified in some of the commonly used encryption > schemes that make them crackable and therefore insecure. I believe a > TLS variant is the only currently known *secure* encryption scheme, > and SSH clients and server side code are all being updated to only > permit it. Connections using something else for encryption will > *fail*. Let's not be naive or overreact. Some problems are man-made, and some of it is fear-based. So it's not rational to expect everyone to constantly upgrade daily all software on their end. Not everything is a rolling Linux distro, and not every piece of software is actively supported by a team of engineers. I sympathize with fixing bugs, but constantly deprecating everything, without much warning, is annoyingly destructive. (I'm not directly referring to the moribund DOS ecosystem here, which is different, just talking in general.) Just to restate the obvious, our old Wget build (using DJGPP, by Michael Kostylev) from 2008 stopped working sometime this year. Well, partially stopped working, most sites work, but Github and SF.net no longer do. So I have to instead use a newer build (by same dude, circa 2015), which does thankfully work. This wouldn't be a problem except it's not mirrored to iBiblio (still) because I haven't verified its sources yet. Things like that are somewhat annoying to build, and trying to be Free/libre (ahem, "Free"DOS) is harder than it sounds sometimes. (Most big stuff like that is cross-compiled, which is far from easy, even with obvious tools and ports. I wish people, in general, were more careful and diligent about things like this. But I'm also grateful that we have such ports at all.) > I don't know what you get email from/send email to, but it still > accepts older deprecated encryption schemes. What will you do when it > no longer does? Does email even need to be encrypted?? Seriously, is this conversation that sensitive that we need to care? Maybe it's possible to spoof someone's identity and ruin their reputation or relationship with others. But even then, is that a serious, pervasive threat here? Security shouldn't be made mandatory on nonsense like this. DOS is always root, but sometimes it doesn't matter because you're not doing anything dangerous. Know what I mean? Maybe for online banking but not for just shooting the breeze. Do you put a lock on your refrigerator? You'd better, someone might steal all the cheese!!! > I do *not* see SSHDOS or SSHDOS2 getting updated to support the > currently mandated encryption scheme. Who would actually make the > updates? Who else? Presumably someone familiar with DJGPP, which indeed has updated SSL libraries. "ANNOUNCE: DJGPP port of OpenSSL 1.0.2o uploaded." (July 16) * https://groups.google.com/forum/#!topic/comp.os.msdos.djgpp/nkmm9_im6Ks * ftp://ftp.delorie.com/pub/djgpp/current/v2tk/ssl102ob.zip "This port has been created because 1.0.2 is the Long Term Support (LTS) version (support will be provided until 31st December 2019)" > > granted, I am not running freedos, but I can with my dos network > > configuration run a browser from my desktop if needful, it is just not > > needful for me due to ssh. > > Whether you run FreeDOS, or a flavor like MSDOS or DR-DOS is > irrelevant. What *is* relevant is that network standards are changing > and DOS is being left behind because there is no one to update > software for it to be compliant. The same guy (Juan) who did the SSL update for DJGPP also updated the Lynx port. To quote the newsgroup (again): "Please note that I am not a lynx user. I have ported it as a real world test for the OpenSSL and WATT-32 ports." There's also Links2 (2.16 is dated May 11), which also supports SSL/TLS (in non-lite, full, version): * http://links.twibright.com/download/binaries/dos/ > At some point, sooner rather than later, your DOS based home network > will no longer be *able* to connect to the outside world. What will > you do then? Presumably they will just use Linux? It's true that DOS isn't well-supported, but it's not totally hopeless. You always sound like you *want* it to be hopeless and dead, but it's not. Certainly some of her engineer friends / helpers could potentially get involved in improving or supporting aforementioned DJGPP ports, if they deem it useful enough. > I play with FreeDOS, and have some old DOS apps still running under > Windows using vDOS Plus, but I do that for fun. The actual *work* > gets done elsewhere, because it can't be *done* under DOS. I don't know why you think a real-mode OS that allows direct hardware access can't "do" some things. Now, whether anyone cares enough or knows enough to actually do it is another story, but
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
I suggest going to the sshdos page at sourceforge.net and reading the thread on the topic. In fact someone posted the thread here too in a prior discussion. Person needed to access openssh in the 7 plus range, we have that here at shellworld as well using Ubuntu 16.04 or so. it is where I use ssh2d386 to telnet. what is allowed here is a broader range of dh keys, not to mention using a nonstandard port. Out of curiosity there are indeed two packages ssh2dos.zip and sshdos.zip listed as ssh options on the freedos page referenced by someone earlier. what is the difference between the two packages? On Mon, 20 Aug 2018, Eric Auer wrote: If sshdos no longer connects, then how am I sending this e-mail? I use dos exclusively and sshdos as packaged in ssh2021b. I explicitly wrote _common_ SSH server configurations. As far as I know, sshdos and ssh2dos do not support many "up to date" encryption styles and many servers expect to use modern styles which means they reject the DOS tool connection attempts. This does not exclude the possibility that your server is configured in a more relaxed way, of course. they configured sshdos to be recognized by current openssh... Interesting, so it was enough to change the config on the DOS side to be compatible with a (probably default) config of the openssh server on the other side? Which settings are needed on the DOS side to do this? Regards, Eric -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
On Mon, Aug 20, 2018 at 10:31 AM, Karen Lewellen wrote: > really? > If sshdos no longer connects, then how am I sending this e-mail? Karen, the point to SSH is an *encrypted* connection to the other end. Flaws have been identified in some of the commonly used encryption schemes that make them crackable and therefore insecure. I believe a TLS variant is the only currently known *secure* encryption scheme, and SSH clients and server side code are all being updated to only permit it. Connections using something else for encryption will *fail*. I don't know what you get email from/send email to, but it still accepts older deprecated encryption schemes. What will you do when it no longer does? I do *not* see SSHDOS or SSHDOS2 getting updated to support the currently mandated encryption scheme. Who would actually make the updates? > I use dos exclusively and sshdos as packaged in ssh2021b. > In the program readme file putty for windows is referenced as one element of > the various codes and libraries used in how the program was constructed. Which means they grabbed code from PuTTY as part of the SSH infrastructure. This is not the same thing as PuTTY itself. (And PuTTY is unnecessary on Linux or OS/X, as other compliant SSH solutions exist for them.) > Lastly, in the discussion area of sshdos an individual explains how they > configured sshdos to be recognized by current openssh...so > there is nothing in of itself about dOS that translates into it not > connecting. Yes, there is. See above about currently permitted encryption schemes. "Recognized by current OpenSSH" is not the same thing as being permitted to connect in an insecure manner. > granted, I am not running freedos, but I can with my dos network > configuration run a browser from my desktop if needful, it is just not > needful for me due to ssh. Whether you run FreeDOS, or a flavor like MSDOS or DR-DOS is irrelevant. What *is* relevant is that network standards are changing and DOS is being left behind because there is no one to update software for it to be compliant. At some point, sooner rather than later, your DOS based home network will no longer be *able* to connect to the outside world. What will you do then? I play with FreeDOS, and have some old DOS apps still running under Windows using vDOS Plus, but I do that for fun. The actual *work* gets done elsewhere, because it can't be *done* under DOS. I'm happy for you that DOS still meets your needs and you can do what you need to do with it. I'm just quite certain that at some point, you will no longer be able to. > Karen __ Dennis > On Mon, 20 Aug 2018, Eric Auer wrote: > >> May be using some misinformation, but what ssh client is included in Freedos if any? Is / was there a putty dos one for example? >> >> >> Putty is a combined terminal window and SSH client, >> so it is only needed in Windows. In Linux, you use >> one of the existing Terminal windows (which seem to >> be more versatile than the command com or cmd exe >> windows of Windows) and a text-based SSH client. >> >> In DOS, you would use sshdos and ssh2dos, which are >> for two different versions of the SSH protocol. Yet, >> both are too old and no longer connect with common >> SSH server configurations! Both are text based apps. >> >> A while ago, I tried to compile a custom secure >> protocol library for a project in Linux and I can >> tell you that those things unfortunately have a >> larger number of dependencies than the should... >> >> A starting point for finding something lightweight >> and feasible to port to DOS might be this list: >> >> https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries >> >> However, that is probably more useful when you want >> to add HTTPS support to a DOS browser and less when >> you want to upgrade SSH2DOS, but I am no expert in >> those things. >> >> Regards, Eric >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> >> > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user -- __ Dennis https://plus.google.com/u/0/105128793974319004519 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
> If sshdos no longer connects, then how am I sending this e-mail? > I use dos exclusively and sshdos as packaged in ssh2021b. I explicitly wrote _common_ SSH server configurations. As far as I know, sshdos and ssh2dos do not support many "up to date" encryption styles and many servers expect to use modern styles which means they reject the DOS tool connection attempts. This does not exclude the possibility that your server is configured in a more relaxed way, of course. > they configured sshdos to be recognized by current openssh... Interesting, so it was enough to change the config on the DOS side to be compatible with a (probably default) config of the openssh server on the other side? Which settings are needed on the DOS side to do this? Regards, Eric -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
really? If sshdos no longer connects, then how am I sending this e-mail? I use dos exclusively and sshdos as packaged in ssh2021b. In the program readme file putty for windows is referenced as one element of the various codes and libraries used in how the program was constructed. Lastly, in the discussion area of sshdos an individual explains how they configured sshdos to be recognized by current openssh...so there is nothing in of itself about dOS that translates into it not connecting. granted, I am not running freedos, but I can with my dos network configuration run a browser from my desktop if needful, it is just not needful for me due to ssh. Karen On Mon, 20 Aug 2018, Eric Auer wrote: May be using some misinformation, but what ssh client is included in Freedos if any? Is / was there a putty dos one for example? Putty is a combined terminal window and SSH client, so it is only needed in Windows. In Linux, you use one of the existing Terminal windows (which seem to be more versatile than the command com or cmd exe windows of Windows) and a text-based SSH client. In DOS, you would use sshdos and ssh2dos, which are for two different versions of the SSH protocol. Yet, both are too old and no longer connect with common SSH server configurations! Both are text based apps. A while ago, I tried to compile a custom secure protocol library for a project in Linux and I can tell you that those things unfortunately have a larger number of dependencies than the should... A starting point for finding something lightweight and feasible to port to DOS might be this list: https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries However, that is probably more useful when you want to add HTTPS support to a DOS browser and less when you want to upgrade SSH2DOS, but I am no expert in those things. Regards, Eric -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
>> May be using some misinformation, >> but what ssh client is included in Freedos >> if any? >> Is / was there a putty dos one for example? Putty is a combined terminal window and SSH client, so it is only needed in Windows. In Linux, you use one of the existing Terminal windows (which seem to be more versatile than the command com or cmd exe windows of Windows) and a text-based SSH client. In DOS, you would use sshdos and ssh2dos, which are for two different versions of the SSH protocol. Yet, both are too old and no longer connect with common SSH server configurations! Both are text based apps. A while ago, I tried to compile a custom secure protocol library for a project in Linux and I can tell you that those things unfortunately have a larger number of dependencies than the should... A starting point for finding something lightweight and feasible to port to DOS might be this list: https://en.wikipedia.org/wiki/Comparison_of_cryptography_libraries However, that is probably more useful when you want to add HTTPS support to a DOS browser and less when you want to upgrade SSH2DOS, but I am no expert in those things. Regards, Eric -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
have not tried the other one though, so. One of them incorporates putty for windows as well, making it possible to bring putty to dos without difficulty. On Sun, 19 Aug 2018, dmccunney wrote: On Sun, Aug 19, 2018 at 8:40 PM, Karen Lewellen wrote: May be using some misinformation, but what ssh client is included in Freedos if any? Is / was there a putty dos one for example? As far as I recall, there has never been a DOS version of PuTTY. It's Windows specific, though a Unix source archive exists if you want to try to build it on other platforms. (Releases are available as 32 bit or 64 bit code. Building a 16 bit version for DOS would be a considerable challenge.) The networking stuff available for FreeDOS is listed here, including two SSH versions for DOS: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/group-net.html (As I recall, you use one of those packages, so I'm not sure why you're asking.) __ Dennis -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
On Sun, Aug 19, 2018 at 8:40 PM, Karen Lewellen wrote: > May be using some misinformation, but what ssh client is included in Freedos > if any? > Is / was there a putty dos one for example? As far as I recall, there has never been a DOS version of PuTTY. It's Windows specific, though a Unix source archive exists if you want to try to build it on other platforms. (Releases are available as 32 bit or 64 bit code. Building a 16 bit version for DOS would be a considerable challenge.) The networking stuff available for FreeDOS is listed here, including two SSH versions for DOS: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/group-net.html (As I recall, you use one of those packages, so I'm not sure why you're asking.) __ Dennis -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
May be using some misinformation, but what ssh client is included in Freedos if any? Is / was there a putty dos one for example? On Sun, 19 Aug 2018, Bertho Grandpied via Freedos-user wrote: After fleshing out the net.cfg to a bare minimum - leaving Ethernet-II framing /only/ - it is working now ! Thanks for the heads-up ! On Sat, 18 Aug 2018 19:10:33 -0400, Don Flowers wrote : | Make sure your net.cfg setting are | specific to rtgeodi. Usually rtgbodi is | default. Also rearrange frame | hierarchy; there are several odipkt driver | you may have to hunt try way back | machine On Saturday, August 18, 2018, Bertho Grandpied via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > Had anyone been successfully DOS-networking using the RT Gigabit adapter > in Subj ... -- Czerno -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
> After fleshing out the net.cfg to a > bare minimum - leaving Ethernet-II framing /only/ - it is > working now ! I've received in-private request to display the contents of the so fleshed out NET.CFG. Thanks for asking. ! Here is the resultant, FWIW - it could hardly be simpler : --- NET.CFG - ; Link Support Max Stacks 8 buffers 6 1600 Link Driver rtgeodi NICNo 1 Frame Ethernet_II MEDIUM AUTO NetWare DOS Requester FIRST NETWORK DRIVE = F NETWARE PROTOCOL = NDS BIND --- Then loading and starting the protocol stack up-to and including the "packet" driver is as easy as : > LSL > RTGEODI > ODIPKT N.B. I suspect the "Netware DOS Requester" section in the above is not relevant and could be ditched also, but I haven't checked yet and I am cut-n-pasting what is sure working... HTH... -- Czerno -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
After fleshing out the net.cfg to a bare minimum - leaving Ethernet-II framing /only/ - it is working now ! Thanks for the heads-up ! On Sat, 18 Aug 2018 19:10:33 -0400, Don Flowers wrote : | Make sure your net.cfg setting are | specific to rtgeodi. Usually rtgbodi is | default. Also rearrange frame | hierarchy; there are several odipkt driver | you may have to hunt try way back | machine On Saturday, August 18, 2018, Bertho Grandpied via Freedos-user < freedos-user@lists.sourceforge.net> wrote: > Had anyone been successfully DOS-networking using the RT Gigabit adapter > in Subj ... -- Czerno -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
Previous links has ipxodi - following link has odipkt.
https://bbs.retropc.se/smmnetwk/00index.html
On Sun, Aug 19, 2018 at 8:18 AM Don Flowers wrote:
> http://dukeworld.com/idgames/utils/network/=s=a
>
> On Sat, Aug 18, 2018 at 7:10 PM Don Flowers wrote:
>
>> Make sure your net.cfg setting are specific to rtgeodi. Usually rtgbodi
>> is default. Also rearrange frame hierarchy; there are several odipkt
>> driver you may have to hunt try way back machine
>>
>> On Saturday, August 18, 2018, Bertho Grandpied via Freedos-user <
>> freedos-user@lists.sourceforge.net> wrote:
>>
>>> Had anyone been successfully DOS-networking using the RT Gigabit adapter
>>> in Subj, I will
>>> humbly take their lessons. My new board (Biostar A68MD-Pro with AMD A10
>>> CPU) has embedded Realtek 8168 GB ethernet controller, for which I sought a
>>> DOS "packet driver".
>>>
>>> At Realtek's site, no packet driver, but they do offer an "ODI" driver
>>> ("rtgeodi.com") : which I got, and then ran in turn the usual trilogy
>>> of TSRs:
>>>
>>> > LSL
>>> > RTGEODI
>>> > ODIPKT 1; comment : alternatively, PKT2ODI /B:2
>>>
>>> This "trilogy" installs "successfully" - at least, each TSR in turn
>>> while installing itself reports success.
>>>
>>> In conjunction with an appropriate NET.CFG... and a TCP/IP network stack
>>> such as Trumpet's, or built-in to DOS networking programs... it should've
>>> been a piece of cake, in my experience, but alas ! *None work* ! Not any
>>> type datagram seems to go in/out on the wire...
>>>
>>> I know the adapter itself is "good" (works as designed in, sorry to have
>>> to mention it, Windows 10).
>>> Also, the Realtek test program in DOS sees, accesses the adapter and
>>> local tests pass OK.
>>>
>>> At this point I'm lost. Either the, Realtek provided ODI driver doesn't
>>> in fact support the flavour of embedded adapter I have got, could there be
>>> a "secret sauce" required to initialise the adapter ?
>>>
>>>
>>> Ah ! I also tried the well known "net boot disk" (an image, run through
>>> Gru4DOS, since this new machine - of course - doesn't have floppy).
>>> Interestingly, /it/ didn't work either, though it identified the adapter
>>> correctly; significant, for the net bootdisk uses another approach
>>> altogether than what I have sketched above, namely it tries to install
>>> MS-DOS (NDIS) networking. Didn't work either :=(
>>>
>>> I am sure a number of people reading this letter are (much) more used to
>>> fixing this kind of problems than I will ever be. Hoping for a heads-up (or
>>> just tell me it won't work, so I don't lose my time and last hair on this
>>> enigma)...
>>>
>>> TYiA
>>>
>>> --
>>> Czerno
>>>
>>>
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>
NET.CFG
Description: Binary data
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
http://dukeworld.com/idgames/utils/network/=s=a
On Sat, Aug 18, 2018 at 7:10 PM Don Flowers wrote:
> Make sure your net.cfg setting are specific to rtgeodi. Usually rtgbodi is
> default. Also rearrange frame hierarchy; there are several odipkt driver
> you may have to hunt try way back machine
>
> On Saturday, August 18, 2018, Bertho Grandpied via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
>
>> Had anyone been successfully DOS-networking using the RT Gigabit adapter
>> in Subj, I will
>> humbly take their lessons. My new board (Biostar A68MD-Pro with AMD A10
>> CPU) has embedded Realtek 8168 GB ethernet controller, for which I sought a
>> DOS "packet driver".
>>
>> At Realtek's site, no packet driver, but they do offer an "ODI" driver ("
>> rtgeodi.com") : which I got, and then ran in turn the usual trilogy of
>> TSRs:
>>
>> > LSL
>> > RTGEODI
>> > ODIPKT 1; comment : alternatively, PKT2ODI /B:2
>>
>> This "trilogy" installs "successfully" - at least, each TSR in turn while
>> installing itself reports success.
>>
>> In conjunction with an appropriate NET.CFG... and a TCP/IP network stack
>> such as Trumpet's, or built-in to DOS networking programs... it should've
>> been a piece of cake, in my experience, but alas ! *None work* ! Not any
>> type datagram seems to go in/out on the wire...
>>
>> I know the adapter itself is "good" (works as designed in, sorry to have
>> to mention it, Windows 10).
>> Also, the Realtek test program in DOS sees, accesses the adapter and
>> local tests pass OK.
>>
>> At this point I'm lost. Either the, Realtek provided ODI driver doesn't
>> in fact support the flavour of embedded adapter I have got, could there be
>> a "secret sauce" required to initialise the adapter ?
>>
>>
>> Ah ! I also tried the well known "net boot disk" (an image, run through
>> Gru4DOS, since this new machine - of course - doesn't have floppy).
>> Interestingly, /it/ didn't work either, though it identified the adapter
>> correctly; significant, for the net bootdisk uses another approach
>> altogether than what I have sketched above, namely it tries to install
>> MS-DOS (NDIS) networking. Didn't work either :=(
>>
>> I am sure a number of people reading this letter are (much) more used to
>> fixing this kind of problems than I will ever be. Hoping for a heads-up (or
>> just tell me it won't work, so I don't lose my time and last hair on this
>> enigma)...
>>
>> TYiA
>>
>> --
>> Czerno
>>
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS networking with embedded Realtek PCIe - 8168
Make sure your net.cfg setting are specific to rtgeodi. Usually rtgbodi is
default. Also rearrange frame hierarchy; there are several odipkt driver
you may have to hunt try way back machine
On Saturday, August 18, 2018, Bertho Grandpied via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> Had anyone been successfully DOS-networking using the RT Gigabit adapter
> in Subj, I will
> humbly take their lessons. My new board (Biostar A68MD-Pro with AMD A10
> CPU) has embedded Realtek 8168 GB ethernet controller, for which I sought a
> DOS "packet driver".
>
> At Realtek's site, no packet driver, but they do offer an "ODI" driver ("
> rtgeodi.com") : which I got, and then ran in turn the usual trilogy of
> TSRs:
>
> > LSL
> > RTGEODI
> > ODIPKT 1; comment : alternatively, PKT2ODI /B:2
>
> This "trilogy" installs "successfully" - at least, each TSR in turn while
> installing itself reports success.
>
> In conjunction with an appropriate NET.CFG... and a TCP/IP network stack
> such as Trumpet's, or built-in to DOS networking programs... it should've
> been a piece of cake, in my experience, but alas ! *None work* ! Not any
> type datagram seems to go in/out on the wire...
>
> I know the adapter itself is "good" (works as designed in, sorry to have
> to mention it, Windows 10).
> Also, the Realtek test program in DOS sees, accesses the adapter and local
> tests pass OK.
>
> At this point I'm lost. Either the, Realtek provided ODI driver doesn't in
> fact support the flavour of embedded adapter I have got, could there be a
> "secret sauce" required to initialise the adapter ?
>
>
> Ah ! I also tried the well known "net boot disk" (an image, run through
> Gru4DOS, since this new machine - of course - doesn't have floppy).
> Interestingly, /it/ didn't work either, though it identified the adapter
> correctly; significant, for the net bootdisk uses another approach
> altogether than what I have sketched above, namely it tries to install
> MS-DOS (NDIS) networking. Didn't work either :=(
>
> I am sure a number of people reading this letter are (much) more used to
> fixing this kind of problems than I will ever be. Hoping for a heads-up (or
> just tell me it won't work, so I don't lose my time and last hair on this
> enigma)...
>
> TYiA
>
> --
> Czerno
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] DOS networking with embedded Realtek PCIe - 8168
Had anyone been successfully DOS-networking using the RT Gigabit adapter in
Subj, I will
humbly take their lessons. My new board (Biostar A68MD-Pro with AMD A10 CPU)
has embedded Realtek 8168 GB ethernet controller, for which I sought a DOS
"packet driver".
At Realtek's site, no packet driver, but they do offer an "ODI" driver
("rtgeodi.com") : which I got, and then ran in turn the usual trilogy of TSRs:
> LSL
> RTGEODI
> ODIPKT 1; comment : alternatively, PKT2ODI /B:2
This "trilogy" installs "successfully" - at least, each TSR in turn while
installing itself reports success.
In conjunction with an appropriate NET.CFG... and a TCP/IP network stack such
as Trumpet's, or built-in to DOS networking programs... it should've been a
piece of cake, in my experience, but alas ! *None work* ! Not any type
datagram seems to go in/out on the wire...
I know the adapter itself is "good" (works as designed in, sorry to have to
mention it, Windows 10).
Also, the Realtek test program in DOS sees, accesses the adapter and local
tests pass OK.
At this point I'm lost. Either the, Realtek provided ODI driver doesn't in fact
support the flavour of embedded adapter I have got, could there be a "secret
sauce" required to initialise the adapter ?
Ah ! I also tried the well known "net boot disk" (an image, run through
Gru4DOS, since this new machine - of course - doesn't have floppy).
Interestingly, /it/ didn't work either, though it identified the adapter
correctly; significant, for the net bootdisk uses another approach altogether
than what I have sketched above, namely it tries to install MS-DOS (NDIS)
networking. Didn't work either :=(
I am sure a number of people reading this letter are (much) more used to fixing
this kind of problems than I will ever be. Hoping for a heads-up (or just tell
me it won't work, so I don't lose my time and last hair on this enigma)...
TYiA
--
Czerno
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
