Date: Sat, 25 Nov 2000 15:47:34 mst7mst From: "Duke Normandin" <01031149@3web.net> To: Jim Durham <durham@w2xo.pgh.pa.us> Cc: questions@freebsd.org Subject: Re: 3.3R <--> win95 Message-ID: <20001126002958.A38AF37B4C5@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
On 25 Nov 00 at 12:32, Jim Durham wrote:
>
>On Fri, 24 Nov 2000, Duke Normandin wrote:
>
>> On 24 Nov 00 at 10:44, Igor' Robul' wrote:
>> >
>> >On Thu, Nov 23, 2000 at 11:42:50PM +0000, Duke Normandin wrote:
>> >> I want the following:
>> >> 3.3R <x-over> win95 <dial-up> ISP
>> >>
>> >> I *have* to use win95 to connect to my ISP. Win95 won't route so I'm
>> >> pooched as far as connecting to my ISP from the FBSD box - I think.
>> >>
>> >> So, for the moment, all I want is an ethernet connection between the two
>> >> boxes. Should I disable tun0 in rc.conf? Can't the "lo0, tun0 and ep0
>> >> co-exist? I thought that "routed" was suppose to do just that. What
>> >Disable tun0. You don't need it.
>> >Also, make sure you have made correct crossover.
>>
>
>You need to tell us just what you are trying to accomplish and
>what you have running on the 3.3 system. I'm not clear on
>what you want to do.
>
>Please explain why you "*have*" to use 95 to dial your ISP.
> This is not usually the case with any ISP I've dealt with.
I realize that my scenario is not the *usual* way! However, I use a free
ISP that insists in having users run his proprietary win95-only software.
His dialer does not even show up in $MS DUN window. So Internet
connections have to happen from the win95 side -- as far as I can tell. It
would be great if I could run Lynx from the FBSD box and trigger a
connection in the win95 box - but I've been told that win95 can't do that
( I believe that the correct terminology is that it cannot "route").
>
>Are you using userland PPP or kernel PPP? Userland PPP uses
> the tun0 interface to connect to the internal networking in
> FreeBSD, so you need it. If you are using the kernel PPP,
> it's ppp0.
>
Up to 6 months ago, I was using a now-defunct ISP to which I could connect
from the FBSD box -- and I did so. I had userland ppp installed using
tun0. I have a shell script - if_start.tun0 - which has ppp -auto my_isp.
All of this worked great for this former ISP. I've renamed the script
hoping that it will not interfere with things.
>What does the ep0 interface connect to?
It connects to my win95 NIC via a x-over cable. As of 11:57:35 PM last
night, I am now able to successfully ping from both ends.
>Are you running Samba on the 3.3 box? What are you tring
> to accomplish? Are you just wanting to telnet or ftp into
> it from the 95 box, or are you wanting to do file sharing
> with M$ networking? If so, you need Samba to do M$ networking.
No Samba at the moment! I'm in the throes of learning hte lay-of-the-
networking-land (obviously) so KISS is my guiding principle. All I want is
ftp/telnet between the two. Samba is for down the road...
>
>Yes, you can have both interfaces running at the same time by
> netmasking them properly.
good....what I needed to know! Like I said above, I can now ping both
ways, however, when I first boot the system I still get the message "using
interface tun0. Then I do a "ps -ax" and sure enough there's a PID for ppp
-auto my_isp even though I have set PPP_enable="NO" and commented out
all PPP stuff in /etc/rc.conf. So I do a kill -HUP ppp_pid and I then can
ping to my hearts content.
So.... I may not have a current use for tun0, but I may down the road. So
how do I unlink tun0 from the LAN connection? ifconfig -a shows:
ep0: flags=8843<UP.BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
ether 00:60:97:0c:c4:5e
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.1 --> 10.0.0.2 netmask 0xffffff00
I can see above that the 2nd line for tun0 is what is causing the problem,
but how it got that way I just don't know. I set up the NIC /etc/rc.conf
with ifconfig_ep0="inet 10.0.0.1 netmask 255.255.255.0". I don't think
that I hosed that line, did I? Other than that I updated /etc/hosts with
10.0.0.1 odie.rockingd.calgary.ab.ca odie
10.0.0.1 odie.rockingd.calgary.ab.ca
10.0.0.2 mandy.rockingd.calgary.ab.ca mandy
10.0.0.2 mandy.rockingd.calgary.ab.ca
besides the 127.0.0.1 stuff. resolv.conf still has my previous ISP's
nameservers in it -- but that shouldn't affect things - but what do I know!
>> The crossover custom (professionally) made and pre-tested. So I'm relying
>> on that. Do I comment out the following in rc.conf to disable tun0:?
>>
>> if_config_tun0=""
>>
>> and remove tun0 from the following:?
>>
>> network_interface="lo0 tun0 ep0"
>>
>> Why would I *have* to do that? What if I wanted to use a modem on tun0
>> *and* ep0 for my LAN? Should I not be able to use both, with ppp "bound" to
>> tun0 only, or does ppp drive the packets on ethernet as well? I'm so
>> confused, I wouldn't know sh*t from Shine-Olla anymore ;,) Thanks...
>>
>
>So, please give us some info! My first take on this is that
>you have the cart and horse reversed. The usual way to set this
>up is to use the userland PPP on FreeBSD in the auto-dial mode
>to set up a PPP to your ISP, then use the ep0 interface to
>set up a LAN connection to your 95 boxes via their ethernet
>interface cards. Then you can turn on address translation
>on the PPP and the 95 box will look like it's directly on the
>internet. This is a common setup for small businesses with
>Windows computers and a FreeBSD box serviing as a gateway
>and auto dialup.
I hear you, but the *usual* isn't my scenario unfortunately. You seem to
have this stuff down to a fine science, so any help that you can throw at
this newbie would be appreciated more than you know. There's no panic for
this stuff -- just home-schooling myself. Just 2 old 486-66 boxes in the
basement ;,)
>-Jim Durham
-duke
Calgary,Alberta, Canada
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001126002958.A38AF37B4C5>