Date: Thu, 26 Feb 1998 02:56:46 -0600 (CST) From: Font <font@Mcs.Net> To: questions@FreeBSD.ORG Subject: userland ppp unhappy with PortMaster-2? Message-ID: <Pine.BSF.3.95.980226024247.25291B-100000@Jupiter.Mcs.Net>
next in thread | raw e-mail | index | archive | help
I have a FreeBSD box running 2.2.5-RELEASE which is happy enough to dial
up two ISPs, but a third, which has a Livingston PortMaster-2e on the
other end, just won't connect properly with my FreeBSD box.
Connecting to the PM-2e with Win95/DUN or MacOS/FreePPP works fine. It's
only ppp in FreeBSD that's having a problem. Is it possible that
something in the PM-2e configuration or in the remote (all static) routing
tables might be causing difficulty? The authentication used in the
Windows and MacOS tests was the same user/passwd pair used in the FreeBSD
tests.
I am not using IP aliasing. The FreeBSD box has just one ed0 and one
tun0. The ppp.conf looks pretty much like this:
default:
set device /dev/cuaa0
set speed 115200
disable pred1
deny pred1
disable lqr
deny lqr
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0
OK-AT-OK \\dATDT\
\T TIMEOUT 40 CONNECT"
set redial 10 3
set log +connect
xyz:
set authname myname
set authkey mypass
set phone myphone
set timeout 900
accept pap
deny chap
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0
set openmode active
This is pretty much straight out of the tutorial. After I dialup and
authenticate with ppp, my netstat -rn looks like:
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.32 UGSc 2 0 tun0
127.0.0.1 127.0.0.1 UH 0 2 lo0
192.168.1 192.168.1.254 UGSc 0 4 tun0
192.168.1.32 192.168.1.254 UH 3 0 tun0
192.168.2 link#1 UC 0 0
192.168.2.2 0:aa:0:c2:87:35 UHLW 3 4905 ed0 928
192.168.2.3 0:c0:93:0:3b:ce UHLW 2 157 lo0
192.168.2.128 8:0:3e:1d:33:19 UHLW 0 551 ed0 987
192.168.2.255 ff:ff:ff:ff:ff:ff UHLWb 2 42 ed0
Here, 192.168.2.3 is the machine trying to make the connection.
192.168.1.254 is the address assigned by the PM-2e. 192.168.1.32 is the
address of the PM-2e.
This looks pretty much identical with the other ISPs which work fine (and
are incidentally using FreeBSD, and probably PortMasters too).
I'm confused. What am I overlooking here?
I have control of the PortMaster-2e at the other end, since it's my
company's equipment, so if there's something in there that I may need to
adjust, I can do that. I've never seen such a problem with the ppp in
FreeBSD before, this must be something obvious. Sigh.
Oh yeah. I can ping the machines on the other side just fine. But I
can't reach them with nslookup, telnet, etc. I have the firewall software
installed on the FreeBSD box trying to connect but it's set to "open" (and
it is open).
Pointers are much appreciated. This is my first experience with all of
this equipment at once.
I did try a static host route through the PM-2e for the IP address
assigned by the PM-2e, but this didn't do anything. Didn't think it
would. Why would Windows and MacOS work fine but not FreeBSD? Wah!
A bug in my MUA causes news.announce.newusers font
to be sent to beneficiaries and senders of UCE/SPAM. @
mcs.net
Wishes are like dishes.
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?Pine.BSF.3.95.980226024247.25291B-100000>