We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


TCP/IP Ethernet

rayc021897 asked
Medium Priority
Last Modified: 2011-10-03
I have a win95 box and a linux box that I want to network together.  I have followed the Ethernet/IP Masquerade/NET HOWTOS and still am having problems.  Here is the situdation:

Linux Kernel 2.0.27
SMC WD8013 Ethernet cards

Linux box:
GW (my ISP)

The kernel see the ETH0 device it shows up during boot fine.

/etc/rc.d/rc.inet1 runs fine...

route looks fine

When I ping (my win95 box) I get noting yet TX and RX show up on my ifconfig

Likewise Ping from my win95 box to my linux box. I see TX/RX lite on the win95box and see RX lite on the linux box yet ping says no connection 100% packet loss.

This is complicated:  If anyone is willing to takle this one
email me I setup Telnet access to my box.

Thank you,



Watch Question

If you havent got it fixed by now - This is the problem as I understand it from your description.

Machine A (Linux,
Machine B (Win95,

Machine B has an always up ppp on

You cant ping either machines from the other.

Lets take it from the start.

192.168.1.x is always on the same physical net, so the gateway information is irrelevant.
If you can't ping the one from the other, either the net software or the physical link is broken.
In other words - you have a bad cable (**VERY** likely)
Terminated correctly ? Most people forget that you must have a T-peice in both ends with a terminator on both and the female connected to the board. Never the cables directly.

Get that to work first. And don't be fooled. There are only these two possibilities. Either the network hardware or the network drivers. There is no possibility that it is Linux acting up.
If you can get ifconfig data then the network drivers stand.
So it could be the Win95 drivers or the cables.

When you have that working - next problem.
You are running named. Be carefull with that.
Masquerade and named doesn't always go hand in hand.
Try telling your resolver that name service is not available.
(Edit /etc/resol* and /etc/host.conf*)
I have had some strange problems because masquerade found the network name and then tried to reconnect to that when the line dropped. It couldn't because it was a  dynamic ppp.

Also be aware of that pppd is a script in the newer Linux's.
You must throw the script away and rename the pppd2.whateverIsNewest to pppd. Otherwise diald can't control whats going on. If it tries to drop the line it kills the pppd-script and doesn't kill the pppd itself. You will get into some mess then.

But basicly - I don't like named and masq at the same time. I had big time problems with that.
You know you don't have name service when the route displauys numbers instead of names.

Otherwise I think your setup looks good.

I hope the broadcast address was a typo. is a network address, the broadcast address would be
could you give an ifconfig and a route -n from your machine?
wow!  where to start?  scratch the above 3 answers to not make your head start hurting.  this is not that difficult if you follow step by step.  I assume here that your linux machine is the one with the modem and is responsible for getting the internet connection and you want your windows machine to be on the net at the same time, using the same ip address of your linux machine.  This being the case your linux machine will have 2 ip addresses.  The first being an internal addy...192...the second being the *real* ip address of a computer on the internet - the real ip addy will be assigned to you when you dial into your isp.  So....follow what I have here exactly (it's time tested and mother approved :o) )

Linux Machine
Ip.  (.1 is default for a *real* router.  ie dont use it)
Dns:  Get from your ISP (I assume you are using dialup)
Gateway:  default route

Windows Machine:
Dns:  I have my linux machine doing dns requests so I have but you might try the same settings from your linux machine if it doesnt work for you.
Gateway:  ipaddress of your linux box.  ie.
I believe you also need Netbeui installed on your Windows machine along with TCP/IP.  

edit your /etc/hosts to look as follows     localhost   linuxmachine.com   windowsmachine.com

ensure your /etc/resolv.conf is as follows
search localdomain
nameserver xxx.xxx.xxxx.xxx <--assigned by your isp (DNS)
nameserver xxx.xxx.xxxx.xxx <-- Secondary DNS

With all that going reboot your windows machine about 5 times (jk) then try to ping each machine by ip address. ie.  from windows ping and from linux ping   If you don't have connectivity at this point you have to look at harware.  ie.  cables and cards and quite possibly windows.  Try pinging on each computer....if this works the problem is elsewhere, if it doesnt work, it means the problem is with that card/drivers/etc.

Provided you now have connectivity between the 2 machines you can get masquerading going.

ipchains -P forward DENY
ipchains -A forward -s -j MASQ

then you should be able to do a:  ipchains -L and see that
you are MASQ from 192.168.1.x to anywhere on the net.  

if you need more help email me at security@vines.net.


Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.