Re: /usr/sbin/ppp doubling connections on tun0
andrew clarke wrote: I'm using /usr/sbin/ppp for PPPoE over an ADSL modem in bridged mode: # ifconfig tun0 tun0: flags=8051 metric 0 mtu 1492 options=8 inet 203.217.27.170 --> 203.215.15.252 netmask 0x inet 203.214.46.107 --> 203.215.7.251 netmask 0x Opened by PID 49158 What would cause this? Notice the two IP addresses assigned to the same interface. It should just have one address assigned. Something causes the initial PPPoE session to stop, then another to restart without properly closing the previous PPPoE session. I'm not sure when this started happening but I've noticed it's become more frequent in the past few weeks. One theory I have is that it may have begun after I upgraded FreeBSD from 8.2 to 8.3 a few months back. I suppose concurrent PPPoE sessions aren't the end of the world, but obviously it makes no sense to have two on the same interface, so I'd like to prevent that. (Strictly speaking they aren't concurrent as the previously allocated IP [203.217.27.170 in the case above] no longer responds to pings, etc. It's dead, Jim.) The multiple IP addresses also causes /usr/ports/dns/ddclient to get confused and not tell DynDNS when a new IP address has been assigned, although perhaps that's a bug (sort of) in ddclient. I notice FreeBSD PR 151400 mentions: "The patch also makes a small change to how ppp(8) destroys interfaces at exit. Instead of just dealiasing interfaces and leaving them behind, they are now destroyed in the same manner "ifconfig destroy" works." I wonder if that's the cause? If I get a chance I'll try building a local copy of /usr/sbin/ppp with the patch reverted and test that, although it can be a difficult problem to replicate. Plus of course the patch doesn't explain the initial disconnections. I suspect that's an issue unrelated to /usr/sbin/ppp though. # cat /etc/ppp/ppp.conf default: set log phase chat lcp ipcp ccp tun command lqm set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 nat enable yes disable lqr disable ipv6cp set echoperiod 30 enable echo iinet: set device PPPoE:bge0 set authname secret set authkey secret set dial set login set mru 1492 set mtu 1492 set redial 15 0 add default HISADDR # grep ppp /etc/rc.conf ppp_enable="YES" ppp_mode="ddial" ppp_nat="YES" ppp_profile="iinet" # uname -a FreeBSD blizzard.phoenix 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun 12 00:39:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 In the meantime I've switched to using mpd5 (/usr/ports/net/mpd5) and /sbin/ipnat. So far, so good: # ifconfig ng0 ng0: flags=88d1 metric 0 mtu 1492 inet 124.170.51.116 --> 203.215.7.251 netmask 0x Regards Andrew Add these statements to your ppp.conf file disable iface-alias# Stop adding old IP address as alias # when ppp redials because line was # lost. These old IPs showed using # ifconfig -a on tun0. iface clear # Remove all previous IP addresses ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /usr/sbin/ppp doubling connections on tun0
On 11/20/2012 2:49 AM, andrew clarke wrote:
I'm using /usr/sbin/ppp for PPPoE over an ADSL modem in bridged mode:
# ifconfig tun0
tun0: flags=8051 metric 0 mtu 1492
options=8
inet 203.217.27.170 --> 203.215.15.252 netmask 0x
inet 203.214.46.107 --> 203.215.7.251 netmask 0x
Opened by PID 49158
What would cause this?
Notice the two IP addresses assigned to the same interface. It should
just have one address assigned.
Yes, I think this is caused by NAT. It seems that this is feature:
iface-alias
Default: Enabled if -nat is specified. This option simply tells
ppp to add new interface addresses to the interface rather than
replacing them. The option can only be enabled if network
address translation is enabled (``nat enable yes'').
With this option enabled, ppp will pass traffic for old interface
addresses through the NAT engine (see libalias(3)), resulting in
the ability (in -auto mode) to properly connect the process that
caused the PPP link to come up in the first place.
Disabling NAT with ``nat enable no'' will also disable
`iface-alias'.
One could say that it's a surprising one! But, yes, is deliberate.
HTH, Nikos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: /usr/sbin/ppp doubling connections on tun0
Hi, On Tue, 20 Nov 2012 11:49:39 +1100 andrew clarke wrote: > I'm using /usr/sbin/ppp for PPPoE over an ADSL modem in bridged mode: > > # ifconfig tun0 > tun0: flags=8051 metric 0 mtu 1492 > options=8 > inet 203.217.27.170 --> 203.215.15.252 netmask 0x > inet 203.214.46.107 --> 203.215.7.251 netmask 0x > Opened by PID 49158 > I noticed the same behaviour in wlan0 recently. I upgraded last night. After checking just now, wlan0 has only one IP address. I do not know if this is linked. I am running 10.0. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
/usr/sbin/ppp doubling connections on tun0
I'm using /usr/sbin/ppp for PPPoE over an ADSL modem in bridged mode: # ifconfig tun0 tun0: flags=8051 metric 0 mtu 1492 options=8 inet 203.217.27.170 --> 203.215.15.252 netmask 0x inet 203.214.46.107 --> 203.215.7.251 netmask 0x Opened by PID 49158 What would cause this? Notice the two IP addresses assigned to the same interface. It should just have one address assigned. Something causes the initial PPPoE session to stop, then another to restart without properly closing the previous PPPoE session. I'm not sure when this started happening but I've noticed it's become more frequent in the past few weeks. One theory I have is that it may have begun after I upgraded FreeBSD from 8.2 to 8.3 a few months back. I suppose concurrent PPPoE sessions aren't the end of the world, but obviously it makes no sense to have two on the same interface, so I'd like to prevent that. (Strictly speaking they aren't concurrent as the previously allocated IP [203.217.27.170 in the case above] no longer responds to pings, etc. It's dead, Jim.) The multiple IP addresses also causes /usr/ports/dns/ddclient to get confused and not tell DynDNS when a new IP address has been assigned, although perhaps that's a bug (sort of) in ddclient. I notice FreeBSD PR 151400 mentions: "The patch also makes a small change to how ppp(8) destroys interfaces at exit. Instead of just dealiasing interfaces and leaving them behind, they are now destroyed in the same manner "ifconfig destroy" works." I wonder if that's the cause? If I get a chance I'll try building a local copy of /usr/sbin/ppp with the patch reverted and test that, although it can be a difficult problem to replicate. Plus of course the patch doesn't explain the initial disconnections. I suspect that's an issue unrelated to /usr/sbin/ppp though. # cat /etc/ppp/ppp.conf default: set log phase chat lcp ipcp ccp tun command lqm set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 nat enable yes disable lqr disable ipv6cp set echoperiod 30 enable echo iinet: set device PPPoE:bge0 set authname secret set authkey secret set dial set login set mru 1492 set mtu 1492 set redial 15 0 add default HISADDR # grep ppp /etc/rc.conf ppp_enable="YES" ppp_mode="ddial" ppp_nat="YES" ppp_profile="iinet" # uname -a FreeBSD blizzard.phoenix 8.3-RELEASE-p3 FreeBSD 8.3-RELEASE-p3 #0: Tue Jun 12 00:39:29 UTC 2012 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 In the meantime I've switched to using mpd5 (/usr/ports/net/mpd5) and /sbin/ipnat. So far, so good: # ifconfig ng0 ng0: flags=88d1 metric 0 mtu 1492 inet 124.170.51.116 --> 203.215.7.251 netmask 0x Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ppp connection goes down - requires reboot
On 7/12/2012 10:18 AM, David Banning wrote:
> Lately I have a problem where the ppp connection goes down.
> Watching the log I see the following;
> Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: opening -> dial
> Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: dial -> carrier
> Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Disconnected!
> Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: carrier -> hangup
> Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Connect time: 5 secs: 0
> octets in, 0 octets out
5 seconds seems like a pretty tight for it to give up. Do you have any
other defaults in your ppp.conf not shown below ?
also add
enable echo
disable vjcomp
set lqrperiod 10
set cd 10
and when its not working, try
tcpdump -nei fxp0
You should see responses to your PADI requests from the remote BAS.
Also get rid of the 209.161.205.12 line. Typically your ISP will assign
you the static IP out of RADIUS and you dont need to specify it.
---Mike
>
> I shutdown ppp and restart it with no luck. I shutoff modem and
> reboot it and wait for connection light to go solid - still no go.
>
>
> my ppp.conf follows;
>
> default: # or name_of_service_provider
> set device PPPoE:fxp0 # replace xl1 with your ethernet device
> set mru 1492
> set mtu 1492
> set authname ***
> set authkey ***
> set log Phase tun command # you can add more detailed logging if you
> wish
> disable ipv6cp
> set dial
> set login
> set ifaddr 209.161.205.12 206.221.248.4
> set ifaddr 10.0.0.1/0 10.0.0.2/0
> add default HISADDR
> nat enable yes
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>
>
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ppp connection goes down - requires reboot
Lately I have a problem where the ppp connection goes down. Watching the log I see the following; Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: Connected! Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: opening -> dial Jul 12 09:54:58 3s1 ppp[30841]: tun0: Phase: deflink: dial -> carrier Jul 12 09:55:12 3s1 ppp[31114]: Phase: Using interface: tun0 Jul 12 09:55:12 3s1 ppp[31114]: Phase: deflink: Created in closed state Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: disable ipv6cp Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set dial Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set login Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 209.161.205.12 206.221.248.4 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.2/0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: add default HISADDR Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: nat enable yes Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set device PPPoE:fxp0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set mru 1492 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set mtu 1492 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set authname [login was here] Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set authkey Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set log Phase tun command Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: disable ipv6cp Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set dial Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set login Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 209.161.205.12 206.221.248.4 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.2/0 Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: add default HISADDR Jul 12 09:55:12 3s1 ppp[31114]: tun0: Command: default: nat enable yes Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: PPP Started (ddial mode). Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: bundle: Establish Jul 12 09:55:12 3s1 ppp[31115]: tun0: Phase: deflink: closed -> opening Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: Connected! Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: opening -> dial Jul 12 09:55:13 3s1 ppp[31115]: tun0: Phase: deflink: dial -> carrier Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Disconnected! Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: carrier -> hangup Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: 0 packets in, 0 packets out Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Thu Jul 12 09:55:13 2012 Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: hangup -> opening Jul 12 09:55:18 3s1 ppp[31115]: tun0: Phase: deflink: Enter pause (30) for redialing. I shutdown ppp and restart it with no luck. I shutoff modem and reboot it and wait for connection light to go solid - still no go. I called ISP and they say there is no problem. I try to login to the ISP with a windows box and am successful. Having no luck connecting with my server, I reboot, and all is fine. What could it be about rebooting the server that allows connection where otherwise it is not possible? Any ideas where I can look for answers? my ppp.conf follows; default: # or name_of_service_provider set device PPPoE:fxp0 # replace xl1 with your ethernet device set mru 1492 set mtu 1492 set authname *** set authkey *** set log Phase tun command # you can add more detailed logging if you wish disable ipv6cp set dial set login set ifaddr 209.161.205.12 206.221.248.4 set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR nat enable yes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Thanks You, now I understand how badly it was broken (the config of course), I confirm that using the config You send everything works like a charm now, for the record, here is mine complete config: | default: | set log Phase Chat LCP IPCP CCP tun command | | 3g: | set device /dev/cuaU0 | set speed 921600 | | set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ | \"\" AT OK-AT-OK \ | AT+CFUN=1 OK \ | AT+COPS=0 OK \ | AT+CGDCONT=1,\\\"IP\\\",\\\"www.plusgsm.pl\\\" OK \ | \dATDT\\T TIMEOUT 40 CONNECT" | | set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" | | set phone *99\# | set timeout 300 | set ifaddr 10.64.64.64/0 10.64.64.64/0 255.255.255.255 0.0.0.0 | add default HISADDR | enable dns | disable ipv6cp I am going to send update to the PR to close it ;) Thanks again, vermaden "Matthias Apitz" pisze: > El día Friday, June 29, 2012 a las 08:02:17AM +0200, vermaden escribió: > > > > I said this already: the /etc/ppp/ppp.conf file you are > > > using is completely broken and the log matches this; > > > > > > what should these AT cmds do in the section of 3g: > > > > > > 3g: > > > set device /dev/cuaU0 > > > set speed 38400 > > > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > > > add default HISADDR > > > term > > > AT+CFUN=1 > > > AT+CGDCONT=1,"IP","www.plusgsm.pl" > > > ATD*99# > > > > > > matthias > > > > I did not knew that its broken, I used the '3g' > > profile to connect, like that: # ppp -ddial 3g > > > > It worked very well without errors on 9.0-RELEASE > > and it stopped working after the update to the > > 9-STABLE, what is broken there? > > I can't imagine that 9-STABLE delivers such a broken file (already > because the "www.plusgsm.pl" entry in your file); I do not know how you > did the update and if maybe this is the result of some kind of broken > merging; I'm attaching the original file out of SVM (CURRENT) and mine > which have a working entry 'umts'; try to rebuild from both a workin one > by hand; > > matthias > > -- > Matthias Apitz > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 > -- ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
El día Friday, June 29, 2012 a las 08:02:17AM +0200, vermaden escribió: > > I said this already: the /etc/ppp/ppp.conf file you are > > using is completely broken and the log matches this; > > > > what should these AT cmds do in the section of 3g: > > > > 3g: > > set device /dev/cuaU0 > > set speed 38400 > > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > > add default HISADDR > > term > > AT+CFUN=1 > > AT+CGDCONT=1,"IP","www.plusgsm.pl" > > ATD*99# > > > > matthias > > I did not knew that its broken, I used the '3g' > profile to connect, like that: # ppp -ddial 3g > > It worked very well without errors on 9.0-RELEASE > and it stopped working after the update to the > 9-STABLE, what is broken there? I can't imagine that 9-STABLE delivers such a broken file (already because the "www.plusgsm.pl" entry in your file); I do not know how you did the update and if maybe this is the result of some kind of broken merging; I'm attaching the original file out of SVM (CURRENT) and mine which have a working entry 'umts'; try to rebuild from both a workin one by hand; matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ######### # PPP Sample Configuration File # Originally written by Toshiharu OHNO # Simplified 5/14/1999 by ws...@cdrom.com # # See /usr/share/examples/ppp/ for some examples # # $FreeBSD: head/etc/ppp/ppp.conf 203943 2010-02-16 01:07:06Z jkim $ # default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION # Ensure that "device" references the correct serial port # for your modem. (cuau0 = COM1, cuau1 = COM2) # set device /dev/cuau1 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 180# 3 minute idle timer (the default) enable dns # request DNS info (for resolv.conf) papchap: # # edit the next three lines and replace the items in caps with # the values which have been assigned by your ISP. # set phone PHONE_NUM set authname USERNAME set authkey PASSWORD set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR# Add a (sticky) default route # # $Id: ppp.conf,v 1.1 2011/11/20 06:07:03 guru Exp $ # # APN (AT+CGDCONT value): pinternet.interkom.de # # # default: set log Phase Chat LCP IPCP CCP tun command umts: set device /dev/cuaU0.0 # device name in CURRENT set speed 921600 # set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATZ OK \ AT+CFUN=1 OK \ AT+COPS=0 OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"pinternet.interkom.de\\\" OK \ \\dATDT\\T TIMEOUT 40 CONNECT" set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" # NAT (not used by me) # nat enable yes # alias enable yes # nat port tcp 192.168.0.0:ftp ftp # nat port tcp 192.168.0.0:http http nat enable yes nat port udp 127.0.0.1:1024-1030 1024-1030 nat port tcp 127.0.0.1:22 22 set phone *99*1\# set authname "x" set authkey "x" set timeout 300 set ifaddr 10.64.64.64/0 10.64.64.64/0 255.255.255.255 0.0.0.0 # add default HISADDR# Add a (sticky) default route enable dns disable ipv6cp # disable deflate # disable pred1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Hi, > Did it perhaps create more serial ports for you that were > not there before ? What is the output of ls -l /dev/cuaU* > > ---Mike # ls -l /dev/cuaU* crw-rw 1 uucp dialer0, 155 2012.06.29 06:42 /dev/cuaU0 crw-rw 1 uucp dialer0, 156 2012.06.29 06:42 /dev/cuaU0.init crw-rw 1 uucp dialer0, 157 2012.06.29 06:42 /dev/cuaU0.lock crw-rw 1 uucp dialer0, 161 2012.06.29 07:55 /dev/cuaU1 crw-rw 1 uucp dialer0, 162 2012.06.29 06:42 /dev/cuaU1.init crw-rw 1 uucp dialer0, 163 2012.06.29 06:42 /dev/cuaU1.lock I have tried both cuaU0 and cuaU1 but same result. > I said this already: the /etc/ppp/ppp.conf file you are > using is completely broken and the log matches this; > > what should these AT cmds do in the section of 3g: > > 3g: > set device /dev/cuaU0 > set speed 38400 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > add default HISADDR > term > AT+CFUN=1 > AT+CGDCONT=1,"IP","www.plusgsm.pl" > ATD*99# > > matthias I did not knew that its broken, I used the '3g' profile to connect, like that: # ppp -ddial 3g It worked very well without errors on 9.0-RELEASE and it stopped working after the update to the 9-STABLE, what is broken there? Regards, vermaden -- ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
El día Thursday, June 28, 2012 a las 07:54:48AM +0200, vermaden escribió: > Hi, > > at the 9.0-RELEASE I have had fully working ppp/3g connection via the > Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded > to 9-STABLE r237458 it does not work any more. > > Were there any significant changes in 9-STABLE that broke it? > > Here is more detailed info: > http://freebsd.org/cgi/query-pr.cgi?pr=169459 I said this already: the /etc/ppp/ppp.conf file you are using is completely broken and the log matches this; what should these AT cmds do in the section of 3g: 3g: set device /dev/cuaU0 set speed 38400 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 add default HISADDR term AT+CFUN=1 AT+CGDCONT=1,"IP","www.plusgsm.pl" ATD*99# matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
On 6/28/2012 1:54 AM, vermaden wrote: > Hi, > > at the 9.0-RELEASE I have had fully working ppp/3g connection via the > Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded > to 9-STABLE r237458 it does not work any more. > > Were there any significant changes in 9-STABLE that broke it? Did it perhaps create more serial ports for you that were not there before ? What is the output of ls -l /dev/cuaU* ---Mike > > Here is more detailed info: > http://freebsd.org/cgi/query-pr.cgi?pr=169459 > > Regards, > vermaden -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
umodem/ppp/3g stopped working after update from 9.0-RELEASE to 9-STABLE
Hi, at the 9.0-RELEASE I have had fully working ppp/3g connection via the Dell 5530 modem in my Dell Latitude E6400 laptop. After I upgraded to 9-STABLE r237458 it does not work any more. Were there any significant changes in 9-STABLE that broke it? Here is more detailed info: http://freebsd.org/cgi/query-pr.cgi?pr=169459 Regards, vermaden -- ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problems in ppp negotiating
On 2011/11/16 at 03:25, Matthias Apitz wrote: > > El día Wednesday, November 16, 2011 a las 01:14:42AM +0800, Denise H. G. > escribió: >> Hi >> >> What is in your /etc/ppp.conf? To better locate your problem, you'd >> better show us the config file. > > Hello, > > I was thinking in this, but then I realized that the ppp.bad file > contained it, even the SIM PIN; anyway, here it is: > > > # > default: > set log Phase Chat LCP IPCP CCP tun command > > umts: > > set device /dev/cuaU0.0 # device name in CURRENT > set speed 230400 > > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ > \"\" AT OK-AT-OK ATZ OK \ > AT+CFUN=1 OK \ > at+cpin="4708" O \ > AT+COPS=0 OK \ > AT+CGDCONT=1,\\\"IP\\\",\\\"pinternet.interkom.de\\\" OK \ > \\dATDT\\T TIMEOUT 40 CONNECT" > > set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" > > set phone *99*1\# > set authname "fonic" > set authkey "fonic" > set timeout 300 > set ifaddr 0.0.0.0/0 10.64.64.64/0 255.255.255.0 0.0.0.0 The line above might be the problem. If you dial mode is NOT `auto', you don't need `set ifaddr' thing, according to the manual of `ppp(8)'. Or you are using `auto' mode to dial up, give it try to use: set ifaddr 10.64.64.64/0 10.64.64.64/0 255.255.255.255 0.0.0.0 This part of the ppp configuration is about using IPCP protocal to negotiate IP address. And your attached ppp logs have IPCP errors. Anyway, I am not sure if this would help or not. Just give it try. Regards. > add default HISADDR# Add a (sticky) default route > enable dns > disable ipv6cp > -- > Matthias Apitz > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 > -- Hindsight is an exact science. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problems in ppp negotiating
El día Wednesday, November 16, 2011 a las 01:14:42AM +0800, Denise H. G. escribió: > Hi > > What is in your /etc/ppp.conf? To better locate your problem, you'd > better show us the config file. Hello, I was thinking in this, but then I realized that the ppp.bad file contained it, even the SIM PIN; anyway, here it is: # default: set log Phase Chat LCP IPCP CCP tun command umts: set device /dev/cuaU0.0 # device name in CURRENT set speed 230400 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATZ OK \ AT+CFUN=1 OK \ at+cpin="4708" O \ AT+COPS=0 OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"pinternet.interkom.de\\\" OK \ \\dATDT\\T TIMEOUT 40 CONNECT" set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" set phone *99*1\# set authname "fonic" set authkey "fonic" set timeout 300 set ifaddr 0.0.0.0/0 10.64.64.64/0 255.255.255.0 0.0.0.0 add default HISADDR# Add a (sticky) default route enable dns disable ipv6cp -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problems in ppp negotiating
Hi What is in your /etc/ppp.conf? To better locate your problem, you'd better show us the config file. Regards! -- Hindsight is an exact science. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
problems in ppp negotiating
Hello, I'm using ppp(8) to connect my netbook to my UMTS ISP, which works reasonable well; from time to time I encounter the situation that it is unwilling to negotiate with the peer, it stops with: Nov 15 12:28:41 tiny ppp[1370]: tun6: Phase: deflink: Too many IPCP REQs sent - abandoning negotiation this is for any attempt during some minutes (or even hours) and then it connects without any change on my ppp.conf; I'm attaching a log of ppp.bad and one of ppp.good; any ideas what I could do in my config? Thanks matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 Nov 15 12:28:52 tiny ppp[1370]: tun6: Phase: bundle: Establish Nov 15 12:28:52 tiny ppp[1370]: tun6: Phase: deflink: closed -> opening Nov 15 12:28:52 tiny ppp[1370]: tun6: Phase: deflink: Connected! Nov 15 12:28:52 tiny ppp[1370]: tun6: Phase: deflink: opening -> dial Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Phone: *99*1# Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: deflink: Dial attempt 1 of 1 Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: AT^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): OK Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: AT^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: OK^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: ATZ^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): OK Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: ATZ^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: OK^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: AT+CFUN=1^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): OK Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: AT+CFUN=1^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: OK^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: at+cpin=4708^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): O Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: at+cpin=4708^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: +CME ERROR: operation not allowed^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: AT+COPS=0^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): OK Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: AT+COPS=0^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: OK^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: AT+CGDCONT=1,"IP","pinternet.interkom.de"^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Expect(5): OK Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: AT+CGDCONT=1,"IP","pinternet.interkom.de"^M^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Received: OK^M Nov 15 12:28:52 tiny ppp[1370]: tun6: Chat: Send: ATDT*99*1#^M Nov 15 12:28:54 tiny ppp[1370]: tun6: Chat: Expect(40): CONNECT Nov 15 12:28:54 tiny ppp[1370]: tun6: Chat: Received: ATDT*99*1#^M^M Nov 15 12:28:54 tiny ppp[1370]: tun6: Chat: Received: CONNECT^M Nov 15 12:28:54 tiny ppp[1370]: tun6: Phase: deflink: dial -> carrier Nov 15 12:28:55 tiny ppp[1370]: tun6: Phase: deflink: /dev/cuaU0.0 doesn't support CD Nov 15 12:28:55 tiny ppp[1370]: tun6: Phase: deflink: carrier -> login Nov 15 12:28:55 tiny ppp[1370]: tun6: Phase: deflink: login -> lcp Nov 15 12:28:55 tiny ppp[1370]: tun6: LCP: FSM: Using "deflink" as a transport Nov 15 12:28:55 tiny ppp[1370]: tun6: LCP: deflink: State change Initial --> Closed Nov 15 12:28:55 tiny ppp[1370]: tun6: LCP: deflink: State change Closed --> Stopped Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: LayerStart Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: SendConfigReq(3) state = Stopped Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACFCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: PROTOCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACCMAP[6] 0x0000 Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: MRU[4] 1500 Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: MAGICNUM[6] 0xed29985d Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: State change Stopped --> Req-Sent Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: RecvConfigReq(3) state = Req-Sent Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACCMAP[6] 0x Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: MAGICNUM[6] 0x0a97f2dc Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: PROTOCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACFCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: SendConfigAck(3) state = Req-Sent Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACCMAP[6] 0x Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: MAGICNUM[6] 0x0a97f2dc Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: PROTOCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: ACFCOMP[2] Nov 15 12:28:56 tiny ppp[1370]: tun6: LCP: deflink: State change R
ppp with mode -auto
Hello, I'm using ppp(1) with mode -auto in a FreeBSD 8.x (an older 8-CURRENT); I'm reading in the man page that the link is not coming up until packages for the tun interface are arriving... But my ppp starts chatting and LCP... just when it is started. My ppp.conf file is attached; any ideas? Thanks in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ # # default: set log Phase Chat LCP IPCP CCP tun command umts: set device /dev/cuaU0.0 # device name in CURRENT set speed 230400 # set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATZ OK \ AT+CFUN=1 OK \ AT+COPS=0 OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"pinternet.interkom.de\\\" OK \ \\dATDT\\T TIMEOUT 40 CONNECT" set logout "ABORT BUSY ABORT ERROR TIMEOUT 30 \"\" +++ATH O ATH OK" set phone *99*1\# set authname "fonic" set authkey "fonic" set timeout 300 set ifaddr 0.0.0.0/0 10.64.64.64/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns disable ipv6cp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ppp auto only works on boot (8.1)
I upgraded from 7.3 to 8.1. I have an internal 3com (dial-up) 56k modem. My ppp.conf script works when I boot, but I cannot bring up the connection again when it has gone down by timing out or pppctl quit. Needless to say, there was no such problem in 7.3. I have been over and over the HARDWARE.txt without being able to find what other hardware I might still be able to buy that would allow me to connect by dial-up (not DSL). Of course I have all kinds of winmodems lying around, including sever Lucent modems that worked with a shim from a port that appears to have been abandoned. This seems to be where uart picks up the modem (dmesg) uart2: port 0xa400-0xa407 irq 17 at device 9.0 on pci3 uart2: [FILTER] This is ppp.log for successful connection (on boot) and failed connection after timeout (on boot - successful) Feb 17 09:48:13 debranded ppp[255]: tun0: Chat: Received: ATDT4194220^M^M Feb 17 09:48:13 debranded ppp[255]: tun0: Chat: Received: CONNECT Feb 17 09:48:13 debranded ppp[255]: tun0: Phase: deflink: dial -> carrier Feb 17 09:48:14 debranded ppp[255]: tun0: Phase: deflink: /dev/cuau2: CD detected Feb 17 09:48:14 debranded ppp[255]: tun0: Phase: deflink: carrier -> login Feb 17 09:48:14 debranded ppp[255]: tun0: Phase: deflink: login -> lcp Feb 17 09:48:14 debranded ppp[255]: tun0: LCP: FSM: Using "deflink" as a transport Feb 17 09:48:14 debranded ppp[255]: tun0: LCP: deflink: State change Initial --> Closed Feb 17 09:48:14 debranded ppp[255]: tun0: LCP: deflink: State change Closed --> Stopped Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: LayerStart Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACFCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: PROTOCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACCMAP[6] 0x Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRU[4] 1500 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MAGICNUM[6] 0x2f3117de Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: State change Stopped --> Req-Sent Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: RecvConfigReq(1) state = Req-Sent Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: <0x0>[4] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRU[4] 1524 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACCMAP[6] 0x0000 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: PROTOCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACFCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRRU[4] 1524 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ENDDISC[9] MAC 00:c0:7b:9f:76:34 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: SendConfigRej(1) state = Req-Sent Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: <0x0>[4] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRRU[4] 1524 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: SendIdent(0) state = Req-Sent Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MAGICNUM 2f3117de Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: TEXT user-ppp 3.4.2 (built COMPILATIONDATE) Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: RecvConfigAck(1) state = Req-Sent Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACFCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: PROTOCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACCMAP[6] 0x Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRU[4] 1500 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MAGICNUM[6] 0x2f3117de Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: State change Req-Sent --> Ack-Rcvd Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: RecvConfigReq(2) state = Ack-Rcvd Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRU[4] 1524 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACCMAP[6] 0x Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: PROTOCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACFCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ENDDISC[9] MAC 00:c0:7b:9f:76:34 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: SendConfigAck(2) state = Ack-Rcvd Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: MRU[4] 1524 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACCMAP[6] 0x Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: AUTHPROTO[5] 0xc223 (CHAP 0x05) Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: PROTOCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ACFCOMP[2] Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: ENDDISC[9] MAC 00:c0:7b:9f:76:34 Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: State change Ack-Rcvd --> Opened Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: LayerUp Feb 17 09:48:15 debranded ppp[255]: tun0: LCP: deflink: SendIdent(1) state = Opened Feb 17 09:
Re: How to configure ppp connection
Dnia poniedziałek, 23 sierpnia 2010 o 21:03:32 Polytropon napisał(a): > > > ppp ON localhost> dial > > Warning: deflink: /dev/cuad1: Bad file descriptor > > Warning: deflink: /dev/cuad0: Bad file descriptor > > PPP tries to access regular serial lines. > > > Nothing happens, there is still no connection. > > Sorry, I don't know enough about wireless network to be more specific, > but allow me this guess: If your connection requires PPPoE, you could > code something like this: > > blah: > set device PPPoE: > set authname > set authkey > set dial > set login > add default HISADDR > > Then, "ppp blah" would be used for manual dialing. I'm not sure in how > far you are required to code AT dialing sequences. > It's broadband, mobile (celluar?) connection via Play (www.playmobile.pl) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to configure ppp connection
On Mon, 23 Aug 2010 20:05:32 +0200, Jakub Nowacki wrote: > Hello! > > (First of all - forgive me my language, I'am form Poland) Dobre. :-) > I'am new in FreeBSD, but I have used Linux for a few year. As a first note, know that FreeBSD has *excellent* manpages. Know the "apropos" and "man" commands, as they will always help you. > I have got mobile modem: Huawei e1750c. As far as I know it is supported by > u3g driver. On Linux I use wvdial as a dialer, and there are no problems with > connection. On FreeBSD I just can't find propper ppp.conf, however I spend > many > hours googling and trying some. You don't need google as a means of OS documentation. :-) First, check /etc/ppp/ppp.conf which is the PPP configuration file. Also, read "man ppp". I have used ppp.conf in the past for dealing with PPPoE, and it worked without any problems. > when i try to use "ppp default" and then "dial" i got: You should define your own label for the connection in ppp.conf, e. g. the name of the provider (doesn't have to be very verbose). > # ppp default > Warning: Bad label in /etc/ppp/ppp.conf (line 2) - missing colon > Warning: Bad label in /etc/ppp/ppp.conf (line 2) - missing colon Check those. > ppp ON localhost> dial > Warning: deflink: /dev/cuad1: Bad file descriptor > Warning: deflink: /dev/cuad0: Bad file descriptor PPP tries to access regular serial lines. > Nothing happens, there is still no connection. Sorry, I don't know enough about wireless network to be more specific, but allow me this guess: If your connection requires PPPoE, you could code something like this: blah: set device PPPoE: set authname set authkey set dial set login add default HISADDR Then, "ppp blah" would be used for manual dialing. I'm not sure in how far you are required to code AT dialing sequences. > Some device nodes are created after I plug a modem. There is diff result > of listed /dev pre and post pluging: > ja...@iac-deb:~$ diff /media/disk/pre_dev /media/disk/post_dev > 17a18 > > cd0 > 20a22,30 > > cuaU0.0 > > cuaU0.0.init > > cuaU0.0.lock > > cuaU0.1 > > cuaU0.1.init > > cuaU0.1.lock > > cuaU0.2 > > cuaU0.2.init > > cuaU0.2.lock > 23a34 > > da0 > 43a55,56 > > pass0 > > pass1 > 51a65,73 > > ttyU0.0 > > ttyU0.0.init > > ttyU0.0.lock > > ttyU0.1 > > ttyU0.1.init > > ttyU0.1.lock > > ttyU0.2 > > ttyU0.2.init > > ttyU0.2.lock > 77a100 > > ugen4.2 > --- > > I would be very gratefull if You could help me to configure ppp.conf. The ttyU* and cuaU* devices obviously belong to the modem. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
How to configure ppp connection
Hello! (First of all - forgive me my language, I'am form Poland) I'am new in FreeBSD, but I have used Linux for a few year. I have got mobile modem: Huawei e1750c. As far as I know it is supported by u3g driver. On Linux I use wvdial as a dialer, and there are no problems with connection. On FreeBSD I just can't find propper ppp.conf, however I spend many hours googling and trying some. --- There are data needed to establish connection: ASP: "internet" user: "" password: "" phone: *99# --- my wvdial (Linux) config file: Modem = /dev/ttyUSB0 Baud = 57600 Init1 = ATH Init2 = ATE1 Init3 = AT+CGDCONT=1,"IP","internet" Dial Command = ATD Phone = *99# Stupid mode = yes Username = "blank" Password = "blank" Auto DNS = yes --- There is one of ppp.conf I tried: default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuaU0.0 set speed 115200 set dial "ABORT BUSY TIMEOUT 2 \ \"\" \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\"IP\\\",\\\"internet\\\" OK \ AT+CGACT? OK-AT-OK \ AT+CGATT? OK \ AT+CGCLASS? OK \ AT+COPS? OK \ ATD*99# CONNECT" set timeout 180 enable dns set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR --- After i plug modem i got: ugen4.2: at usbus4 ugen4.2: at usbus4 (disconnected) ugen4.2: at usbus4 [b]u3g0: on usbus4 u3g0: Found 3 ports.[/b] umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 umass1: on usbus4 umass1: SCSI over Bulk-Only; quirks = 0x (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present umass1:1:1:-1: Attached to scbus1 (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error (probe0:umass-sim1:1:0:0): SCSI status: Check Condition (probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) da0 at umass-sim1 bus 1 scbus1 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present ------- when i try to use "ppp default" and then "dial" i got: # ppp default Loading /lib/libalias_cuseeme.so Loading /lib/libalias_ftp.so Loading /lib/libalias_irc.so Loading /lib/libalias_nbt.so Loading /lib/libalias_pptp.so Loading /lib/libalias_skinny.so Loading /lib/libalias_smedia.so Working in interactive mode Using interface: tun0 Warning: Bad label in /etc/ppp/ppp.conf (line 2) - missing colon Warning: Bad label in /etc/ppp/ppp.conf (line 2) - missing colon ppp ON localhost> dial Warning: deflink: /dev/cuad1: Bad file descriptor Warning: deflink: /dev/cuad0: Bad file descriptor --- Nothing happens, there is still no connection. Some device nodes are created after I plug a modem. There is diff result of listed /dev pre and post pluging: ja...@iac-deb:~$ diff /media/disk/pre_dev /media/disk/post_dev 17a18 > cd0 20a22,30 > cuaU0.0 > cuaU0.0.init > cuaU0.0.lock > cuaU0.1 > cuaU0.1.init > cuaU0.1.lock > cuaU0.2 > cuaU0.2.init > cuaU0.2.lock 23a34 > da0 43a55,56 > pass0 > pass1 51a65,73 > ttyU0.0 > ttyU0.0.init > ttyU0.0.lock > ttyU0.1 > ttyU0.1.init > ttyU0.1.lock > ttyU0.2 > ttyU0.2.init > ttyU0.2.lock 77a100 > ugen4.2 --- I would be very gratefull if You could help me to configure ppp.conf. FreeBSD without internt connection is useless for me... :( Thanks, Jakub Nowacki. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ppp problem over bluetooth
hello i am on freesd 6 , i am trying to connect to internet using my nokia phone. so far i got paired it with my pc and able to dialup to my isp, problem is i get connected for sometime and gets disconnected. i cant browse, only one dsn server gets assigned in resolv.conf, infact there must be two. this is how i do it : # /etc/rc.bluetooth start ubt0 BD_ADDR: 00:11:67:0e:04:85 Features: 0xff 0xff 0x8d 0x78 0x8 0x18 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 678 bytes Number of ACL packets: 8 Max. SCO packet size: 48 bytes Number of SCO packets: 10 # rfcomm_pppd -a BD_ADDR -c -C dun -l rfcomm-dialup my ppp.conf - default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuad1 set speed 115200 set dial "ABORT ERROR ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" ATZ OK-ATZ-OK AT+CGDCONT=1,\\\"IP\\\",\\\"airtelgprs.com\\\" OK \\dATD\\T TIMEOUT 40 CONNECT" set timeout 120 enable force-scripts enable dns accept dns enable lqr accept lqr set dial set timeout 0 rfcomm-dialup: set phone "*99***1#" set authname set authkey accept pap accept chap set timeout 300 add default HISADDR #set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 #set dial "ABORT ERROR ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \\"\"AT+CGDCONT=1,\\\"IP\\\",\\\"airtelgprs.com \\\" OK #\\dATD\\T TIMEOUT 40 CONNECT" #set dial "ABORT ERROR ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" ATZ OK-ATZ-OK AT+CGDCONT=1,\\\"IP\\\",\\\"airtelgprs.com\\\" OK \\dATD\\T TIMEOUT 40 CONNECT" # Ensure that "device" references the correct serial port # for your modem. (cuad0 = COM1, cuad1 = COM2) #PAPorCHAPpmdemand: #set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ # \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" # edit the next three lines and replace the items in caps with # the values which have been assigned by your ISP. my ppp.log Aug 25 21:00:51 ppp[787]: Phase: Using interface: tun0 Aug 25 21:00:51 ppp[787]: Phase: deflink: Created in closed state Aug 25 21:00:51 ppp[787]: tun0: Command: default: ident user-ppp VERSION (built COMPILATIONDATE) Aug 25 21:00:51 ppp[787]: tun0: Command: default: set device /dev/cuad1 Aug 25 21:00:51 ppp[787]: tun0: Command: default: set speed 115200 Aug 25 21:00:51 ppp[787]: tun0: Command: default: set dial ABORT ERROR ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5"" AT+CGDCONT=1,\"IP\",\"airtelgprs.com\" OK \dATD\T TIMEOUT 40 CONNECT Aug 25 21:00:51 ppp[787]: tun0: Command: default: set timeout 120 Aug 25 21:00:51 ppp[787]: tun0: Command: default: enable force-scripts Aug 25 21:00:51 ppp[787]: tun0: Command: default: enable dns Aug 25 21:00:51 ppp[787]: tun0: Command: default: enable lqr Aug 25 21:00:51 ppp[787]: tun0: Command: default: accept lqr Aug 25 21:00:51 ppp[787]: tun0: Command: default: set dial Aug 25 21:00:51 ppp[787]: tun0: Command: default: set timeout 0 Aug 25 21:00:51 ppp[787]: tun0: Command: default: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: set phone *99***1# Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: set authname Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: set authkey Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: accept pap Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: accept chap Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: set timeout 300 Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: add default HISADDR Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: resolv rewrite Aug 25 21:00:51 ppp[787]: tun0: IPCP: Primary nameserver set to xxx.xx.250.6 Aug 25 21:00:51 ppp[787]: tun0: Command: rfcomm-dialup: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 Aug 25 21:00:51 ppp[787]: tun0: Phase: PPP Started (direct mode). Aug 25 21:00:51 ppp[787]: tun0: Phase: bundle: Establish Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: closed -> opening Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: Connected! Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: opening -> dial Aug 25 21:00:51 ppp[787]: tun0: Chat: deflink: Dial attempt 1 of 1 Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: dial -> carrier Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: carrier -> login Aug 25 21:00:51 ppp[787]: tun0: Phase: deflink: login -> lcp Aug 25 21:00:51 ppp[787]: tun0: LCP: FSM: Using "deflink" as a transport Aug 25 21:00:51 ppp[787]: tun0: LCP: deflink: State change Initial --> Closed Aug 25 21:00:51 ppp[787]: tun0: LCP: deflink: State change Closed --> Stopped Aug 25 21:00:52 ppp[787]: tun0: LCP: deflink: LayerStart Aug 25 21:00:52 ppp[787]: tun0: LCP: deflink: SendConfigReq(1)
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
Thank you Ruben :-) :-) I wouldn't have thought in a million years that could be the issue, but what you have said makes perfect sense. Looks like its back to /bin/sh for root. Cheers, Alex. Ruben de Groot wrote: On Fri, Aug 14, 2009 at 10:08:48PM +1000, Alex R typed: Actually I did change the root shell to bash. U think that might cause it? Definately. before ldconfig is run, only the system libraries in /lib and /usr/lib are known. Doing a "su -m root" at that time, as /etc/rc.d/ppp is doing, will result in the error message you got, as bash wants to load libintl.so.8, which lives in /usr/local/lib. Ruben Ruben de Groot wrote: On Fri, Aug 14, 2009 at 09:49:48PM +1000, Alex R typed: Hi Ruben, Output is as follows: /usr/bin/su: libutil.so.7 => /lib/libutil.so.7 (0x800635000) libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) libc.so.7 => /lib/libc.so.7 (0x800962000) That's normal. Shall I take a guess? You changed root's shell to bash! bash uses libintl, and will be invoked by the "su -m $ppp_user" in /etc/rc.d/ppp Yet another good reason not to change root's default shell :D cheers, Ruben Ruben de Groot wrote: On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: Hi Guys, I ran into the same problem as this person did (see the link below): http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html ppp starts fine if invoked from shell prompt, however the problem above occurs for me when I attempt to start it automatically at boot via /etc/rc.conf Funnily enough, the solution presented in that article seems to fix the issue.. But why? This problem is very easy to reproduce, how could it have been overlooked? I just happened to find the article in the link above, out of desperation, it's not good that I had to Google for a solution. What's the output of the command ldd `which su` ? Is the solution given "safe"? Should I open a PR? Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
On Fri, Aug 14, 2009 at 10:08:48PM +1000, Alex R typed: > Actually I did change the root shell to bash. U think that might cause it? Definately. before ldconfig is run, only the system libraries in /lib and /usr/lib are known. Doing a "su -m root" at that time, as /etc/rc.d/ppp is doing, will result in the error message you got, as bash wants to load libintl.so.8, which lives in /usr/local/lib. Ruben > Ruben de Groot wrote: > >On Fri, Aug 14, 2009 at 09:49:48PM +1000, Alex R typed: > > > >>Hi Ruben, > >> > >>Output is as follows: > >> > >>/usr/bin/su: > >> libutil.so.7 => /lib/libutil.so.7 (0x800635000) > >> libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) > >> libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) > >> libc.so.7 => /lib/libc.so.7 (0x800962000) > >> > > > >That's normal. Shall I take a guess? > > > >You changed root's shell to bash! > >bash uses libintl, and will be invoked by the "su -m $ppp_user" in > >/etc/rc.d/ppp > > > >Yet another good reason not to change root's default shell :D > > > >cheers, > >Ruben > > > > > >>Ruben de Groot wrote: > >> > >>>On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: > >>> > >>> > >>>>Hi Guys, > >>>> > >>>>I ran into the same problem as this person did (see the link below): > >>>> > >>>>http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html > >>>> > >>>>ppp starts fine if invoked from shell prompt, however the problem above > >>>>occurs for me when I attempt to start it automatically at boot via > >>>>/etc/rc.conf > >>>> > >>>>Funnily enough, the solution presented in that article seems to fix the > >>>>issue.. But why? This problem is very easy to reproduce, how could it > >>>>have been overlooked? I just happened to find the article in the link > >>>>above, out of desperation, it's not good that I had to Google for a > >>>>solution. > >>>> > >>>> > >>>What's the output of the command > >>> > >>>ldd `which su` > >>> > >>>? > >>> > >>> > >>> > >>>>Is the solution given "safe"? Should I open a PR? > >>>> > >>>>Alex > >>>> > >>>>___ > >>>>freebsd-questions@freebsd.org mailing list > >>>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>>>To unsubscribe, send any mail to > >>>>"freebsd-questions-unsubscr...@freebsd.org" > >>>> > >>>> > >>> > >>> > >>___ > >>freebsd-questions@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>To unsubscribe, send any mail to > >>"freebsd-questions-unsubscr...@freebsd.org" > >> > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
Actually I did change the root shell to bash. U think that might cause it? Ruben de Groot wrote: On Fri, Aug 14, 2009 at 09:49:48PM +1000, Alex R typed: Hi Ruben, Output is as follows: /usr/bin/su: libutil.so.7 => /lib/libutil.so.7 (0x800635000) libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) libc.so.7 => /lib/libc.so.7 (0x800962000) That's normal. Shall I take a guess? You changed root's shell to bash! bash uses libintl, and will be invoked by the "su -m $ppp_user" in /etc/rc.d/ppp Yet another good reason not to change root's default shell :D cheers, Ruben Ruben de Groot wrote: On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: Hi Guys, I ran into the same problem as this person did (see the link below): http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html ppp starts fine if invoked from shell prompt, however the problem above occurs for me when I attempt to start it automatically at boot via /etc/rc.conf Funnily enough, the solution presented in that article seems to fix the issue.. But why? This problem is very easy to reproduce, how could it have been overlooked? I just happened to find the article in the link above, out of desperation, it's not good that I had to Google for a solution. What's the output of the command ldd `which su` ? Is the solution given "safe"? Should I open a PR? Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
On Fri, Aug 14, 2009 at 09:49:48PM +1000, Alex R typed: > Hi Ruben, > > Output is as follows: > > /usr/bin/su: >libutil.so.7 => /lib/libutil.so.7 (0x800635000) >libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) >libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) >libc.so.7 => /lib/libc.so.7 (0x800962000) That's normal. Shall I take a guess? You changed root's shell to bash! bash uses libintl, and will be invoked by the "su -m $ppp_user" in /etc/rc.d/ppp Yet another good reason not to change root's default shell :D cheers, Ruben > Ruben de Groot wrote: > >On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: > > > >>Hi Guys, > >> > >>I ran into the same problem as this person did (see the link below): > >> > >>http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html > >> > >>ppp starts fine if invoked from shell prompt, however the problem above > >>occurs for me when I attempt to start it automatically at boot via > >>/etc/rc.conf > >> > >>Funnily enough, the solution presented in that article seems to fix the > >>issue.. But why? This problem is very easy to reproduce, how could it > >>have been overlooked? I just happened to find the article in the link > >>above, out of desperation, it's not good that I had to Google for a > >>solution. > >> > > > >What's the output of the command > > > >ldd `which su` > > > >? > > > > > >>Is the solution given "safe"? Should I open a PR? > >> > >>Alex > >> > >>___ > >>freebsd-questions@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>To unsubscribe, send any mail to > >>"freebsd-questions-unsubscr...@freebsd.org" > >> > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
There are also some interesting responses in comp.unix.bsd.freebsd.misc about this (I opened a thread there too). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
Hi Ruben, Output is as follows: /usr/bin/su: libutil.so.7 => /lib/libutil.so.7 (0x800635000) libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) libc.so.7 => /lib/libc.so.7 (0x800962000) Ruben de Groot wrote: On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: Hi Guys, I ran into the same problem as this person did (see the link below): http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html ppp starts fine if invoked from shell prompt, however the problem above occurs for me when I attempt to start it automatically at boot via /etc/rc.conf Funnily enough, the solution presented in that article seems to fix the issue.. But why? This problem is very easy to reproduce, how could it have been overlooked? I just happened to find the article in the link above, out of desperation, it's not good that I had to Google for a solution. What's the output of the command ldd `which su` ? Is the solution given "safe"? Should I open a PR? Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Userland PPP fails to load via rc.conf (7.2/amd64)
On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: > Hi Guys, > > I ran into the same problem as this person did (see the link below): > > http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html > > ppp starts fine if invoked from shell prompt, however the problem above > occurs for me when I attempt to start it automatically at boot via > /etc/rc.conf > > Funnily enough, the solution presented in that article seems to fix the > issue.. But why? This problem is very easy to reproduce, how could it > have been overlooked? I just happened to find the article in the link > above, out of desperation, it's not good that I had to Google for a > solution. What's the output of the command ldd `which su` ? > Is the solution given "safe"? Should I open a PR? > > Alex > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Userland PPP fails to load via rc.conf (7.2/amd64)
Hi Guys, I ran into the same problem as this person did (see the link below): http://www.mail-archive.com/freebsd-...@freebsd.org/msg24337.html ppp starts fine if invoked from shell prompt, however the problem above occurs for me when I attempt to start it automatically at boot via /etc/rc.conf Funnily enough, the solution presented in that article seems to fix the issue.. But why? This problem is very easy to reproduce, how could it have been overlooked? I just happened to find the article in the link above, out of desperation, it's not good that I had to Google for a solution. Is the solution given "safe"? Should I open a PR? Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: about using ppp over ethernet
Yavuz Maşlak wrote: I have a adsl modem. I am going to use freebsd as a router and firewall. ... What am I doing wrong? It is probably the firewall, it seems that you use firewall_type="closed". Could give us some more info about it? Which firewall do you use? what are your custom rules? You can read more about the firewalls available in FreeBSD from relevant section of the handbook: http://www.freebsd.org/doc/en/books/handbook/firewalls.html Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
about using ppp over ethernet
I use freebsd7.1 I have a adsl modem. I am going to use freebsd as a router and firewall. I wish to use over pppoe. I set the adsl modem as a bridge mode. I configured ppp.conf on freebsd. When I try to connect to internet using ADSL, But I get an error as below; Freebsd can't ping at any outside ip. Therefore I am not able to reach to internet in this way. What am I doing wrong? Any advice ? Thanks May 21 17:35:54 gw110 ppp[1215]: tun0: Phase: bundle: Establish May 21 17:35:54 gw110 ppp[1215]: tun0: Phase: deflink: closed -> opening May 21 17:35:54 gw110 ppp[1215]: tun0: Phase: deflink: Connected! May 21 17:35:54 gw110 ppp[1215]: tun0: Phase: deflink: opening -> dial May 21 17:35:54 gw110 ppp[1215]: tun0: Phase: deflink: dial -> carrier May 21 17:35:55 gw110 ppp[1215]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook "SE-ATAKOY-NEC-1") May 21 17:35:55 gw110 ppp[1215]: tun0: Phase: Received NGM_PPPOE_SESSIONID May 21 17:35:55 gw110 ppp[1215]: tun0: Phase: Received NGM_PPPOE_SUCCESS May 21 17:35:55 gw110 ppp[1215]: tun0: Phase: deflink: carrier -> login May 21 17:35:55 gw110 ppp[1215]: tun0: Phase: deflink: login -> lcp May 21 17:35:56 gw110 ppp[1215]: tun0: Phase: bundle: Authenticate May 21 17:35:56 gw110 ppp[1215]: tun0: Phase: deflink: his = PAP, mine = none May 21 17:35:56 gw110 ppp[1215]: tun0: Phase: Pap Output: x...@ttnet ******** May 21 17:35:57 gw110 ppp[1215]: tun0: Phase: Pap Input: SUCCESS () May 21 17:35:57 gw110 ppp[1215]: tun0: Phase: deflink: lcp -> open May 21 17:35:57 gw110 ppp[1215]: tun0: Phase: bundle: Network May 21 17:35:57 gw110 ppp[1215]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process May 21 17:35:57 gw110 ppp[1215]: tun0: Warning: ff02:7::/32: Change route failed: errno: Network is unreachable cat /etc/rc.conf gw110# ifconfig xl0: flags=8843 metric 0 mtu 1500 options=8 ether 00:60:97:b8:77:eb media: Ethernet autoselect (100baseTX ) status: active stge0: flags=8843 metric 0 mtu 1500 options=209b ether 00:22:15:10:73:04 inet 10.11.1.221 netmask 0xff00 broadcast 10.11.1.255 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=108810 metric 0 mtu 1500 pflog0: flags=0<> metric 0 mtu 33204 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 tun0: flags=8051 metric 0 mtu 1492 inet 88.238.76.207 --> 88.238.64.1 netmask 0x Opened by PID 1215 tun1: flags=8010 metric 0 mtu 1500 gw110# ping 88.238.76.207 PING 88.238.76.207 (88.238.76.207): 56 data bytes 64 bytes from 88.238.76.207: icmp_seq=0 ttl=64 time=0.831 ms 64 bytes from 88.238.76.207: icmp_seq=1 ttl=64 time=0.222 ms 64 bytes from 88.238.76.207: icmp_seq=2 ttl=64 time=0.206 ms Bu elektronik posta ve varsa ekleri tamamen gizli ve gönderilen kişiler listesine özeldir. Eğer adınız gönderilen kişiler listesinde yer almıyorsa, lütfen derhal gönderen kişiyi bilgilendiriniz ve içeriğini herhangi başka bir kişiye iletmeyiniz, herhangi bir amaç için kullanmayınız, sayısal ve basılı ortamlar dahil olmak üzere saklamayınız ve kopyalamayınız. This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by reply e-mail and delete all copies of this message and attachments. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Passing ppp/vpn with ip-filter
Hi: I have the following setup: XP -- FBSD -- Ineternet --- Work I need to setup a VPN connection from my work station to work but the connection failes, presumably blocked by my firewall. The FBSD gateway use ip filter to filter traffic with a default block. Listening on the pflog inteface I got this: 1. 051533 rule 97/0(match): block in on vr1: 172.16.0.127 > 217.126.X.X: GREv1, call 62316, seq 9, proto PPP (0x880b), length 37: [|ppp] How do I create a rule to pass this connection? Thanks, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem about ppp -nat
> > # ppp -background isp > > Loading /lib/libalias_cuseeme.so > > Loading /lib/libalias_ftp.so > > Loading /lib/libalias_irc.so > > Loading /lib/libalias_nbt.so > > Loading /lib/libalias_pptp.so > > Loading /lib/libalias_skinny.so > > Loading /lib/libalias_smedia.so > > I'm surprised ppp would load these unless -nat was specified somewhere? It is just ppp -background isp. > I spent about 15 years debugging user problems with dialup modems; it > can be really difficult without first knowing the modem type and it's > internal config - however that doesn't seem to be your problem here. Modem type... it is just a normal external serial modem. Internal config... I don't know I lost its manual, sorry. > That is, on connect it should then procede to authentication. There's > no sign of that. Whether failing at your end or the other is unclear; > maybe logging LCP might provide more of a clue, but I'm not sure .. I also don't know about this. > > At boot time ... > > Flush all rules. > > ipfw: unknown interface name tun0 > > ipfw: getsockopt(IP_FW_ADD): Invalid argument > > Hmm. I have rules for natd via ng0, which also doesn't exist at boot, > without any such complaints, but that's on a 5.5-STABLE box. > > > 00100 check-state > > ... > > > > After presence of tun0 (after dialing) ... > > # sh /etc/ipfw.rules > > Flush all rules. > > ipfw: ipfw_ctl invalid option 56 > > What's that about? You haven't shown the rule that produced that .. [EMAIL PROTECTED]:~# cat /etc/ipfw.rules # Define the firewall command (as in /etc/rc.firewall) for easy # reference. Helps to make it easier to read. fwcmd="/sbin/ipfw" # Define our outside interface. With userland-ppp this # defaults to tun0. Or just define ethernet device. oif="tun0" # Force a flushing of the current rules before we reload. $fwcmd -f flush # Do NAT before check-state $fwcmd nat 123 config if $oif log deny_in same_ports unreg_only reset $fwcmd add nat 123 ip4 from any to any via $oif # Check the state of all packets. $fwcmd add check-state # Allow all internal traffics, it is dangerous but just for testing. $fwcmd add allow all from any to any via fxp0 # Allow IPv6 tunneling $fwcmd add allow udp from any 3653 to any 3653 via $oif $fwcmd add allow tcp from any 3653 to any 3653 via $oif # The following line is for user-ppp. $fwcmd add allow ipv6 from any to any via gif0 # The following line is for UDP encapsulation (machine behind NAT). # $fwcmd add allow ipv6 from any to any via tun1 # Stop spoofing on the outside interface. $fwcmd add deny ip from any to any in via $oif not verrevpath # Allow all connections that we initiate, and keep their state. # but deny established connections that don't have a dynamic rule. $fwcmd add allow ip from me to any out via $oif keep-state $fwcmd add deny tcp from any to any established in via $oif # Allow all local traffic. $fwcmd add allow all from any to any via lo0 $fwcmd add deny all from any to 127.0.0.0/8 $fwcmd add deny ip from 127.0.0.0/8 to any # Allow internet users to connect to the port 21, 23 and 80. # We specifically allow connections to the ftpd, telnetd and a webserver. $fwcmd add allow tcp from any to me dst-port 21,23,80 in via $oif setup keep-state # Allow ICMP packets: remove type 8 if you don't want your host # to be pingable. $fwcmd add allow icmp from any to any via $oif icmptypes 0,3,8,11,12 # Deny and log all the rest. $fwcmd add deny log ip from any to any > > 5. Then insert these commands to /etc/ipfw.rules as the first two rules. > >/sbin/ipfw add divert natd all from any to any via tun0 > > /sbin/ipfw add pass all from any to any > >then run the ipfw script to load the new rules. > >sh /etc/ipfw.rules > > Which other rules? Please see above. > > But I just can't pass step 3, unless I unload ipdivert. > > And your ppp.conf or ppp command definitely doesn't mention -nat? Not at all. As said above only ``ppp -background isp''. /etc/rc.conf and /etc/ppp/ppp.conf do not store anything about -nat. > > Please don't suspect my system. It had just been very freshly > > installed from CDs before I tried everything. And without ipdivert > > being loaded into the kernel, I can dial and browse any sites and > > very fast with my /etc/ppp/ppp.conf. Should note a bug? > > Maybe it is. I'm out of ideas anyway, and noone else has come forward. I have been using *Unix for 7 years (2 years for linux and 5 years for FreeBSD). I haven't found such things. Even with noisy telephone line, I could always dial isp. (But link down so
Re: Problem about ppp -nat
On Sun, 30 Nov 2008, Pongthep Kulkrisada wrote: > Hi all, > > > set log phase chat connect carrier link ipcp ccp ID0 TUN command > I still can't dial using this configuration... Yes sorry, that was from a really old system, from backups. > # ppp -background isp > Loading /lib/libalias_cuseeme.so > Loading /lib/libalias_ftp.so > Loading /lib/libalias_irc.so > Loading /lib/libalias_nbt.so > Loading /lib/libalias_pptp.so > Loading /lib/libalias_skinny.so > Loading /lib/libalias_smedia.so I'm surprised ppp would load these unless -nat was specified somewhere? My newest system that used ppp is 5.5-STABLE, up till last August, but I'm not up with it on 6 or 7, still this does look rather odd to me. Perhaps someone else could confirm whether ppp always loads these libalias modules, whether intending to use them or not? > Working in background mode > Using interface: tun0 > Warning: carrier: Invalid log value > Warning: link: Invalid log value > Warning: usage: set log [local] > [+|-]all|async|cbcp|ccp|chat|command|connect|debug|dns|hdlc|id0|ipcp|lcp|lqm|phase|physical|radius|sync|tcp/ip|timer|tun... > Attempting redial > Attempting redial > Attempting redial > > I then removed ``carrier'' and ``link''. It always keeps redialing without > hearing dialing tone from the modem. So I removed ``connect'' again. The > result was still the same. Sorry again. On 5.5 I just used 'log Phase LCP IPCP CCP tun command' once everything was running smoothly, using several different modems. > > Try /dev/cuaa0. At least in the olden days, cuad0 was configured more > > for dialin rather than dialout. This may? explain the next two lines: > It keeps redialing without hearing any tone from the modem. So I > switched back to /dev/cuad0. Then dial; now I hear dialing tone from > the modem but warning message of ``Child failed (errdead)'' occured > then line dropped. And can not connect. I tried it many times. Note > that /dev/cuad0 appeared in my > /usr/share/examples/ppp/ppp.conf.sample, not /dev/cuaa0. If I > remember correctly I changed from cuaa0 to cuad0 when I upgraded from > FBSD5.4R to FBSD6.2R. Ok. I hadn't realised that ppp had changed so much. Wish someone who knows a bit more about the current situation would comment .. > [...] > Working in background mode > Using interface: tun0 > Child failed (errdead) > > >> set ctsrts off # enables software flow control > >> set accmap 000a # comments out these 2 lines for hardware flow > >> control > > Not sure why you don't want to use hardware flow control? Is this with > > a regular external modem? Anyway, I've always used ctsrts (with cuaa0). > 5 year ago, I downloaded this ppp.conf from some web site. But > anyway, I did follow your suggestion i.e. hardware flow control. It > still doesn't work as ``Child failed''. Actually I don't know so much > in this area (flow control). I only code C on *Unix. I rarely do this > kind of things e.g. system setup or configuration. And yes, it is a > regular external modem. I spent about 15 years debugging user problems with dialup modems; it can be really difficult without first knowing the modem type and it's internal config - however that doesn't seem to be your problem here. > >> add! default HISADDR # Add a (sticky) default route > >> [...] > >> add 0 0 HISADDR > > You probably don't want both those add statements. Try taking out the > > first one, and replacing the last one with the add! default HISADDR. > I changed it before dialing. > > > Unsure if you need an 'enable pap' as well, maybe default. Can't hurt. > I added it before dialing. But all failed. I think it is probably caused by > ipdivert. Well as mentioned above, if ppp is loading libalias modules also, there definitely could be some conflict there .. but I'm now out of my depth. > > Anyway, some extra logging should show you when and how it fails, if it > > still does .. > Nov 30 17:00:00 bsdhost newsyslog[960]: logfile turned over due to size>100K > Nov 30 17:00:16 bsdhost ppp[977]: Phase: Using interface: tun0 > Nov 30 17:00:16 bsdhost ppp[977]: Phase: deflink: Created in closed state > Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: ident user-ppp > VERSION (built COMPILATIONDATE) > Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set device > /dev/cuad0 > Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set speed 115200 > Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: disable p
Re: Problem about ppp -nat
Hi all,
> set log phase chat connect carrier link ipcp ccp ID0 TUN command
I still can't dial using this configuration...
# ppp -background isp
Loading /lib/libalias_cuseeme.so
Loading /lib/libalias_ftp.so
Loading /lib/libalias_irc.so
Loading /lib/libalias_nbt.so
Loading /lib/libalias_pptp.so
Loading /lib/libalias_skinny.so
Loading /lib/libalias_smedia.so
Working in background mode
Using interface: tun0
Warning: carrier: Invalid log value
Warning: link: Invalid log value
Warning: usage: set log [local]
[+|-]all|async|cbcp|ccp|chat|command|connect|debug|dns|hdlc|id0|ipcp|lcp|lqm|phase|physical|radius|sync|tcp/ip|timer|tun...
Attempting redial
Attempting redial
Attempting redial
I then removed ``carrier'' and ``link''. It always keeps redialing without
hearing dialing tone from the modem. So I removed ``connect'' again. The result
was still the same.
> Try /dev/cuaa0. At least in the olden days, cuad0 was configured more
> for dialin rather than dialout. This may? explain the next two lines:
It keeps redialing without hearing any tone from the modem. So I switched back
to /dev/cuad0. Then dial; now I hear dialing tone from the modem but warning
message of ``Child failed (errdead)'' occured then line dropped. And can not
connect. I tried it many times. Note that /dev/cuad0 appeared in my
/usr/share/examples/ppp/ppp.conf.sample, not /dev/cuaa0. If I remember
correctly I changed from cuaa0 to cuad0 when I upgraded from FBSD5.4R to
FBSD6.2R.
[...]
Working in background mode
Using interface: tun0
Child failed (errdead)
>> set ctsrts off # enables software flow control
>> set accmap 000a # comments out these 2 lines for hardware flow control
> Not sure why you don't want to use hardware flow control? Is this with
> a regular external modem? Anyway, I've always used ctsrts (with cuaa0).
5 year ago, I downloaded this ppp.conf from some web site. But anyway, I did
follow your suggestion i.e. hardware flow control. It still doesn't work as
``Child failed''. Actually I don't know so much in this area (flow control). I
only code C on *Unix. I rarely do this kind of things e.g. system setup or
configuration. And yes, it is a regular external modem.
>> add! default HISADDR # Add a (sticky) default route
>> [...]
>> add 0 0 HISADDR
> You probably don't want both those add statements. Try taking out the
> first one, and replacing the last one with the add! default HISADDR.
I changed it before dialing.
> Unsure if you need an 'enable pap' as well, maybe default. Can't hurt.
I added it before dialing. But all failed. I think it is probably caused by
ipdivert.
> Anyway, some extra logging should show you when and how it fails, if it
> still does ..
Nov 30 17:00:00 bsdhost newsyslog[960]: logfile turned over due to size>100K
Nov 30 17:00:16 bsdhost ppp[977]: Phase: Using interface: tun0
Nov 30 17:00:16 bsdhost ppp[977]: Phase: deflink: Created in closed state
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: ident user-ppp
VERSION (built COMPILATIONDATE)
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set device /dev/cuad0
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set speed 115200
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: disable pred1
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: deny pred1
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: disable lqr
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: deny lqr
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set dial ABORT BUSY
ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK \dATDT\T
TIMEOUT 180 CONNECT
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: set redial 3 20
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: default: enable dns
Nov 30 17:00:16 bsdhost ppp[977]: tun0: ID0: 0x28389e78 =
fopen("/etc/ppp/ppp.conf", "r")
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set phone 0123456789
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set authname
[EMAIL PROTECTED]
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set authkey **
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set timeout 0
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set openmode active
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: accept pap
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: enable pap
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: set ifaddr 10.0.0.1/0
10.0.0.2/0 255.255.255.0 0.0.0.0
Nov 30 17:00:16 bsdhost ppp[977]: tun0: Command: ego: add! default HISADDR
Nov 30 17:00:16 bsdhost ppp[977]: tun0: ID0: 10 = socket(17, 3, 0)
Nov 30 17:00:16 bsdhost ppp[977]: tun0: ID0: -1 = write(10, data, 140)
Nov 30 17:00:16 bsdhost ppp[978]: tun0: ID0: 0x28389e78 =
fopen("/var/run/tun0.pid&qu
Re: Problem about ppp -nat
On Wed, 26 Nov 2008, Pongthep Kulkrisada wrote: [..] > read many docs. Yesterday I decided to re-install FBSD7.0R from CDs > again. That causes late reply, I'm sorry. :-( No worries .. it's not like we were just hanging out waiting :) > I now have gateway_enable="YES" and firewall_enable="YES" in my /etc/rc.conf. > I can then dial ISP again. Then the following steps were taken. > > 1. I can ping any sites and very fast. > 2. # kldload ipfw (as I don't want to compile kernel anymore.) > 3. # kldload ipdivert I was under the impression that divert had to be built into the kernel, but perhaps kldload ipdivert works allright with 7.x. > 4. I also have ``natd8668/divert'' in my /etc/services. > 5. # natd -interface tun0 > 6. # /sbin/ipfw add 101 divert natd all from any to any via tun0 > 7. # /sbin/ipfw add 102 pass all from any to any > (Note that my first ipfw rule is 100 check-state. So steps 6 and 7 > should be considered as the first two filtering rules.) Just as an aside, as you're not using any keep-state rules: you should do NAT before a check-state, so packets match dynamic rules after NAT. > I do this way because I know from reading document that ppp must be > run before natd. I always want to dial ppp by myself so I can't put > natd in /etc/rc.conf. And doing it interactively is very easy to > detect when something goes wrong and step 1 can proof my good > connection. More specifically the interface, here tun0, must exist before using divert sockets using that interface. natd(8) says: 3. If you use the -interface option, make sure that your interface is already configured. If, for example, you wish to specify `tun0' as your interface, and you are using ppp(8) on that interface, you must make sure that you start ppp prior to starting natd. You've probably noticed that tun0 doesn't go away when you close ppp, so it's sufficient to have run ppp once before using the divert rule. In any case I doubt this'd really do any harm (apart from not working :) There's another way to bring up ppp (so creating tun0) without dialing out until you're ready; using ppp -auto, with a dial filter rule/s. See ppp(8) and the examples in /usr/share/examples/ppp/ppp.conf.sample .. maybe something like: set filter dial 00 0 icmp src eq 8 which will only dial upon seeing an outbound ping packet. You could specify some address rather than 0 0 if you want to be more specific. > After step 7 I switched to terminal, which keeping ping. > I found that ping stalled. I tried re-connect many times, now I know > that step 3 causes the problem. I have also tried putting > ipfw_load="YES" and ipdivert_load="YES" in /boot/loader.conf. The > problem persists. I'm quite sure that the module ipdivert has adverse > effect to the connection through modem. Should I say a bug?!!! Perhaps others can say if it's ok to kldload ipdivert after ipfw these days? In any case, this could mean coincidence rather than causation. You've not shown error messages from ppp.log indicating disconnection? Two things you should always check if there are problems passing traffic through an interface that's apparently 'UP': # ifconfig # make sure addresses, netmasks, etc make sense. # netstat -finet -ran # check the default and other routes make sense. > Without ipdivert I can not play NAT (I don't want to learn ``ipfw > nat'' and ``ppp -nat'' for now). This was also the major problem when 'ipfw nat' is as easy to setup as natd, using much the same semantics, and doesn't require the presence of ipdivert. I can't say whether it would get upset if tun0 was specified and didn't yet exist, but expect it'll just ignore any packets that don't match the specified interface, though I can't test that here now. Something like this should work: # ipfw nat 123 config if tun0 log deny_in same_ports unreg_only reset # ipfw add [number] nat 123 ip4 from any to any via tun0 where 123 is an arbitary number,and ip4 is more specific than 'all' nat logging is likely intense, but useful until things are working. deny_in provides some protection till your ipfw is properly setup. unreg_only means only traffic from your internal network (eg 192.168.*) is considered, not traffic from your router itself - maybe quicker. reset clears the aliasing table if your IP address on tun0 changes. You can study more about all NAT functionality in 'man 3 libalias'. > I recompiled kernel with options IPDIVERT few days ago. That caused > me unable to connect ISP. One thing I should note here, always run > ppp before natd. Last
Re: Problem about ppp -nat
On Fri, 28 Nov 2008, Pongthep Kulkrisada wrote: > Hi all, > > > I didn't touch /etc/ppp/ppp.conf, which has been working for 5 years > > since FBSD5.0R. Even if I go back to GENERIC kernel. I could not dial out > > to ISP in any ways. I didn't know what I do wrong even if > > I did read many docs. > I tried exactly what being described in the handbook. But all failed, > I still can't dial ISP. I think that posting /etc/ppp/ppp.conf may be > useful for your diagnostic. Note that this file has been used for > long time and never changed. But I've just reminded that ppp is > changed from version to version. My ppp.conf may not suit the current > version. I don't know. > > # cat /etc/ppp/ppp.conf > > default: > set log Phase Chat LCP IPCP CCP tun command Try using more logging, at least temporarily, then you should be able to see from your ppp.log just what's going on. For about 10 years I used: set log phase chat connect carrier link ipcp ccp ID0 TUN command > ident user-ppp VERSION (built COMPILATIONDATE) > > set device /dev/cuad0 Try /dev/cuaa0. At least in the olden days, cuad0 was configured more for dialin rather than dialout. This may? explain the next two lines: > set ctsrts off # enables software flow control > set accmap 000a# comments out these 2 lines for hardware flow > control Not sure why you don't want to use hardware flow control? Is this with a regular external modem? Anyway, I've always used ctsrts (with cuaa0). > set speed 115200 > disable pred1 > deny pred1 > disable lqr > deny lqr > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ > \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 180 CONNECT" > set redial 3 20 > enable dns # request DNS info (for resolv.conf) Looks ok. TIMEOUT 60 is plenty for a dialup modem, but whatever. > isp: > set phone 0123456789 > set authname [EMAIL PROTECTED] > set authkey mypassword > set timeout 0 > add! default HISADDR # Add a (sticky) default route > set openmode active > accept pap > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add 0 0 HISADDR You probably don't want both those add statements. Try taking out the first one, and replacing the last one with the add! default HISADDR. Unsure if you need an 'enable pap' as well, maybe default. Can't hurt. Anyway, some extra logging should show you when and how it fails, if it still does .. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
Hi all, > I didn't touch /etc/ppp/ppp.conf, which has been working for 5 years > since FBSD5.0R. Even if I go back to GENERIC kernel. I could not dial out > to ISP in any ways. I didn't know what I do wrong even if > I did read many docs. I tried exactly what being described in the handbook. But all failed, I still can't dial ISP. I think that posting /etc/ppp/ppp.conf may be useful for your diagnostic. Note that this file has been used for long time and never changed. But I've just reminded that ppp is changed from version to version. My ppp.conf may not suit the current version. I don't know. # cat /etc/ppp/ppp.conf default: set log Phase Chat LCP IPCP CCP tun command ident user-ppp VERSION (built COMPILATIONDATE) set device /dev/cuad0 set ctsrts off # enables software flow control set accmap 000a# comments out these 2 lines for hardware flow control set speed 115200 disable pred1 deny pred1 disable lqr deny lqr set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 180 CONNECT" set redial 3 20 enable dns # request DNS info (for resolv.conf) isp: set phone 0123456789 set authname [EMAIL PROTECTED] set authkey mypassword set timeout 0 add! default HISADDR # Add a (sticky) default route set openmode active accept pap set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add 0 0 HISADDR Thank you. Pongthep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
Hi all, Firstly many thanks to all your help! And sorry for late reply... > > With these settings, My FBSD host can NOT even dial out to ISP. :-( > > Please anybody tell me, what I do wrong here. > > > At this time I must go back to the original setting in order to dial ISP. > > And lastly I'm sorry for long questions. I didn't touch /etc/ppp/ppp.conf, which has been working for 5 years since FBSD5.0R. Even if I go back to GENERIC kernel. I could not dial out to ISP in any ways. I didn't know what I do wrong even if I did read many docs. Yesterday I decided to re-install FBSD7.0R from CDs again. That causes late reply, I'm sorry. :-( I now have gateway_enable="YES" and firewall_enable="YES" in my /etc/rc.conf. I can then dial ISP again. Then the following steps were taken. 1. I can ping any sites and very fast. 2. # kldload ipfw (as I don't want to compile kernel anymore.) 3. # kldload ipdivert 4. I also have ``natd8668/divert'' in my /etc/services. 5. # natd -interface tun0 6. # /sbin/ipfw add 101 divert natd all from any to any via tun0 7. # /sbin/ipfw add 102 pass all from any to any (Note that my first ipfw rule is 100 check-state. So steps 6 and 7 should be considered as the first two filtering rules.) I do this way because I know from reading document that ppp must be run before natd. I always want to dial ppp by myself so I can't put natd in /etc/rc.conf. And doing it interactively is very easy to detect when something goes wrong and step 1 can proof my good connection. After step 7 I switched to terminal, which keeping ping. I found that ping stalled. I tried re-connect many times, now I know that step 3 causes the problem. I have also tried putting ipfw_load="YES" and ipdivert_load="YES" in /boot/loader.conf. The problem persists. I'm quite sure that the module ipdivert has adverse effect to the connection through modem. Should I say a bug?!!! Without ipdivert I can not play NAT (I don't want to learn ``ipfw nat'' and ``ppp -nat'' for now). This was also the major problem when I recompiled kernel with options IPDIVERT few days ago. That caused me unable to connect ISP. One thing I should note here, always run ppp before natd. Last time when I was on GENERIC kernel, I couldn't connect ISP because my /etc/rc.conf contained natd. So natd ran before ppp, which was run manually. That was wrong. Anyone has a clue please point me to the right direction. I would probably go back to external router gateway ``out of the box''. For now I give up and need to rest. Thank you. Pongthep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
On Sun, 23 Nov 2008 14:14:44 +0700 "Pongthep Kulkrisada" <[EMAIL PROTECTED]> wrote: > Hi All, > > Firstly, I'm sorry for late reply. For simplicity to your responses, I shall > ask question by question... > > * Manolis Kiagias ([EMAIL PROTECTED]) wrote: > > > > There are at least two ways that I know of to achieve this. One uses the > > ipfw firewall, the other the pf firewall. > > For the ipfw solution, look at the FreeBSD Handbook: > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html Since you're running FreeBSD 7 with ipfw, there's actually a third way: in-kernel NAT. See ipfw(8) searching for NAT (in caps) for the section. > 1. I heard that ppp itself has capability of NAT. It can work with the > command ppp -nat and without running natd. Please tell me whether it is > right or wrong. ipfw is the same. If natd is not used, I can't add the rule > ... > > add divert natd ip from any to any via tun0 > > to /etc/ipfw.rules. I'm confused. You're right in that if you use ppp -nat, NAT's already done by the time ipfw (or pf, ipf etc) see the packets. ppp has some simple and limited rules you might apply, but I'd have to recommend using either natd(8) or ipfw nat, and running ppp without -nat. This leaves open for you the possibility of using mpd rather than ppp, either dialup or pppoe etc. All use the same libalias(3) libraries, but both ppp -nat and natd run in userland, while ipfw nat runs in-kernel, which may not matter at dialup speeds, but will migrate easily if/when you get a faster link. > 2. And if natd is still required, what -nat argument (ppp -nat) is for? For some very simple nat setups, mostly in ye olden days :) > > This worked fine for me, although I prefer to use pf. Here is how I > > setup pf (Adjust for your interfaces as necessary) > > > > My Internet interface is rl0, setup in rc.conf as: > > > > ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0" > > > > My local interface is rl1, setup in rc.conf as: > > > > ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0" > 3. I haven't mentioned that I can't use this configuration. I have 2 > interfaces i.e. public and private LAN. But I have only one NIC card for > private LAN. I don't have NIC card for public. I'm using 56k modem to > connect the outside world. I think I can't add > > ifconfig_tun0="inet 192.168.0.100 netmask 0xff00" > > to /etc/rc.conf. If I'm wrong, please tell me. No, and you don't need to; ppp (or mpd) assigns the 'outside' IP and sets up the default route through it on connection or renegotiation, assuming your ppp.conf is setup right. I gather from your previous success with ppp that this is most likely not a problem. > I did much googling. All sites always refer 2 NIC cards being used like your > example. I do have only one NIC card + 56k serial modem (/dev/cuad0). That's fine. tun0 for ppp (or ng0 for mpd) will be configured as your outside interface, and ipfw only needs that, not its (varying) address. > > (I also have a defaultrouter setting which probably does not apply to you) > > > > I have nameserver entries in /etc/resolv.conf (or setup your own DNS > > server if you wish) > 4. I also have nameserver entries. I tried setting DNS server on my WinXP > host to both gateway (FBSD host) and DNS servers of ISP. Both don't work. Once you get the NAT right, that should work out. I think ppp will fetch nameserver addresses for you if so configured, mpd sure will, or if they're constant just use resolv.conf and have ppp leave it alone. > > Use this settings in rc.conf for pf: > > > > pf_enable="YES" > > pflog_logfile="/var/log/pflog" > > pflog_flags="" > > pf_rules="/etc/pf.conf" > > pf_flags="" > > gateway_enable="YES" > 5. I think I have equivalent setting of ipfw in /etc/rc.conf but don't work. > gateway_enable="YES" > firewall_enable="YES" > firewall_type="OPEN" > firewall_quite="YES" That's 'firewall_quiet' - I think it only gets used by the default rules in rc.firewall, unless you add a check for it in your own, to add a '-q' flag to each ipfw command, so it's not noisy on boot or reloading ipfw. > firewall_script="/etc/ipfw.rules" > firewall_logging="YES" If you've used the IPFW section in the Handbook as a guide, I suggest reconsidering that after half a dozen browses of ipfw(8), and inste
Re: Problem about ppp -nat
Hi Pongthep, Pongthep Kulkrisada wrote: Hi All, Firstly, I'm sorry for late reply. For simplicity to your responses, I shall ask question by question... * Manolis Kiagias ([EMAIL PROTECTED]) wrote: There are at least two ways that I know of to achieve this. One uses the ipfw firewall, the other the pf firewall. For the ipfw solution, look at the FreeBSD Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html 1. I heard that ppp itself has capability of NAT. It can work with the command ppp -nat and without running natd. Please tell me whether it is right or wrong. That is correct, it doesn't require natd for 'ppp -nat' Just setup your fw of choice as if the tun0 device is the external device and leave all the nat stuff completely out of it. Put any port forwarding rules you need in the ppp.conf file. ipfw is the same. If natd is not used, I can't add the rule ... Correct, you need natd if you will be using ipfw for your NAT rules. add divert natd ip from any to any via tun0 to /etc/ipfw.rules. I'm confused. 2. And if natd is still required, what -nat argument (ppp -nat) is for? natd isn't required for ppp -nat. HTH the confusion. cya Andrew This worked fine for me, although I prefer to use pf. Here is how I setup pf (Adjust for your interfaces as necessary) My Internet interface is rl0, setup in rc.conf as: ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0" My local interface is rl1, setup in rc.conf as: ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0" 3. I haven't mentioned that I can't use this configuration. I have 2 interfaces i.e. public and private LAN. But I have only one NIC card for private LAN. I don't have NIC card for public. I'm using 56k modem to connect the outside world. I think I can't add ifconfig_tun0="inet 192.168.0.100 netmask 0xff00" to /etc/rc.conf. If I'm wrong, please tell me. I did much googling. All sites always refer 2 NIC cards being used like your example. I do have only one NIC card + 56k serial modem (/dev/cuad0). (I also have a defaultrouter setting which probably does not apply to you) I have nameserver entries in /etc/resolv.conf (or setup your own DNS server if you wish) 4. I also have nameserver entries. I tried setting DNS server on my WinXP host to both gateway (FBSD host) and DNS servers of ISP. Both don't work. Use this settings in rc.conf for pf: pf_enable="YES" pflog_logfile="/var/log/pflog" pflog_flags="" pf_rules="/etc/pf.conf" pf_flags="" gateway_enable="YES" 5. I think I have equivalent setting of ipfw in /etc/rc.conf but don't work. gateway_enable="YES" firewall_enable="YES" firewall_type="OPEN" firewall_quite="YES" firewall_script="/etc/ipfw.rules" firewall_logging="YES" Run: # sysctl net.inet.ip.forwarding=1 # /etc/rc.d/routing restart Add net.inet.ip.forwarding=1 to /etc/sysctl.conf so it persists reboots 6. I recompiled my kernel. options IPFIREWALL options IPFIREWALL_FORWARD options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=120 options IPDIVERT I think it should be equivalent to sysctl setting. Add the following rule to /etc/pf.conf nat pass on rl0 from rl1:network to any -> rl0 AFAIR, if rl0 has a dynamic address, you will have to write it with parentheses, like: nat pass on rl0 from rl1:network to any -> (rl0) (Note that in /etc/pf.conf translation rules like the above, are placed above filtering rules like pass or block etc) You may have to adjust /etc/pf.conf filtering rules, assuming you have any. Restart some services # /etc/rc.d/netif restart # /etc/rc.d/routing restart # /etc/rc.d/pf restart or simply reboot, and you should be set. 7. I don't know about PF. * Fbsd1 ([EMAIL PROTECTED]) wrote: You need to run dhcp so you can assign ip address on the LAN so the down stream xp box can gain access to the public internet through your gateway freebsd box. There is a detailed step by step instructions in the install guide at www.a1poweruser.com 8. I read doc from the mentioned site. The doc does not mention anything about sharing ppp dial-up to the other host. And I'm sorry dhcp is not the point of my concern now. I only want to share internet access whether IP is static or dynamic. BTW the doc is very good anyway. I shall keep it. :-) * Polytropon ([EMAIL PROTECTED]) wrote: First of all, I made my kernel capable; significant parts: # Firewall, NAT ...blah 9. I compiled the kernel following your advice excepted NETGRAPH. I think PPPoE is not the point of concern Configuration in /etc/rc.conf goes this way: ifconfig_xl0="inet 192.168.0.1 netmask 0xff00" ifconfig_rl0="inet 192.168.1.1 netmask 0xff00 media 10baseT/UTP" 10.
Re: Problem about ppp -nat
Pongthep Kulkrisada wrote: > * Manolis Kiagias ([EMAIL PROTECTED]) wrote: > >> This worked fine for me, although I prefer to use pf. Here is how I >> setup pf (Adjust for your interfaces as necessary) >> >> My Internet interface is rl0, setup in rc.conf as: >> >> ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0" >> >> My local interface is rl1, setup in rc.conf as: >> >> ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0" >> > 3. I haven't mentioned that I can't use this configuration. I have 2 > interfaces i.e. public and private LAN. But I have only one NIC card for > private LAN. I don't have NIC card for public. I'm using 56k modem to > connect the outside world. I think I can't add > > ifconfig_tun0="inet 192.168.0.100 netmask 0xff00" > You won't of course put this in rc.conf. However AFAIK tun0 is *still* a network interface and can appear in firewall rules. So the PF method I described should work, tun0 is considered the "external" network interface, the rule would be: nat pass on tun0 from rl1:network to any -> (tun0) where rl1 would be the internal interface. Needless to say, I have no way of testing the above as I don't have a modem. Since obviously you want to use ipfw, I still suggest you go by the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html First, make sure Internet works normally on your FreeBSD host. Then apply the above instructions. The example in the handbook shows a line: natd_interface="fxp0" which in your case would be: natd_interface="tun0" It seems you already have these settings though, so I would review the Handbook instructions and remove anything else from the configuration which does not appear there. Once things are working, go back and add firewall rules etc. Handbook instructions worked for me (with two ethernet cards though) "out of the box". ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
Hi All, Firstly, I'm sorry for late reply. For simplicity to your responses, I shall ask question by question... * Manolis Kiagias ([EMAIL PROTECTED]) wrote: > > There are at least two ways that I know of to achieve this. One uses the > ipfw firewall, the other the pf firewall. > For the ipfw solution, look at the FreeBSD Handbook: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html 1. I heard that ppp itself has capability of NAT. It can work with the command ppp -nat and without running natd. Please tell me whether it is right or wrong. ipfw is the same. If natd is not used, I can't add the rule ... add divert natd ip from any to any via tun0 to /etc/ipfw.rules. I'm confused. 2. And if natd is still required, what -nat argument (ppp -nat) is for? > This worked fine for me, although I prefer to use pf. Here is how I > setup pf (Adjust for your interfaces as necessary) > > My Internet interface is rl0, setup in rc.conf as: > > ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0" > > My local interface is rl1, setup in rc.conf as: > > ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0" 3. I haven't mentioned that I can't use this configuration. I have 2 interfaces i.e. public and private LAN. But I have only one NIC card for private LAN. I don't have NIC card for public. I'm using 56k modem to connect the outside world. I think I can't add ifconfig_tun0="inet 192.168.0.100 netmask 0xff00" to /etc/rc.conf. If I'm wrong, please tell me. I did much googling. All sites always refer 2 NIC cards being used like your example. I do have only one NIC card + 56k serial modem (/dev/cuad0). > (I also have a defaultrouter setting which probably does not apply to you) > > I have nameserver entries in /etc/resolv.conf (or setup your own DNS > server if you wish) 4. I also have nameserver entries. I tried setting DNS server on my WinXP host to both gateway (FBSD host) and DNS servers of ISP. Both don't work. > Use this settings in rc.conf for pf: > > pf_enable="YES" > pflog_logfile="/var/log/pflog" > pflog_flags="" > pf_rules="/etc/pf.conf" > pf_flags="" > gateway_enable="YES" 5. I think I have equivalent setting of ipfw in /etc/rc.conf but don't work. gateway_enable="YES" firewall_enable="YES" firewall_type="OPEN" firewall_quite="YES" firewall_script="/etc/ipfw.rules" firewall_logging="YES" > Run: > # sysctl net.inet.ip.forwarding=1 > # /etc/rc.d/routing restart > > Add net.inet.ip.forwarding=1 to /etc/sysctl.conf so it persists reboots 6. I recompiled my kernel. options IPFIREWALL options IPFIREWALL_FORWARD options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=120 options IPDIVERT I think it should be equivalent to sysctl setting. > Add the following rule to /etc/pf.conf > > nat pass on rl0 from rl1:network to any -> rl0 > > AFAIR, if rl0 has a dynamic address, you will have to write it with > parentheses, like: > > nat pass on rl0 from rl1:network to any -> (rl0) > (Note that in /etc/pf.conf translation rules like the above, are placed > above filtering rules like pass or block etc) > You may have to adjust /etc/pf.conf filtering rules, assuming you have any. > > Restart some services > > # /etc/rc.d/netif restart > # /etc/rc.d/routing restart > # /etc/rc.d/pf restart > > or simply reboot, and you should be set. 7. I don't know about PF. * Fbsd1 ([EMAIL PROTECTED]) wrote: > You need to run dhcp so you can assign ip address on the LAN so the down > stream xp box can gain access to the public internet through your > gateway freebsd box. There is a detailed step by step instructions in > the install guide at www.a1poweruser.com 8. I read doc from the mentioned site. The doc does not mention anything about sharing ppp dial-up to the other host. And I'm sorry dhcp is not the point of my concern now. I only want to share internet access whether IP is static or dynamic. BTW the doc is very good anyway. I shall keep it. :-) * Polytropon ([EMAIL PROTECTED]) wrote: > First of all, I made my kernel capable; significant parts: > # Firewall, NAT > ...blah 9. I compiled the kernel following your advice excepted NETGRAPH. I think PPPoE is not the point of concern > Configuration in /etc/rc.conf goes this way: >ifconfig_xl0="inet 192.168.0.1 netmask 0xff00" >ifconfig_rl0="inet 192.168.1.1 netmask 0xff00 media 10baseT/UTP" 10. As said earlier, my interface connecting to outside are 56k serial modem (/dev/cuad0). I think I can't set /dev/cuad0 (or even tun0) in this way. 11. CONCLUSION: I did rea
Re: Problem about ppp -nat
Allthough others have already given you good advice, I'd like to add that I'm running here at a similar setting, but without any of these "Windows". :-) First of all, I made my kernel capable; significant parts: # Firewall, NAT options DUMMYNET options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=500 options IPFILTER options IPDIVERT # PPPoE: netgraph(4) system options NETGRAPH options NETGRAPH_ETHER options NETGRAPH_SOCKET options NETGRAPH_PPPOE If you don't want to compile a custom kernel, it's no problem. As far as I know, the required kernel modules will be loaded automatically. My setting includes two network interfaces, just like yours. Interface xl0 + tun0 is the PPPoE connection to the outside, while interface rl0 is the connection to the (slow) switch where the "clients" are connected. Configuration in /etc/rc.conf goes this way: ifconfig_xl0="inet 192.168.0.1 netmask 0xff00" ifconfig_rl0="inet 192.168.1.1 netmask 0xff00 media 10baseT/UTP" firewall_enable="YES" firewall_type="/etc/ipfw.conf" gateway_enable="YES" named_enable="YES" natd_enable="YES" natd_interface="xl0" ppp_enable="YES" ppp_profile="mydslprovider" ppp_mode="ddial" ppp_nat="YES" The connection is established via /etc/ppp/ppp.conf settings. Then I use a DHCP server to assign IPs to the "clients" instead of giving them fixed ones. In fact, they are fixed because I set up isc-dhcpd3-server (from ports) to assign IPs according to the respective MAC adresses. :-) Important note to IPFW settings: Have the line add divert natd ip from any to any via xl0 in your /etc/ipfw.conf. If you need to, you can add flags for natd in order to have a certain kind of port or address redirection, such as natd_flags="-redirect_port tcp 192.168.1.5:23 " or natd_flags="-redirect_address 192.168.1.2 123.456.789.123 \ -redirect_address 192.168.1.5 123.456.789.123" In any case, go and check your "Windows" the usual way. Don't forget to do it, instead you'll end up searching for an error on the correctly working FreeBSD installation. :-) Check if the "Windows" has got the correct IP, if the name server settings are correct and if you can (1st) ping the gateway machine and (2nd) something outside the gateway machine. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
Pongthep Kulkrisada wrote: Hi All, I have just subscribed to freebsd-questions and I have a question about ppp -nat. I have 2 computers. One is running FreeBSD-7.0R, the other is running WinXP. The host running FBSD7.0R has been connecting to the outside world using user-ppp without any problem for very long. Now I want to share internet access to the other host behind NAT through this FBSD host. My FBSD machine has 2 interfaces i.e. tun0 (connecting to ISP) with dynamic IP (of course) fxp0 (for internal LAN) with static IP of 192.168.1.10 My WinXP machine has 1 interface (internal LAN) with static IP of 192.168.1.11 Previously I have a router acting as a gateway for all machines behind NAT. But now I want FBSD machine to work as a gateway. I have never done this before. I tried some googling with reading ppp(8) and ipfw(8). And I tried masquerading but it didn't work. I have plenty configuration files. But the relevant configurations are listed here. /etc/rc.conf # enable IP forwarding gateway_enable="YES" # previously I ran web-server, just disable it or comment it out, not sure why! #apache_enable="YES" On the host running WinXP, I set its gateway and DNS server to the IP of ppp host i.e. 192.168.1.10. I then inserted the following line as the first rule in /etc/ipfw.rules. /sbin/ipfw add allow all from any to any via fxp0 (I know this rule is dangerous, but just for testing.) I then issue the ppp command. [EMAIL PROTECTED]:~# ppp -background -nat myisp FBSD host (running ppp) can access anywhere but WinXP host can't. I learned from some site explaining that ppp itself has the capability of IP masquerading. And it does not require natd(8). So I don't mention about natd here. Anyone have a clue or who have done the correct configurations, please point me out. Thank you in advance. Pongthep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" You need to run dhcp so you can assign ip address on the LAN so the down stream xp box can gain access to the public internet through your gateway freebsd box. There is a detailed step by step instructions in the install guide at www.a1poweruser.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem about ppp -nat
Pongthep Kulkrisada wrote: > Hi All, > > I have just subscribed to freebsd-questions and I have a question about ppp > -nat. > > I have 2 computers. One is running FreeBSD-7.0R, the other is running WinXP. > The host running FBSD7.0R has been connecting to the outside world using > user-ppp without any problem for very long. Now I want to share internet > access to the other host behind NAT through this FBSD host. > My FBSD machine has 2 interfaces i.e. > tun0 (connecting to ISP) with dynamic IP (of course) > fxp0 (for internal LAN) with static IP of 192.168.1.10 > My WinXP machine has 1 interface (internal LAN) with static IP of 192.168.1.11 > > Previously I have a router acting as a gateway for all machines behind NAT. > But now I want FBSD machine to work as a gateway. I have never done this > before. I tried some googling with reading ppp(8) and ipfw(8). And I tried > masquerading but it didn't work. I have plenty configuration files. But the > relevant configurations are listed here. > > /etc/rc.conf > # enable IP forwarding > gateway_enable="YES" > # previously I ran web-server, just disable it or comment it out, not sure > why! > #apache_enable="YES" > > On the host running WinXP, I set its gateway and DNS server to the IP of ppp > host i.e. 192.168.1.10. > > I then inserted the following line as the first rule in /etc/ipfw.rules. > /sbin/ipfw add allow all from any to any via fxp0 > (I know this rule is dangerous, but just for testing.) > > I then issue the ppp command. > [EMAIL PROTECTED]:~# ppp -background -nat myisp > > FBSD host (running ppp) can access anywhere but WinXP host can't. I learned > from some site explaining that ppp itself has the capability of IP > masquerading. And it does not require natd(8). So I don't mention about natd > here. > Anyone have a clue or who have done the correct configurations, please point > me out. > > Thank you in advance. > Pongthep > > There are at least two ways that I know of to achieve this. One uses the ipfw firewall, the other the pf firewall. For the ipfw solution, look at the FreeBSD Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html This worked fine for me, although I prefer to use pf. Here is how I setup pf (Adjust for your interfaces as necessary) My Internet interface is rl0, setup in rc.conf as: ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0" My local interface is rl1, setup in rc.conf as: ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0" (I also have a defaultrouter setting which probably does not apply to you) I have nameserver entries in /etc/resolv.conf (or setup your own DNS server if you wish) Use this settings in rc.conf for pf: pf_enable="YES" pflog_logfile="/var/log/pflog" pflog_flags="" pf_rules="/etc/pf.conf" pf_flags="" gateway_enable="YES" Run: # sysctl net.inet.ip.forwarding=1 # /etc/rc.d/routing restart Add net.inet.ip.forwarding=1 to /etc/sysctl.conf so it persists reboots Add the following rule to /etc/pf.conf nat pass on rl0 from rl1:network to any -> rl0 AFAIR, if rl0 has a dynamic address, you will have to write it with parentheses, like: nat pass on rl0 from rl1:network to any -> (rl0) (Note that in /etc/pf.conf translation rules like the above, are placed above filtering rules like pass or block etc) You may have to adjust /etc/pf.conf filtering rules, assuming you have any. Restart some services # /etc/rc.d/netif restart # /etc/rc.d/routing restart # /etc/rc.d/pf restart or simply reboot, and you should be set. Note that in your client machine, you should set gateway to point to your FreeBSD machine, but unless you are running your own DNS server, DNS entries should point to your ISP. If you combine this setup with a DHCP server from the Ports Collection, you will have pretty much a standard home router out of a FreeBSD machine. There are also other capabilities, like port forwarding and so on, but I'll let you figure them out yourself ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem about ppp -nat
Hi All, I have just subscribed to freebsd-questions and I have a question about ppp -nat. I have 2 computers. One is running FreeBSD-7.0R, the other is running WinXP. The host running FBSD7.0R has been connecting to the outside world using user-ppp without any problem for very long. Now I want to share internet access to the other host behind NAT through this FBSD host. My FBSD machine has 2 interfaces i.e. tun0 (connecting to ISP) with dynamic IP (of course) fxp0 (for internal LAN) with static IP of 192.168.1.10 My WinXP machine has 1 interface (internal LAN) with static IP of 192.168.1.11 Previously I have a router acting as a gateway for all machines behind NAT. But now I want FBSD machine to work as a gateway. I have never done this before. I tried some googling with reading ppp(8) and ipfw(8). And I tried masquerading but it didn't work. I have plenty configuration files. But the relevant configurations are listed here. /etc/rc.conf # enable IP forwarding gateway_enable="YES" # previously I ran web-server, just disable it or comment it out, not sure why! #apache_enable="YES" On the host running WinXP, I set its gateway and DNS server to the IP of ppp host i.e. 192.168.1.10. I then inserted the following line as the first rule in /etc/ipfw.rules. /sbin/ipfw add allow all from any to any via fxp0 (I know this rule is dangerous, but just for testing.) I then issue the ppp command. [EMAIL PROTECTED]:~# ppp -background -nat myisp FBSD host (running ppp) can access anywhere but WinXP host can't. I learned from some site explaining that ppp itself has the capability of IP masquerading. And it does not require natd(8). So I don't mention about natd here. Anyone have a clue or who have done the correct configurations, please point me out. Thank you in advance. Pongthep ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with reconnecting ppp (ppp -ddial isp)
cpghost wrote: On Sat, 26 Apr 2008 21:12:11 +0200 Ivan Toman [1]<[EMAIL PROTECTED]> wrote: First problem get when ISP disconnect me after 24 hours due to IP change. Link does not properly get reconnected. ppp tries to connect, and appearenty is connected, but something is wrong because no traffic is possible and after few seconds ppp goes down and reconnects again. And again and again Strange above all is that during reconnecting routing table always has default route, but ping does not go. Next, I will put some information that I think is relevant to problem, but it seems to me, not very useful in debugging this. I don't know if it's exactly the same problem, but I've had a similar problem with userland ppp and even submitted logfiles of forced disconnects. I thought the problem was with ng_pppoe, but apparently, it is with ppp(8). Unfortunately, ppp's maintainer didn't reply or chime in, and the problem is obviously still lingering there, deep inside ppp or between ppp and ng_pppoe. :( The thread started here: [2]http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038874.html You may not have hit the very same bug, but the circumstances are pretty much similar. Someone really ought to have a look at ppp. Fortunately, with the help from Alexander and Julian, I've switched to net/mpd5, and didn't encounter any problems with this 24h forced ADSL disconnect ever since (running RELENG_7 now). Just give it a try: you'll like it! I'm now using the following /usr/local/etc/mpd5/mpd.conf: Hello dear cpghost, thanks for answer! I don't know why but it seems that some messages sent to mailing list does not appear imediately (in fact, I sent yesterday one that is not even now there as reply to Patrick Lamaizière's post). In that reply I stated that i managed to use that mpd client instead of ppp and it works great! I found no case when it hangs, so for now I can tell the problem is "solved". Just, couldn't find way to configure mpd5, it seems it does not have same rules for conf file as mpd4 that I setup to work for me. Now with your example, I will probably try to upgrade to mpd5, thanks. Yes it does look to me as ppp bug, or in something closely related to ppp. If somebody want to go deeper into this I can send more findings of myself, but for me, mpd will go on from now. Thanks all! (hope message will appear on mailing list) Ivan References 1. mailto:[EMAIL PROTECTED] 2. http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038874.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with reconnecting ppp (ppp -ddial isp)
On Sat, 26 Apr 2008 21:12:11 +0200 Ivan Toman <[EMAIL PROTECTED]> wrote: > First problem get when ISP disconnect me after 24 hours due to IP > change. Link does not properly get reconnected. ppp tries to connect, > and appearenty is connected, but something is wrong because no > traffic is possible and after few seconds ppp goes down and > reconnects again. And again and again Strange above all is that > during reconnecting routing table always has default route, but ping > does not go. Next, I will put some information that I think is > relevant to problem, but it seems to me, not very useful in debugging > this. I don't know if it's exactly the same problem, but I've had a similar problem with userland ppp and even submitted logfiles of forced disconnects. I thought the problem was with ng_pppoe, but apparently, it is with ppp(8). Unfortunately, ppp's maintainer didn't reply or chime in, and the problem is obviously still lingering there, deep inside ppp or between ppp and ng_pppoe. :( The thread started here: http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038874.html You may not have hit the very same bug, but the circumstances are pretty much similar. Someone really ought to have a look at ppp. Fortunately, with the help from Alexander and Julian, I've switched to net/mpd5, and didn't encounter any problems with this 24h forced ADSL disconnect ever since (running RELENG_7 now). Just give it a try: you'll like it! I'm now using the following /usr/local/etc/mpd5/mpd.conf: --- /usr/local/etc/mpd5/mpd.conf -- startup: # configure users set user mpd XX # configure the console set console self 127.0.0.1 5005 set console user mpd set console open # configure the web server set web self 192.168.254.1 5006 set web user mpd set web open default: load pppoe_client pppoe_client: create bundle static B1 set iface route default set iface enable nat set ipcp ranges 0.0.0.0/0 0.0.0.0/0 set ipcp disable vjcomp create link static L1 pppoe set link action bundle B1 set auth authname "" set auth password "XX" set link max-redial 0 set link mtu 1460 set link mru 1460 set link keep-alive 10 60 set link disable acfcomp set link disable protocomp set pppoe iface sis0 set pppoe service "" set log +echo open --- /usr/local/etc/mpd5/mpd.conf --- Good luck! > Ivan Toman -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp reconnecting problem
On Sun, 27 Apr 2008 04:43 pm, Ivan Toman wrote: > >Hello! >I encountered big problem after switching router from gentoo to >freebsd. It does not properly reconnect ADSL link after loosing >connection, for example, when ISP cycle IP address or when I pull out >cable from ADSL switcher for testing purporse. I cannot realize what's >going on and really need help. >First problem get when ISP disconnect me after 24 hours due to IP >change. Link does not properly get reconnected. ppp tries to connect, >and appearenty is connected, but something is wrong because no traffic > is possible and after few seconds ppp goes down and reconnects again. >And again and again Strange above all is that during reconnecting >routing table always has default route, but ping does not go. Next, I >will put some information that I think is relevant to problem, but it >seems to me, not very useful in debugging this. >During reconnecting as I describe above, this is my routing table: >[EMAIL PROTECTED] /home/coldplug]# netstat -rn >Routing tables >Internet: >Destination� � � � � � � Gateway� � � � � � � � � � � Flags� � � >Refs� � � � � Use� Netif Expire >default� � � � � � � � � � � 172.29.252.12� � � � � >UGS� � � � � � � � 1� 2284023� � tun0 >10.23.99.64/29� � � � link#1� � � � � � � � � � � � >UC� � � � � � � � � 0� � � � � � � 0� � nfe0 >10.23.99.66� � � � � � � 00:30:84:ee:3c:cf� UHLW� � � � � � � >1� � � � 4065� � nfe0� � 1030 >10.23.99.70� � � � � � � 00:02:b3:9e:b9:81� UHLW� � � � � � � 1� � >223104� � nfe0� � 1027 >127.0.0.1� � � � � � � � � 127.0.0.1� � � � � � � � � >UH� � � � � � � � � 0� � � � � � 72� � � lo0 >172.29.252.12� � � � � 78.3.33.136� � � � � � � UGH� � � � � � � � >1� � � � � � � 0� � tun0 >Internet6: >Destination� � � � � � � � � � � � � � � � � � � � � � >Gateway� � � � � � � � � � � � � � � � � � � � � � Flags� Netif >Expire >::1� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � >::1� � � � � � � � � � � � � � � � � � � � � � � � � � UHL� � � � >lo0 >fe80::%lo0/64� � � � � � � � � � � � � � � � � � � � >fe80::1%lo0� � � � � � � � � � � � � � � � � � U� � � � lo0 >fe80::1%lo0� � � � � � � � � � � � � � � � � � � � � � >link#5� � � � � � � � � � � � � � � � � � � � � � � UHL� � � � lo0 >ff01:5::/32� � � � � � � � � � � � � � � � � � � � � � >fe80::1%lo0� � � � � � � � � � � � � � � � � � UC� � � � lo0 >ff01:6::/32� � � � � � � � � � � � � � � � � � � � � � >link#6� � � � � � � � � � � � � � � � � � � � � � � UGC� � � tun0 >ff02::%lo0/32� � � � � � � � � � � � � � � � � � � � >fe80::1%lo0� � � � � � � � � � � � � � � � � � UC� � � � lo0 >ff02::%tun0/32� � � � � � � � � � � � � � � � � � � >fe80::211:9ff:fe8d:4a27%tun0� UGC� � � tun0 >[EMAIL PROTECTED] /home/coldplug]# >And this I get if try to ping ISP's dns >[EMAIL PROTECTED] /home/coldplug]# ping 195.29.150.3 >PING 195.29.150.3 (195.29.150.3): 56 data bytes >ping: sendto: No buffer space available >ping: sendto: No buffer space available >ping: sendto: No buffer space available >ping: sendto: No buffer space available >^C >--- 195.29.150.3 ping statistics --- >10 packets transmitted, 0 packets received, 100.0% packet loss >[EMAIL PROTECTED] /home/coldplug]# >No buffer space available??? What is that? >These are lines from log, where you can see that it reconnects and >never stops that >[EMAIL PROTECTED] /home/coldplug]# tail -f /var/log/ppp.log >Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: carrier -> >login > Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: login -> >lcp > Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Warning: deflink: Reducing >configured MRU from 1500 to 1492 >Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: deflink: his = PAP, > mine = none >Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: Pap Output: >[EMAIL PROTECTED] >Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: Pap Input: SUCCESS >(Access Accepted. ) >Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: Already in >NETWORK phase >Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> open > Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change > route failed: errno: No such process >Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: > Change route failed: errno: Network is unreachable >Apr 26 12:08:23 maraska-gw ppp[956]: tu
Re: ppp reconnecting problem
Le Sun, 27 Apr 2008 09:13:06 +0200, Ivan Toman <[EMAIL PROTECTED]> a __crit : > >Hello! >I encountered big problem after switching router from gentoo to >freebsd. It does not properly reconnect ADSL link after loosing >connection, for example, when ISP cycle IP address or when I pull > out cable from ADSL switcher for testing purporse. I cannot realize > what's going on and really need help. >First problem get when ISP disconnect me after 24 hours due to IP >change. Link does not properly get reconnected. ppp tries to > connect, and appearenty is connected, but something is wrong because > no traffic is possible and after few seconds ppp goes down and > reconnects again. And again and again If you kill ppp and restart it, does-it work again ? When I was runing ppp on FreeBSD i saw few times this kind of "already in network phase" You can restart ppp each day with cron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with reconnecting ppp (ppp -ddial isp)
Hello! I encountered big problem after switching router from gentoo to freebsd. It does not properly reconnect ADSL link after loosing connection, for example, when ISP cycle IP address or when I pull out cable from ADSL switcher for testing purporse. I cannot realize what's going on and really need help. First problem get when ISP disconnect me after 24 hours due to IP change. Link does not properly get reconnected. ppp tries to connect, and appearenty is connected, but something is wrong because no traffic is possible and after few seconds ppp goes down and reconnects again. And again and again Strange above all is that during reconnecting routing table always has default route, but ping does not go. Next, I will put some information that I think is relevant to problem, but it seems to me, not very useful in debugging this. During reconnecting as I describe above, this is my routing table: [EMAIL PROTECTED] /home/coldplug]# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.29.252.12 UGS 1 2284023 tun0 10.23.99.64/29 link#1 UC 00 nfe0 10.23.99.6600:30:84:ee:3c:cf UHLW1 4065 nfe0 1030 10.23.99.7000:02:b3:9e:b9:81 UHLW1 223104 nfe0 1027 127.0.0.1 127.0.0.1 UH 0 72lo0 172.29.252.12 78.3.33.136UGH 10 tun0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#5UHL lo0 ff01:5::/32 fe80::1%lo0 UC lo0 ff01:6::/32 link#6UGCtun0 ff02::%lo0/32 fe80::1%lo0 UC lo0 ff02::%tun0/32fe80::211:9ff:fe8d:4a27%tun0 UGCtun0 [EMAIL PROTECTED] /home/coldplug]# And this I get if try to ping ISP's dns [EMAIL PROTECTED] /home/coldplug]# ping 195.29.150.3 PING 195.29.150.3 (195.29.150.3): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- 195.29.150.3 ping statistics --- 10 packets transmitted, 0 packets received, 100.0% packet loss [EMAIL PROTECTED] /home/coldplug]# No buffer space available??? What is that? These are lines from log, where you can see that it reconnects and never stops that [EMAIL PROTECTED] /home/coldplug]# tail -f /var/log/ppp.log Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: carrier -> login Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: login -> lcp Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492 Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: deflink: his = PAP, mine = none Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: Pap Output: [EMAIL PROTECTED] Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: Pap Input: SUCCESS (Access Accepted. ) Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: Already in NETWORK phase Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> open Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Phase: deflink: open -> lcp Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: Received NGM_PPPOE_CLOSE Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Device disconnected Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Disconnected! Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> logout Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Disconnected! Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: logout -> hangup Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Connect time: 123 secs: 374 octets in, 96 octets out Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: 3218212 packets in, 2284164 packets out Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: total 3 bytes/sec, peak 40 bytes/sec on Sat Apr 26 12:06:24 2008 Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: hangup -> opening Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Enter pause (3) for redialing. Apr 26 12:08:27 m
ppp reconnecting problem (try #2)
Hello. My first e-mail seems very messed up, so I will try again. Sorry about that, I hope this will be OK. I encountered big problem after switching router from gentoo to freebsd. It does not properly reconnect ADSL link after loosing connection, for example, when ISP cycle IP address or when I pull out cable from ADSL switcher for testing purporse. I cannot realize what's going on and really need help. First problem get when ISP disconnect me after 24 hours due to IP change. Link does not properly get reconnected. ppp tries to connect, and appearenty is connected, but something is wrong because no traffic is possible and after few seconds ppp goes down and reconnects again. And again and again Strange above all is that during reconnecting routing table always has default route, but ping does not go. Next, I will put some information that I think is relevant to problem, but it seems to me, not very useful in debugging this. During reconnecting as I describe above, this is my routing table: [EMAIL PROTECTED] /home/coldplug]# netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default172.29.252.12 UGS 1 2284023 tun0 10.23.99.64/29 link#1 UC 00 nfe0 10.23.99.6600:30:84:ee:3c:cf UHLW1 4065 nfe0 1030 10.23.99.7000:02:b3:9e:b9:81 UHLW1 223104 nfe0 1027 127.0.0.1 127.0.0.1 UH 0 72lo0 172.29.252.12 78.3.33.136UGH 10 tun0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#5UHL lo0 ff01:5::/32 fe80::1%lo0 UC lo0 ff01:6::/32 link#6UGCtun0 ff02::%lo0/32 fe80::1%lo0 UC lo0 ff02::%tun0/32fe80::211:9ff:fe8d:4a27%tun0 UGCtun0 [EMAIL PROTECTED] /home/coldplug]# And this I get if try to ping ISP's dns [EMAIL PROTECTED] /home/coldplug]# ping 195.29.150.3 PING 195.29.150.3 (195.29.150.3): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- 195.29.150.3 ping statistics --- 10 packets transmitted, 0 packets received, 100.0% packet loss [EMAIL PROTECTED] /home/coldplug]# No buffer space available??? What is that? These are lines from log, where you can see that it reconnects and never stops that [EMAIL PROTECTED] /home/coldplug]# tail -f /var/log/ppp.log Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: carrier -> login Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: login -> lcp Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492 Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: deflink: his = PAP, mine = none Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: Pap Output: [EMAIL PROTECTED] Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: Pap Input: SUCCESS (Access Accepted. ) Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: Already in NETWORK phase Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> open Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Phase: deflink: open -> lcp Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: Received NGM_PPPOE_CLOSE Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Device disconnected Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Disconnected! Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> logout Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Disconnected! Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: logout -> hangup Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Connect time: 123 secs: 374 octets in, 96 octets out Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: 3218212 packets in, 2284164 packets out Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: total 3 bytes/sec, peak 40 bytes/sec on Sat Apr 26 12:06:24 2008 Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: hangup -> opening Apr 26 12:
ppp reconnecting problem
Hello! I encountered big problem after switching router from gentoo to freebsd. It does not properly reconnect ADSL link after loosing connection, for example, when ISP cycle IP address or when I pull out cable from ADSL switcher for testing purporse. I cannot realize what's going on and really need help. First problem get when ISP disconnect me after 24 hours due to IP change. Link does not properly get reconnected. ppp tries to connect, and appearenty is connected, but something is wrong because no traffic is possible and after few seconds ppp goes down and reconnects again. And again and again Strange above all is that during reconnecting routing table always has default route, but ping does not go. Next, I will put some information that I think is relevant to problem, but it seems to me, not very useful in debugging this. During reconnecting as I describe above, this is my routing table: [EMAIL PROTECTED] /home/coldplug]# netstat -rn Routing tables Internet: Destination� � � � � � � Gateway� � � � � � � � � � � Flags� � � Refs� � � � � Use� Netif Expire default� � � � � � � � � � � 172.29.252.12� � � � � UGS� � � � � � � � 1� 2284023� � tun0 10.23.99.64/29� � � � link#1� � � � � � � � � � � � UC� � � � � � � � � 0� � � � � � � 0� � nfe0 10.23.99.66� � � � � � � 00:30:84:ee:3c:cf� UHLW� � � � � � � 1� � � � 4065� � nfe0� � 1030 10.23.99.70� � � � � � � 00:02:b3:9e:b9:81� UHLW� � � � � � � 1� � 223104� � nfe0� � 1027 127.0.0.1� � � � � � � � � 127.0.0.1� � � � � � � � � UH� � � � � � � � � 0� � � � � � 72� � � lo0 172.29.252.12� � � � � 78.3.33.136� � � � � � � UGH� � � � � � � � 1� � � � � � � 0� � tun0 Internet6: Destination� � � � � � � � � � � � � � � � � � � � � � Gateway� � � � � � � � � � � � � � � � � � � � � � Flags� Netif Expire ::1� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � ::1� � � � � � � � � � � � � � � � � � � � � � � � � � UHL� � � � lo0 fe80::%lo0/64� � � � � � � � � � � � � � � � � � � � fe80::1%lo0� � � � � � � � � � � � � � � � � � U� � � � lo0 fe80::1%lo0� � � � � � � � � � � � � � � � � � � � � � link#5� � � � � � � � � � � � � � � � � � � � � � � UHL� � � � lo0 ff01:5::/32� � � � � � � � � � � � � � � � � � � � � � fe80::1%lo0� � � � � � � � � � � � � � � � � � UC� � � � lo0 ff01:6::/32� � � � � � � � � � � � � � � � � � � � � � link#6� � � � � � � � � � � � � � � � � � � � � � � UGC� � � tun0 ff02::%lo0/32� � � � � � � � � � � � � � � � � � � � fe80::1%lo0� � � � � � � � � � � � � � � � � � UC� � � � lo0 ff02::%tun0/32� � � � � � � � � � � � � � � � � � � fe80::211:9ff:fe8d:4a27%tun0� UGC� � � tun0 [EMAIL PROTECTED] /home/coldplug]# And this I get if try to ping ISP's dns [EMAIL PROTECTED] /home/coldplug]# ping 195.29.150.3 PING 195.29.150.3 (195.29.150.3): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- 195.29.150.3 ping statistics --- 10 packets transmitted, 0 packets received, 100.0% packet loss [EMAIL PROTECTED] /home/coldplug]# No buffer space available??? What is that? These are lines from log, where you can see that it reconnects and never stops that [EMAIL PROTECTED] /home/coldplug]# tail -f /var/log/ppp.log Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: carrier -> login Apr 26 12:06:22 maraska-gw ppp[956]: tun0: Phase: deflink: login -> lcp Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492 Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: deflink: his = PAP, mine = none Apr 26 12:06:23 maraska-gw ppp[956]: tun0: Phase: Pap Output: [EMAIL PROTECTED] Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: Pap Input: SUCCESS (Access Accepted. ) Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: Already in NETWORK phase Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Phase: deflink: lcp -> open Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:06:24 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Phase: deflink: open -> lcp Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process Apr 26 12:08:23 maraska-gw ppp[956]: tun0: Warning: ff02:6::/32: Change route failed: errno: Network is unreachable Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: Received NGM_PPPOE_CLOSE Apr 26 12:08:24 maraska-gw ppp[956]: tun0: Phase: deflink: Device disconnected Apr 26 12:08:24 maraska-gw ppp[956]
unknown PPP protocol - fragmentation problems
Hi I've just changed ISP and I am having some issues with PPP and large packets. I've got a Draytek Vigor 100 ethernet modem which proxies PPPoA <-> PPPoE so I can initiate the PPPoE connection to my ISP from my FreeBSD 7.0-STABLE box. This worked perfectly with my previous ISP but now any packets larger than 1500 bytes and thus requiring fragmentation which arrive in do not make it to the tun0 ppp interface. For example here I initiate a large ping from outside my network to the machine on which my ppp client is running - # ping -s 1500 -c 1 88.129.153.191 This is what arrives on the physical vr1 interface on which pppoe is running 002774 00:50:7f:8c:f2:08 > 00:00:24:c9:57:39, ethertype PPPoE S (0x8864), length 1018: PPPoE [len 1502 > 998!] [ses 0x3ec] unknown (0x2021), length 998: unknown PPP protocol (0x2021) 0x: 4500 eb13 4357 2000 3301 0334 5775 d0c5 0x0010: 5895 9ac6 0800 6190 ffe8 47fc a40e 0x0020: efd9 0809 0a0b 0c0d 0e0f 1011 1213 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 0x0040: 2425 2627 2829 2a2b 2c2d 40 00:50:7f:8c:f2:08 > 00:00:24:c9:57:39, ethertype PPPoE S (0x8864), length 538: [ver 4] [type 5]PPPoE [len 1502 > 518!] [ses 0x20c] unknown (0x009e), length 518: unknown PPP protocol (0x009e) 0x: 4500 d3ea 4357 2000 3301 0334 c8c9 cacb 0x0010: cccd cecf d0d1 d2d3 d4d5 d6d7 d8d9 dadb 0x0020: dcdd dedf e0e1 e2e3 e4e5 e6e7 e8e9 eaeb 0x0030: eced eeef f0f1 f2f3 f4f5 f6f7 f8f9 fafb 0x0040: fcfd feff 0001 0203 0405 11 00:50:7f:8c:f2:08 > 00:00:24:c9:57:39, ethertype PPPoE S (0x8864), length 70: PPPoE [ses 0x6] IP (0x0021), length 50: (tos 0x0, ttl 51, id 17239, offset 1480, flags [none], proto ICMP (1), length 48) 87.119.223.147 > 88.129.153.191: icmp This is all that arrives on the tun0 ppp interface 15. 242441 AF IPv4 (2), length 52: (tos 0x0, ttl 51, id 18322, offset 1480, flags [none], proto ICMP (1), length 48) 87.119.223.147 > 88.129.153.191: icmp If anyone can decipher this and give me an idea of what's going wrong I'd be most grateful. Thanks Gianni ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Normal CPU usage with a PPP connection
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Nikos > Vassiliadis > Sent: Tuesday, February 26, 2008 1:49 AM > To: freebsd-questions@freebsd.org > Cc: Dylan Smith > Subject: Re: Normal CPU usage with a PPP connection > > > On Sunday 24 February 2008 14:34:37 Dylan Smith wrote: > > Hey guys, i'm running 6.3-R with (i think) userland ppp to connect to my > > ADSL provider over PPPoE. > > I build a number of graphs(mrtg) for system stats and i am noticing that > > under heavy load on my ppp connection, that is sustained 150KB/s for an > > hour or so my cpu usage, based on my graph, hovers around 20% (haven't > > looked at it in top yet but if there isn't a simple solution/reason for > > this i will look into what sort of usage it is). > > You should check top and tcpdump, it might be a big number of small > packets causing the load. > > > The box is a home > > router/server so at any 1 time isn't doing anything else that i can see > > would account for this. I also noticed that this usage increase does not > > occur with traffic coming/going on the inward facing interface, which > > regularly has transfer speeds around 10 MB/s. > > > > I'm running a AMD X2 3800+ with 2GB ram. Is this sort of usage normal? > > Can't really tell if it's normal, but it is known that userland ppp uses > much resources. I have seen it too using 20% CPU time running on > a much slower machine(I faintly remember that it was a Pentium > Celeron at 300MHz) and a much slower(384/128?) ADSL line. > > > Is there something i can do to bring it down? > > Fortunately yes, you could use net/mpd. The CPU load then, > will probably be near zero for normal traffic, the 150KB/s you > mention. If a million of small packets arrive at your router the > load will be higher, nevertheless orders of magnitude lower > than the load caused by userland ppp. > Or, you can ignore it? You still have 80% of the CPU doing nothing Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Normal CPU usage with a PPP connection
On Sunday 24 February 2008 14:34:37 Dylan Smith wrote: > Hey guys, i'm running 6.3-R with (i think) userland ppp to connect to my > ADSL provider over PPPoE. > I build a number of graphs(mrtg) for system stats and i am noticing that > under heavy load on my ppp connection, that is sustained 150KB/s for an > hour or so my cpu usage, based on my graph, hovers around 20% (haven't > looked at it in top yet but if there isn't a simple solution/reason for > this i will look into what sort of usage it is). You should check top and tcpdump, it might be a big number of small packets causing the load. > The box is a home > router/server so at any 1 time isn't doing anything else that i can see > would account for this. I also noticed that this usage increase does not > occur with traffic coming/going on the inward facing interface, which > regularly has transfer speeds around 10 MB/s. > > I'm running a AMD X2 3800+ with 2GB ram. Is this sort of usage normal? Can't really tell if it's normal, but it is known that userland ppp uses much resources. I have seen it too using 20% CPU time running on a much slower machine(I faintly remember that it was a Pentium Celeron at 300MHz) and a much slower(384/128?) ADSL line. > Is there something i can do to bring it down? Fortunately yes, you could use net/mpd. The CPU load then, will probably be near zero for normal traffic, the 150KB/s you mention. If a million of small packets arrive at your router the load will be higher, nevertheless orders of magnitude lower than the load caused by userland ppp. HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Normal CPU usage with a PPP connection
Hey guys, i'm running 6.3-R with (i think) userland ppp to connect to my ADSL provider over PPPoE. I build a number of graphs(mrtg) for system stats and i am noticing that under heavy load on my ppp connection, that is sustained 150KB/s for an hour or so my cpu usage, based on my graph, hovers around 20% (haven't looked at it in top yet but if there isn't a simple solution/reason for this i will look into what sort of usage it is). The box is a home router/server so at any 1 time isn't doing anything else that i can see would account for this. I also noticed that this usage increase does not occur with traffic coming/going on the inward facing interface, which regularly has transfer speeds around 10 MB/s. I'm running a AMD X2 3800+ with 2GB ram. Is this sort of usage normal? Is there something i can do to bring it down? Dylan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PPP] Dialing using a cellphone
On Saturday 02 February 2008 17:44:58 Matthias Apitz wrote: > > At boot, FreeBSD recognizes the phone as a USB modem: > > ugen: Samsung Mobile USB Modem, rev. 2.00/1.00, addr 2 > ... > > However, when I try to actually dial out, I get: > > tun0: Warning: chat_Write: Operation not supported by device > > > > Any thoughts? > > PPP needs a serial device to work with, 'ugen' does not > provide this; More to the point, umodem(4) lists the supported USB modems. The thing to do would be send-pr with output of pciconf -lv and request support for this modem. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PPP] Dialing using a cellphone
El día Saturday, February 02, 2008 a las 02:52:08PM +, Alphons Fonz van Werven escribió: > Hi, > > I'm trying to dial in to my phone provider for internet access using my > cellphone (Samsung D900i) connected to a USB port of my computer. > > At boot, FreeBSD recognizes the phone as a USB modem: > ugen: Samsung Mobile USB Modem, rev. 2.00/1.00, addr 2 'ugen' means that only the USB generic device driver attached to your device; check the man page with 'man ugen' > > I've modified /etc/ppp/ppp.conf to use the device mentioned above: > set device /dev/ugen1 > and changed username, password, phone# etc according to my provider's > settings. > > However, when I try to actually dial out, I get: > tun0: Warning: chat_Write: Operation not supported by device > > Any thoughts? PPP needs a serial device to work with, 'ugen' does not provide this; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[PPP] Dialing using a cellphone
Hi, I'm trying to dial in to my phone provider for internet access using my cellphone (Samsung D900i) connected to a USB port of my computer. At boot, FreeBSD recognizes the phone as a USB modem: ugen: Samsung Mobile USB Modem, rev. 2.00/1.00, addr 2 I've modified /etc/ppp/ppp.conf to use the device mentioned above: set device /dev/ugen1 and changed username, password, phone# etc according to my provider's settings. However, when I try to actually dial out, I get: tun0: Warning: chat_Write: Operation not supported by device Any thoughts? Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
On Thursday 25 October 2007 00:11:39 [EMAIL PROTECTED] wrote: > Oct 24 12:33:35 nightmare ppp[859]: tun0: Debug: deflink: PPPoE:ed1: > Cannot determine bandwidth > > I presume this is a result of the lost LQR packets. No, bandwidth isn't known to ppp. You can ignore this warning. There is no connection between LQR and bandwidth. > The above summary appears to indicate that line quality requests are > being transferred; so what's with the too many LQR packets lost message? Perhaps the peer does not accept LQR. Disable LQR. Disable echo as well. These settings provide some monitoring capabilities, but must be accepted by both peers. If for some reason(probably misconfiguration) these are not accepted by the other peer, things will not work... But, try disabling only LQR at first. > > Finally, > Where does the initial IP address used in the negotiation come from? > I did not specify specific IP address assignment, > yet the request appears to have asked for 12.32.36.65 > This is the IP of the other interface on the machine, > and my ppp.conf has no mention of it. It's not important. These IP addresses will be denied by the other peer during IPCP. The peer will then provide you an IP address and ppp will accept it. Hope this helps Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
Nikos Vassiliadis wrote: You said you had wrong encapsulation type. Did you make any progress? Yes. Changing the encapsulation type brought the line up, and things hobbled along... However, the line is dropped after a few minutes, apparently a result of not being able to determine line quality: Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: ** Too many LQR packets lost ** Oct 24 12:39:06 nightmare ppp[859]: tun0: LQM: deflink: Too many LQR packets lost Oct 24 12:39:06 nightmare ppp[859]: tun0: CCP: deflink: State change Stopped --> Closed Oct 24 12:39:06 nightmare ppp[859]: tun0: CCP: deflink: State change Closed --> Initial Oct 24 12:39:06 nightmare ppp[859]: tun0: LCP: deflink: LayerDown Oct 24 12:39:06 nightmare ppp[859]: tun0: LCP: deflink: State change Opened --> Starting Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: open -> lcp Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_UpdateMTU (5) Oct 24 12:39:06 nightmare ppp[859]: tun0: TCP/IP: route_UpdateMTU: Netif: 5 (tun0), dst 0.0.0.0/0, mtu 1500 Oct 24 12:39:06 nightmare ppp[859]: tun0: TCP/IP: route_UpdateMTU: Netif: 5 (tun0), dst 216.47.48.1, mtu 1500 Oct 24 12:39:06 nightmare ppp[859]: tun0: TCP/IP: route_UpdateMTU: Netif: 5 (tun0), dst ff01:5::/32, mtu 1500 Oct 24 12:39:06 nightmare ppp[859]: tun0: TCP/IP: route_UpdateMTU: Netif: 5 (tun0), dst ff02:5::/32, mtu 1500 Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: deflink: LayerDown: 12.32.44.142 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: ReadSystem: Can't open /etc/ppp/ppp.linkdown. Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: ReadSystem: Can't open /etc/ppp/ppp.linkdown. Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: ReadSystem: Can't open /etc/ppp/ppp.linkdown. Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: deflink: State change Opened --> Starting Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: deflink: LayerFinish. Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: Connect time: 331 secs: 2253 octets in, 1584 octets out Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: 24 packets in, 25 packets out Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: total 11 bytes/sec, peak 275 bytes/sec on Wed Oct 24 12:34:43 2007 Oct 24 12:39:06 nightmare ppp[859]: tun0: IPCP: deflink: State change Starting --> Initial Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: bundle: Terminate Oct 24 12:39:06 nightmare ppp[859]: tun0: LCP: deflink: LayerFinish Oct 24 12:39:06 nightmare ppp[859]: tun0: LCP: deflink: State change Starting --> Initial Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: Disconnected! Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: lcp -> logout Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: Disconnected! Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: logout -> hangup Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: deflink: Close Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: Connect time: 332 secs: 3044 octets in, 2789 octets out Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: 70 packets in, 77 packets out Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: total 17 bytes/sec, peak 315 bytes/sec on Wed Oct 24 12:34:46 2007 Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: deflink: hangup -> closed Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_IfDelete (5) Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found 0.0.0.0/0 216.47.48.1 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_IfDelete: Skip it (pass 0) Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found 216.47.48.1 12.32.44.142 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_IfDelete: Skip it (pass 0) Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found ff01:5::/32 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_IfDelete: Skip it (pass 0) Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found ff02:5::/32 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: route_IfDelete: Skip it (pass 0) Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found 0.0.0.0/0 216.47.48.1 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: wrote 124: cmd = Delete, dst = 0.0.0.0/0, gateway = Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found 216.47.48.1 12.32.44.142 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: wrote 108: cmd = Delete, dst = 216.47.48.1, gateway = Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found ff01:5::/32 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: wrote 148: cmd = Delete, dst = ff01:5::/32, gateway = Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: Found ff02:5::/32 Oct 24 12:39:06 nightmare ppp[859]: tun0: Debug: wrote 148: cmd = Delete, dst = ff02:5::/32, gateway = Oct 24 12:39:06 nightmare ppp[859]: tun0: Phase: bundle: Dead During initial protocol negotiation, it looks like come sort of compression is disallowed, but it doesn't seem like that should cause the line to be dropped later: Oct 24 12:33:35 nightma
Re: user ppp and PPPoE bridging
On Tuesday 23 October 2007 21:04:48 [EMAIL PROTECTED] wrote: > This is a zyxel 642r modem; I can't try my other modem, a cisco 678, > because it doesn't support a vci > 63. Oh cisco :) Be thankful to cisco for not creating other proprietary protocols to replace the existing ATM/DSL combination :) > > The modem is set to use VC-based multiplexing, vpi=0, vci=100 > These are the parameters used for PPPoE, and I presume are still > required as part of the ATM layer when bridging. > > I am assuming there should be no need for my ISP to be notified that I > am trying to use bridging in the modem, since it should be transparent > on their end. They claim not to support bridging, but I don't see how > they can say that, other than that they don't want to deal with the > support issues. Is this a reasonable assumption? My knowledge about ATM is minimal. So, I don't realy know how to answer to your question about bridging being transparent to the ISP. But I can tell you for sure that ISPs do not bother if you cannot connect using FreeBSD and PPPoE. You are mainly on your own. I assume that if you use the same settings your modem uses to do PPPoE it won't make a difference to the ISP end. You said you had wrong encapsulation type. Did you make any progress? > The packets are clearly reaching the modem, as it records them as > received. Can you also check the number of cells going out/coming in from the ATM interface? Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
To answer my own question: I had the mux type set wrong -- VC-based instead of LLC-based. While the line comes up, the session is never opened because of the mux mismatch. moving right along now... Gary The freebsd box is connected directly via ed1 to the dsl modem; a crossover cable is used; the packets are clearly reaching the modem, as it records them as received. I've simplified ppp.conf to the following, essentially the ppp.conf.sample: default: set log all -timer blackfoot: set device PPPoE:ed1 enable lqr echo set cd 5 set redial 0 0 set dial set login set authname set authkey add! default HISADDR #ifconfig ed1 ed1: flags=8943 mtu 1500 inet6 fe80::220:18ff:fe72:8b72%ed1 prefixlen 64 scopeid 0x3 ether 00:20:18:72:8b:72 #tcpdump -efntl -i ed1 tcpdump: WARNING: ed1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ed1, link-type EN10MB (Ethernet), capture size 96 bytes 00:20:18:72:8b:72 > ff:ff:ff:ff:ff:ff, ethertype PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x402DA4C1] [Service-Name] 00:20:18:72:8b:72 > ff:ff:ff:ff:ff:ff, ethertype PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x402DA4C1] [Service-Name] It appears that no PADO reply is being received by the modem; the modem shows two packets being transmitted, but non being received. Since the line is marked as up by the modem, and since the line comes up properly when the modem is operating in full PPPoE mode, I'm puzzled as to what kind of mismatch could be preventing the ISP end from responding. This is a zyxel 642r modem; I can't try my other modem, a cisco 678, because it doesn't support a vci > 63. The modem is set to use VC-based multiplexing, vpi=0, vci=100 These are the parameters used for PPPoE, and I presume are still required as part of the ATM layer when bridging. I am assuming there should be no need for my ISP to be notified that I am trying to use bridging in the modem, since it should be transparent on their end. They claim not to support bridging, but I don't see how they can say that, other than that they don't want to deal with the support issues. Is this a reasonable assumption? Nikos Vassiliadis wrote: On Tuesday 23 October 2007 05:31:45 [EMAIL PROTECTED] wrote: I'm attempting to change a DSL link from using PPPoE in the DSL modem to doing PPPoE on 6.1, with the modem in bridging mode. I've put the DSL modem in bridging mode, and it brings up the link properly -- or at least it reports it as up (DSL led steady; modem status report shows it as up, rfc 1483. Using user ppp, when I attempt to establish the PPPoE connection, I never get very far -- ppp dies when it tries to acquire carrier. I don't understand this, as there isn't a carrier signal to acquire on an ethernet. There is carrier on ethernet. Ethernet belongs to the CSMA/DA model where CS means carrier sense. I tried disabling cd in ppp.conf but as noted in the doc, it's required for a PPPoE connection and is forced on. Also, how do I know know which interface it is attempting to connect to? The debug log shows it found five interfaces, but doesn't indicate which one it is trying to connect to. It tries to use ed1 for PPPoE(set device PPPoE:ed1) Can you use the minimal configuration labelled pppoe from /usr/share/examples/ppp/ppp.conf.sample? The only things you have to change are: The ethernet interface it will try PPPoE. username and password. Is your ed1 connected to the modem directly? Or it goes through a switch? Can you try connecting your ed1 directly on your DSL modem's ethernet port? You might need a crossover cable to do this( http://en.wikipedia.org/wiki/Ethernet_crossover_cable) or not since these days many ethernet ports do this automatically. Please post also ifconfig and run tcpdump on ed1 during try. ... I dont'see anything wrong, but I may be wrong. The small sample configuration always worked for me. Why don't you use it as a starting point? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
Hi Nikos, Thank you and rw for your replies. The freebsd box is connected directly via ed1 to the dsl modem; a crossover cable is used; the packets are clearly reaching the modem, as it records them as received. I've simplified ppp.conf to the following, essentially the ppp.conf.sample: default: set log all -timer blackfoot: set device PPPoE:ed1 enable lqr echo set cd 5 set redial 0 0 set dial set login set authname set authkey add! default HISADDR #ifconfig ed1 ed1: flags=8943 mtu 1500 inet6 fe80::220:18ff:fe72:8b72%ed1 prefixlen 64 scopeid 0x3 ether 00:20:18:72:8b:72 #tcpdump -efntl -i ed1 tcpdump: WARNING: ed1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ed1, link-type EN10MB (Ethernet), capture size 96 bytes 00:20:18:72:8b:72 > ff:ff:ff:ff:ff:ff, ethertype PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x402DA4C1] [Service-Name] 00:20:18:72:8b:72 > ff:ff:ff:ff:ff:ff, ethertype PPPoE D (0x8863), length 32: PPPoE PADI [Host-Uniq 0x402DA4C1] [Service-Name] It appears that no PADO reply is being received by the modem; the modem shows two packets being transmitted, but non being received. Since the line is marked as up by the modem, and since the line comes up properly when the modem is operating in full PPPoE mode, I'm puzzled as to what kind of mismatch could be preventing the ISP end from responding. This is a zyxel 642r modem; I can't try my other modem, a cisco 678, because it doesn't support a vci > 63. The modem is set to use VC-based multiplexing, vpi=0, vci=100 These are the parameters used for PPPoE, and I presume are still required as part of the ATM layer when bridging. I am assuming there should be no need for my ISP to be notified that I am trying to use bridging in the modem, since it should be transparent on their end. They claim not to support bridging, but I don't see how they can say that, other than that they don't want to deal with the support issues. Is this a reasonable assumption? Nikos Vassiliadis wrote: On Tuesday 23 October 2007 05:31:45 [EMAIL PROTECTED] wrote: I'm attempting to change a DSL link from using PPPoE in the DSL modem to doing PPPoE on 6.1, with the modem in bridging mode. I've put the DSL modem in bridging mode, and it brings up the link properly -- or at least it reports it as up (DSL led steady; modem status report shows it as up, rfc 1483. Using user ppp, when I attempt to establish the PPPoE connection, I never get very far -- ppp dies when it tries to acquire carrier. I don't understand this, as there isn't a carrier signal to acquire on an ethernet. There is carrier on ethernet. Ethernet belongs to the CSMA/DA model where CS means carrier sense. I tried disabling cd in ppp.conf but as noted in the doc, it's required for a PPPoE connection and is forced on. Also, how do I know know which interface it is attempting to connect to? The debug log shows it found five interfaces, but doesn't indicate which one it is trying to connect to. It tries to use ed1 for PPPoE(set device PPPoE:ed1) Can you use the minimal configuration labelled pppoe from /usr/share/examples/ppp/ppp.conf.sample? The only things you have to change are: The ethernet interface it will try PPPoE. username and password. Is your ed1 connected to the modem directly? Or it goes through a switch? Can you try connecting your ed1 directly on your DSL modem's ethernet port? You might need a crossover cable to do this( http://en.wikipedia.org/wiki/Ethernet_crossover_cable) or not since these days many ethernet ports do this automatically. Please post also ifconfig and run tcpdump on ed1 during try. ... I dont'see anything wrong, but I may be wrong. The small sample configuration always worked for me. Why don't you use it as a starting point? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
On Mon, 22 Oct 2007 17:50:15 -0600 Gary Aitken <[EMAIL PROTECTED]> wrote: > I'm attempting to change a DSL link from using PPPoE in the DSL modem > to doing PPPoE on 6.1, with the modem in bridging mode. > > I've put the DSL modem in bridging mode, and it brings up the link > properly -- or at least it reports it as up (DSL led steady; modem > status report shows it as up, rfc 1483. > > Using user ppp, when I attempt to establish the PPPoE connection, I > never get very far -- ppp dies when it tries to acquire carrier. I > don't understand this, as there isn't a carrier signal to acquire on > an ethernet. I tried disabling cd in ppp.conf but as noted in the > doc, it's required for a PPPoE connection and is forced on. > I'd try simplifying a bit, this is my ppp.conf file default: set log Phase tun command adsl: set device PPPoE:vr0 set authname ** set authkey *** add default HISADDR # DNS configured manually # enable dns ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: user ppp and PPPoE bridging
On Tuesday 23 October 2007 05:31:45 [EMAIL PROTECTED] wrote: > I'm attempting to change a DSL link from using PPPoE in the DSL modem > to doing PPPoE on 6.1, with the modem in bridging mode. > > I've put the DSL modem in bridging mode, and it brings up the link > properly -- or at least it reports it as up (DSL led steady; modem > status report shows it as up, rfc 1483. > > Using user ppp, when I attempt to establish the PPPoE connection, I > never get very far -- ppp dies when it tries to acquire carrier. I > don't understand this, as there isn't a carrier signal to acquire on > an ethernet. There is carrier on ethernet. Ethernet belongs to the CSMA/DA model where CS means carrier sense. > I tried disabling cd in ppp.conf but as noted in the doc, > it's required for a PPPoE connection and is forced on. > > Also, how do I know know which interface it is attempting to connect to? > The debug log shows it found five interfaces, but doesn't indicate which > one it is trying to connect to. It tries to use ed1 for PPPoE(set device PPPoE:ed1) Can you use the minimal configuration labelled pppoe from /usr/share/examples/ppp/ppp.conf.sample? The only things you have to change are: The ethernet interface it will try PPPoE. username and password. Is your ed1 connected to the modem directly? Or it goes through a switch? Can you try connecting your ed1 directly on your DSL modem's ethernet port? You might need a crossover cable to do this( http://en.wikipedia.org/wiki/Ethernet_crossover_cable) or not since these days many ethernet ports do this automatically. Please post also ifconfig and run tcpdump on ed1 during try. > [snip] > > ==== ppp.conf: === > > default: > set log all > set log -timer > ident user-ppp VERSION (built COMPILATIONDATE) > set redial 15 0 > set reconnect 15 1 > isp: > set device PPPoE:ed1 > disable acfcomp protocomp > deny acfcomp > set mtu max 1492 > set mru max 1492 > enable mssfixup > set speed sync > enable lqr > set lqrperiod 5 > set ctsrts off > disable ipv6cp > set dial > set login > set timeout 0 > set authname xx > set authkey yy > add! default HISADDR > I dont'see anything wrong, but I may be wrong. The small sample configuration always worked for me. Why don't you use it as a starting point? Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
user ppp and PPPoE bridging
I'm attempting to change a DSL link from using PPPoE in the DSL modem
to doing PPPoE on 6.1, with the modem in bridging mode.
I've put the DSL modem in bridging mode, and it brings up the link
properly -- or at least it reports it as up (DSL led steady; modem status
report shows it as up, rfc 1483.
Using user ppp, when I attempt to establish the PPPoE connection, I
never get very far -- ppp dies when it tries to acquire carrier. I
don't understand this, as there isn't a carrier signal to acquire on
an ethernet. I tried disabling cd in ppp.conf but as noted in the doc,
it's required for a PPPoE connection and is forced on.
Also, how do I know know which interface it is attempting to connect to?
The debug log shows it found five interfaces, but doesn't indicate which
one it is trying to connect to.
Thanks for any clues,
Gary
log file: =====
Oct 22 16:34:15 nightmare ppp[84336]: Phase: Using interface: tun0 Oct 22
16:34:15 nightmare ppp[84336]: Phase: deflink: Created in closed state
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set log -timer
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: ident user-ppp
VERSION (built COMPILATIONDATE)
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set redial 15 0
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set reconnect 15
10000
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Phase: PPP Started (interactive
mode).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: /dev/ttyp3: dial blackfoot
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking default
(/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set device
PPPoE:ed1
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable acfcomp
protocomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: deny acfcomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mtu max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mru max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable mssfixup
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set speed sync
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable lqr
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set lqrperiod 5
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set ctsrts off
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable ipv6cp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set dial
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set login
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set timeout 0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authname
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authkey
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: add! default
HISADDR
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 3 = socket(17, 3, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: bundle: Establish
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: deflink: closed -> opening
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = NgMkSockNode("", &cs, &ds)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: List of netgraph node
``ed1:'' (id 2) hooks:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found orphans -> ethernet
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Connecting netgraph socket
.:tun0 -> [8]::tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 4 = socket(2, 2, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 3223349521,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 2149607696,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Sending PPPOE_CONNECT to
.:tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found the following
interfaces:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 1, name "ep0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 2, name "plip0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 3, name "ed1"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 4, name "lo0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0:
user ppp and PPPoE bridging
I'm attempting to change a DSL link from using PPPoE in the DSL modem
to doing PPPoE on 6.1, with the modem in bridging mode.
I've put the DSL modem in bridging mode, and it brings up the link
properly -- or at least it reports it as up (DSL led steady; modem status
report shows it as up, rfc 1483.
Using user ppp, when I attempt to establish the PPPoE connection, I
never get very far -- ppp dies when it tries to acquire carrier. I
don't understand this, as there isn't a carrier signal to acquire on
an ethernet. I tried disabling cd in ppp.conf but as noted in the doc,
it's required for a PPPoE connection and is forced on.
Also, how do I know know which interface it is attempting to connect to?
The debug log shows it found five interfaces, but doesn't indicate which
one it is trying to connect to.
Thanks for any clues,
Gary
log file: =====
Oct 22 16:34:15 nightmare ppp[84336]: Phase: Using interface: tun0 Oct 22
16:34:15 nightmare ppp[84336]: Phase: deflink: Created in closed state
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set log -timer
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: ident user-ppp
VERSION (built COMPILATIONDATE)
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set redial 15 0
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set reconnect 15
10000
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Phase: PPP Started (interactive
mode).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: /dev/ttyp3: dial blackfoot
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking default
(/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set device
PPPoE:ed1
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable acfcomp
protocomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: deny acfcomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mtu max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mru max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable mssfixup
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set speed sync
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable lqr
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set lqrperiod 5
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set ctsrts off
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable ipv6cp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set dial
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set login
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set timeout 0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authname
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authkey
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: add! default
HISADDR
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 3 = socket(17, 3, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: bundle: Establish
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: deflink: closed -> opening
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = NgMkSockNode("", &cs, &ds)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: List of netgraph node
``ed1:'' (id 2) hooks:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found orphans -> ethernet
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Connecting netgraph socket
.:tun0 -> [8]::tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 4 = socket(2, 2, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 3223349521,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 2149607696,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Sending PPPOE_CONNECT to
.:tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found the following
interfaces:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 1, name "ep0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 2, name "plip0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 3, name "ed1"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 4, name "lo0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0:
user ppp and PPPoE bridging
I'm attempting to change a DSL link from using PPPoE in the DSL modem
to doing PPPoE on 6.1, with the modem in bridging mode.
I've put the DSL modem in bridging mode, and it brings up the link
properly -- or at least it reports it as up (DSL led steady; modem status
report shows it as up, rfc 1483.
Using user ppp, when I attempt to establish the PPPoE connection, I
never get very far -- ppp dies when it tries to acquire carrier. I
don't understand this, as there isn't a carrier signal to acquire on
an ethernet. I tried disabling cd in ppp.conf but as noted in the doc,
it's required for a PPPoE connection and is forced on.
Also, how do I know know which interface it is attempting to connect to?
The debug log shows it found five interfaces, but doesn't indicate which
one it is trying to connect to.
Thanks for any clues,
Gary
log file: =====
Oct 22 16:34:15 nightmare ppp[84336]: Phase: Using interface: tun0 Oct 22
16:34:15 nightmare ppp[84336]: Phase: deflink: Created in closed state
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set log -timer
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: ident user-ppp
VERSION (built COMPILATIONDATE)
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set redial 15 0
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Command: default: set reconnect 15
10000
Oct 22 16:34:15 nightmare ppp[84336]: tun0: Phase: PPP Started (interactive
mode).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: /dev/ttyp3: dial blackfoot
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking default
(/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0x282e72e0 = fopen("/etc/ppp/ppp.conf",
"r")
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: ReadSystem: Checking
blackfoot (/etc/ppp/ppp.conf).
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set device
PPPoE:ed1
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable acfcomp
protocomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: deny acfcomp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mtu max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set mru max 1492
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable mssfixup
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set speed sync
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: enable lqr
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set lqrperiod 5
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set ctsrts off
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: disable ipv6cp
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set dial
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set login
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set timeout 0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authname
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: set authkey
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Command: blackfoot: add! default
HISADDR
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 3 = socket(17, 3, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: bundle: Establish
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Phase: deflink: closed -> opening
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = NgMkSockNode("", &cs, &ds)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: List of netgraph node
``ed1:'' (id 2) hooks:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found orphans -> ethernet
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Connecting netgraph socket
.:tun0 -> [8]::tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 4 = socket(2, 2, 0)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 3223349521,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: ID0: 0 = ioctl(4, 2149607696,
0xbfbfda00)
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Sending PPPOE_CONNECT to
.:tun0
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Found the following
interfaces:
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 1, name "ep0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 2, name "plip0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 3, name "ed1"
Oct 22 16:34:24 nightmare ppp[84336]: tun0: Debug: Index 4, name "lo0"
Oct 22 16:34:24 nightmare ppp[84336]: tun0:
Re: Problem with ppp
Kevin Kinsey wrote: > Lars Normann wrote: >> I just upgraded my kernel and system. I also ran mergemaster. > > > Upgraded to what? `uname -a` ... FreeBSD tengil 6.2-STABLE FreeBSD 6.2-STABLE #0: Sun Oct 14 03:29:35 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TENGIL i386 > >> Now, when i go online with 'ppp -ddial telenor', I get this error in my >> ppp.log: >> >> "tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process" >> >> Here is my full ppp.log when connecting: >> >> Oct 15 01:42:05 tengil ppp[1343]: Phase: Using interface: tun0 >> Oct 15 01:42:05 tengil ppp[1343]: Phase: deflink: Created in closed state >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set device >> PPPoE:ep0 >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authname >> [EMAIL PROTECTED] >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authkey >> >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set dial >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set login >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set mtu 1464 >> Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: add default >> HISADDR >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: PPP Started (ddial mode). >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: bundle: Establish >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: closed -> opening >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: Connected! >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: opening -> dial >> Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: dial -> carrier >> Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_ACNAME >> (hook "ti500710a340") >> Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received >> NGM_PPPOE_SESSIONID >> Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_SUCCESS >> Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: carrier -> login >> Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: login -> lcp >> Oct 15 01:42:07 tengil ppp[1344]: tun0: Warning: deflink: Reducing >> configured MRU from 1500 to 1492 >> Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: bundle: Authenticate >> Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: deflink: his = PAP, mine >> = none >> Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: Pap Output: >> [EMAIL PROTECTED] >> Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: Pap Input: SUCCESS >> (Nextra dialin) >> Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: deflink: lcp -> open >> Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: bundle: Network >> Oct 15 01:42:08 tengil ppp[1344]: tun0: Warning: 0.0.0.0/0: Change route >> failed: errno: No such process >> >> What is going on here? Tried searching the archive and google but found >> nothing. > > Hmm. The message comes from usr.sbin/ppp/route.c, but that hasn't been > changed in 2 years, so I doubt you've hit a new bug. > > Got any strange routes set? What does `netstat -nrf inet` show? Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default88.88.120.0UGS 0 638892 tun0 10 link#1 UC 00rl0 10.0.0.1 00:10:a7:14:ad:0c UHLW1 146lo0 10.0.0.100 00:0c:76:1c:d7:40 UHLW1 104282rl0789 10.0.0.113 00:0a:cd:0f:61:98 UHLW1 442983rl0 1128 10.0.0.117 00:16:38:e9:9d:6f UHLW115306rl0 1174 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 1 184rl0 88.88.120.088.88.122.104 UH 10 tun0 127.0.0.1 127.0.0.1 UH 00lo0 > > Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with ppp
Lars Normann wrote: I just upgraded my kernel and system. I also ran mergemaster. Upgraded to what? `uname -a` ... Now, when i go online with 'ppp -ddial telenor', I get this error in my ppp.log: "tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process" Here is my full ppp.log when connecting: Oct 15 01:42:05 tengil ppp[1343]: Phase: Using interface: tun0 Oct 15 01:42:05 tengil ppp[1343]: Phase: deflink: Created in closed state Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set device PPPoE:ep0 Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authname [EMAIL PROTECTED] Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authkey Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set dial Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set login Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set mtu 1464 Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: add default HISADDR Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: PPP Started (ddial mode). Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: bundle: Establish Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: closed -> opening Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: Connected! Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: opening -> dial Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: dial -> carrier Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook "ti500710a340") Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_SESSIONID Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_SUCCESS Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: carrier -> login Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: login -> lcp Oct 15 01:42:07 tengil ppp[1344]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492 Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: bundle: Authenticate Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: deflink: his = PAP, mine = none Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: Pap Output: [EMAIL PROTECTED] Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: Pap Input: SUCCESS (Nextra dialin) Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: deflink: lcp -> open Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: bundle: Network Oct 15 01:42:08 tengil ppp[1344]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process What is going on here? Tried searching the archive and google but found nothing. Hmm. The message comes from usr.sbin/ppp/route.c, but that hasn't been changed in 2 years, so I doubt you've hit a new bug. Got any strange routes set? What does `netstat -nrf inet` show? Kevin Kinsey -- We read to say that we have read. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with ppp
I just upgraded my kernel and system. I also ran mergemaster. Now, when i go online with 'ppp -ddial telenor', I get this error in my ppp.log: "tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process" Here is my full ppp.log when connecting: Oct 15 01:42:05 tengil ppp[1343]: Phase: Using interface: tun0 Oct 15 01:42:05 tengil ppp[1343]: Phase: deflink: Created in closed state Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set device PPPoE:ep0 Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authname [EMAIL PROTECTED] Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set authkey Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set dial Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set login Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: set mtu 1464 Oct 15 01:42:05 tengil ppp[1343]: tun0: Command: telenor: add default HISADDR Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: PPP Started (ddial mode). Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: bundle: Establish Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: closed -> opening Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: Connected! Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: opening -> dial Oct 15 01:42:05 tengil ppp[1344]: tun0: Phase: deflink: dial -> carrier Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook "ti500710a340") Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_SESSIONID Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: Received NGM_PPPOE_SUCCESS Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: carrier -> login Oct 15 01:42:06 tengil ppp[1344]: tun0: Phase: deflink: login -> lcp Oct 15 01:42:07 tengil ppp[1344]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492 Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: bundle: Authenticate Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: deflink: his = PAP, mine = none Oct 15 01:42:07 tengil ppp[1344]: tun0: Phase: Pap Output: [EMAIL PROTECTED] Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: Pap Input: SUCCESS (Nextra dialin) Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: deflink: lcp -> open Oct 15 01:42:08 tengil ppp[1344]: tun0: Phase: bundle: Network Oct 15 01:42:08 tengil ppp[1344]: tun0: Warning: 0.0.0.0/0: Change route failed: errno: No such process What is going on here? Tried searching the archive and google but found nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
Bahman M. wrote: Once I had a similar problem on a Linux box (send OK/no receive) and after days of playing with settings and configurations I found that the problem was the network _cable_. I replaced the cable and it went fine without any additional configurations. Hope this helps. Bahman Thank for the suggestion, I've got PPP! I too don't know why but I've switched cables and some of them worked for ppp, some of them didn't. But for basic network flow, they all work. WTF? Nikos Vassiliadis wrote: > > [EMAIL PROTECTED] wrote: > > > > LAN]--[Microsoft Windows XP w/ routing]--[Dialcom ADSL Bridge]--[line > > //WORKS LAN][Corega BAR SD hardware router]--[Dialcom ADSL > > Bridge]--[line //WORKS LAN]--[FreeBSD software router]--[Dialcom > > ADSL Bridge]--[line //SUCKS :) > > > > What does FreeBSD suck at? > > I know FreeBSD PPPoE doesn't suck for sure. Also, if FreeBSD > doesn't work for you, that doesn't have to mean it's broken. > What I was trying to get at is that the internet connection can be made with the hardware router. Which means either that that ADSL modem is in bridging mode already, or it does not need to be in it at all, but FreeBSD requires some wtf. Thx again ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
Once I had a similar problem on a Linux box (send OK/no receive) and after days of playing with settings and configurations I found that the problem was the network _cable_. I replaced the cable and it went fine without any additional configurations. Hope this helps. Bahman On 8/29/07, Nikos Vassiliadis <[EMAIL PROTECTED]> wrote: > On Wednesday 29 August 2007 12:15, [EMAIL PROTECTED] wrote: > > Nikos Vassiliadis wrote: > > >> The tcpdump test displays PADI! OK, so not in bridging more? > > > > > > No, PADI is your request for initiating a PPPoE connection. > > > You should see an offer(PADO). Something like this: > > > 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq > > > 0x04000700] 09:18:01.731345 PPPoE PADI [Service-Name] > > > [Host-Uniq 0x04000700] 09:18:01.731694 PPPoE PADO [AC-Name > > > "iris.teledomenet.gr"] [Service-Name] > > > > [Service-Name "*"] [Host-Uniq 0x04000700] [AC-Cookie 0x80DEECC3] > > > > > 09:18:01.731772 PPPoE PADR [Service-Name] [Host-Uniq > > > 0x04000800] > > > > [AC-Cookie 0x80DEECC3] > > > > > 09:18:01.731786 PPPoE PADS [ses 0x46] [AC-Name "iris.teledomenet.gr"] > > > > [Service-Name] [Host-Uniq 0x04000800] [AC-Cookie 0x80DEECC3] > > > > > 09:18:01.732322 PPPoE [ses 0x46] LCP, Conf-Request (0x01), id 22, > > > length 18 09:18:01.736886 PPPoE [ses 0x46] LCP, Conf-Request (0x01), > > > id 0, length 19 09:18:01.737145 PPPoE [ses 0x46] LCP, Conf-Reject > > > (0x04), id 0, length 9 09:18:01.747045 PPPoE [ses 0x46] LCP, > > > Conf-Reject (0x04), id 22, length 8 > > > > I get only things like this (without -v or -vv): > > 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq 0x04000700] > > > > Like 3 of these lines. Just that. No PADO and nothing else whatsoever. > > OK, once again, no replies from the outside world... > FreeBSD sends requests, but doesn't get any replies. > > > > > >> The modem is a Dialcom ADSL Bridge 1600, which sound like some > > >> bridge, duh. I've searched for information about this product, there > > >> is no support for it. Dialcom sells these things to ISPs only I > > >> think. There's supposed to be a web interface to it, but I couldn't > > >> get in there yet. > > > > > > Well, it's not optional to check the modem's settings:) > > > The two settings you have to configure for bridging are: > > > 1) enable bridging:) > > > 2) correct virtual circuit, you have to use correct VPI/VCI. > > >You should get this from your ISP. > > > > > 1) do this: > > > Perhaps your modem has DHCP. Try "dhclient rl0". If you do get > > > an address on your rl0, then do a "route -n get default" and > > > try to connect to the gateway using a web browser. > > 2) post your network configuration, that is: > ifconfig -u > netstat -rnfinet > > I asked in previous mail what's the purpose of ipfw and bridge. > Can you disable them? at least for testing purposes. > > > > Because your modem is probably not configured correctly. FreeBSD > > > sends requests, but doesn't get any answers back. FreeBSD is widely > > > tested with PPPoE, both in server and client environments. > > > > I mean > > > > LAN]--[Microsoft Windows XP w/ routing]--[Dialcom ADSL Bridge]--[line > > //WORKS LAN][Corega BAR SD hardware router]--[Dialcom ADSL > > Bridge]--[line //WORKS LAN]--[FreeBSD software router]--[Dialcom > > ADSL Bridge]--[line //SUCKS :) > > > > What does FreeBSD suck at? > > I know FreeBSD PPPoE doesn't suck for sure. Also, if FreeBSD > doesn't work for you, that doesn't have to mean it's broken. > > Nikos > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
On Wednesday 29 August 2007 12:15, [EMAIL PROTECTED] wrote: > Nikos Vassiliadis wrote: > >> The tcpdump test displays PADI! OK, so not in bridging more? > > > > No, PADI is your request for initiating a PPPoE connection. > > You should see an offer(PADO). Something like this: > > 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq > > 0x04000700] 09:18:01.731345 PPPoE PADI [Service-Name] > > [Host-Uniq 0x04000700] 09:18:01.731694 PPPoE PADO [AC-Name > > "iris.teledomenet.gr"] [Service-Name] > > [Service-Name "*"] [Host-Uniq 0x04000700] [AC-Cookie 0x80DEECC3] > > > 09:18:01.731772 PPPoE PADR [Service-Name] [Host-Uniq > > 0x04000800] > > [AC-Cookie 0x80DEECC3] > > > 09:18:01.731786 PPPoE PADS [ses 0x46] [AC-Name "iris.teledomenet.gr"] > > [Service-Name] [Host-Uniq 0x04000800] [AC-Cookie 0x80DEECC3] > > > 09:18:01.732322 PPPoE [ses 0x46] LCP, Conf-Request (0x01), id 22, > > length 18 09:18:01.736886 PPPoE [ses 0x46] LCP, Conf-Request (0x01), > > id 0, length 19 09:18:01.737145 PPPoE [ses 0x46] LCP, Conf-Reject > > (0x04), id 0, length 9 09:18:01.747045 PPPoE [ses 0x46] LCP, > > Conf-Reject (0x04), id 22, length 8 > > I get only things like this (without -v or -vv): > 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq 0x04000700] > > Like 3 of these lines. Just that. No PADO and nothing else whatsoever. OK, once again, no replies from the outside world... FreeBSD sends requests, but doesn't get any replies. > > >> The modem is a Dialcom ADSL Bridge 1600, which sound like some > >> bridge, duh. I've searched for information about this product, there > >> is no support for it. Dialcom sells these things to ISPs only I > >> think. There's supposed to be a web interface to it, but I couldn't > >> get in there yet. > > > > Well, it's not optional to check the modem's settings:) > > The two settings you have to configure for bridging are: > > 1) enable bridging:) > > 2) correct virtual circuit, you have to use correct VPI/VCI. > >You should get this from your ISP. > > 1) do this: > > Perhaps your modem has DHCP. Try "dhclient rl0". If you do get > > an address on your rl0, then do a "route -n get default" and > > try to connect to the gateway using a web browser. 2) post your network configuration, that is: ifconfig -u netstat -rnfinet I asked in previous mail what's the purpose of ipfw and bridge. Can you disable them? at least for testing purposes. > > Because your modem is probably not configured correctly. FreeBSD > > sends requests, but doesn't get any answers back. FreeBSD is widely > > tested with PPPoE, both in server and client environments. > > I mean > > LAN]--[Microsoft Windows XP w/ routing]--[Dialcom ADSL Bridge]--[line > //WORKS LAN][Corega BAR SD hardware router]--[Dialcom ADSL > Bridge]--[line //WORKS LAN]--[FreeBSD software router]--[Dialcom > ADSL Bridge]--[line //SUCKS :) > > What does FreeBSD suck at? I know FreeBSD PPPoE doesn't suck for sure. Also, if FreeBSD doesn't work for you, that doesn't have to mean it's broken. Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
Nikos Vassiliadis wrote: >> The tcpdump test displays PADI! OK, so not in bridging more? > > No, PADI is your request for initiating a PPPoE connection. > You should see an offer(PADO). Something like this: > 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq 0x04000700] > 09:18:01.731345 PPPoE PADI [Service-Name] [Host-Uniq 0x04000700] > 09:18:01.731694 PPPoE PADO [AC-Name "iris.teledomenet.gr"] [Service-Name] [Service-Name "*"] [Host-Uniq 0x04000700] [AC-Cookie 0x80DEECC3] > 09:18:01.731772 PPPoE PADR [Service-Name] [Host-Uniq 0x04000800] [AC-Cookie 0x80DEECC3] > 09:18:01.731786 PPPoE PADS [ses 0x46] [AC-Name "iris.teledomenet.gr"] [Service-Name] [Host-Uniq 0x04000800] [AC-Cookie 0x80DEECC3] > 09:18:01.732322 PPPoE [ses 0x46] LCP, Conf-Request (0x01), id 22, length 18 > 09:18:01.736886 PPPoE [ses 0x46] LCP, Conf-Request (0x01), id 0, length 19 > 09:18:01.737145 PPPoE [ses 0x46] LCP, Conf-Reject (0x04), id 0, length 9 > 09:18:01.747045 PPPoE [ses 0x46] LCP, Conf-Reject (0x04), id 22, length 8 > I get only things like this (without -v or -vv): 09:17:56.744957 PPPoE PADI [Service-Name] [Host-Uniq 0x04000700] Like 3 of these lines. Just that. No PADO and nothing else whatsoever. >> The modem is a Dialcom ADSL Bridge 1600, which sound like some bridge, >> duh. I've searched for information about this product, there is no >> support for it. Dialcom sells these things to ISPs only I think. There's >> supposed to be a web interface to it, but I couldn't get in there yet. > > Well, it's not optional to check the modem's settings:) > The two settings you have to configure for bridging are: > 1) enable bridging:) > 2) correct virtual circuit, you have to use correct VPI/VCI. >You should get this from your ISP. > > Perhaps your modem has DHCP. Try "dhclient rl0". If you do get > an address on your rl0, then do a "route -n get default" and > try to connect to the gateway using a web browser. > > I would also set the modem to factory defaults. At least > then you will know some settings. Most modems have a little > button which can be pressed using a pin. I understood that > you did get the modem second-hand. > > My hungarian is not very good these days. But you can see IP addresses etc > http://oldradio.tesla.hu/szetszedtem/039adslmodemek/004dialcom/dialcom.htm > Yes, I think I can google too. About that button, I don't ever have to press it until I really fuck up something in the settings. I did exactly what was told there to get the web interface page, but I got none. Now I'm gonna try that FreeBSD method. >> One important thing. FreeBSD is a good piece of software. If a hardware >> router can establish a PPPoE connection, why can't FreeBSD do the same >> thing? What does my hardware router have what FreeBSD doesn't? > > Because your modem is probably not configured correctly. FreeBSD sends > requests, but doesn't get any answers back. FreeBSD is widely tested > with PPPoE, both in server and client environments. > I mean LAN]--[Microsoft Windows XP w/ routing]--[Dialcom ADSL Bridge]--[line //WORKS LAN][Corega BAR SD hardware router]--[Dialcom ADSL Bridge]--[line //WORKS LAN]--[FreeBSD software router]--[Dialcom ADSL Bridge]--[line //SUCKS :) What does FreeBSD suck at? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
On Tuesday 28 August 2007 19:25, [EMAIL PROTECTED] wrote: > Nikos Vassiliadis wrote: > > On Tuesday 28 August 2007 13:48, [EMAIL PROTECTED] wrote: > >> What does configuring the modem in bridging mode means? > >> > >> = > >>= =ppp.conf > >> = > >> = > >>= > >> > >> default: > >> set device PPPoE:rl0 > >> set MTU 1492 > >> set MRU 1492 > >> set crtscts off > >> set speed sync > >> #set timeout 0 > >> #set redial 0 0 > >> enable lqr > >> #disable deflate > >> #disable pred1 > >> #disable vjcomp > >> #disable acfcomp > >> #disable protocomp > >> set log Phase tun LCP IPCP CCP Warning Error Alert > >> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > >> add default HISADDR > >> #enable proxy > >> #nat enable yes > >> #nat log yes > >> #nat same_ports yes > >> #nat unregistered_only yes > >> #nat deny_incoming yes > >> dsl: > >> set login > >> set authname [EMAIL PROTECTED] > >> set authkey asd12345 > > > > This configuration file has several irrelevant settings. > > Try the one below, it's from here: > > /usr/share/examples/ppp/ppp.conf.sample > > I just added "set authname" & "set authkey", > > changed the NIC's name and removed the service name. > > > > pppoe: > > set authname "your_username" > > set authkey "your_password" > > set device PPPoE:rl0 > > enable lqr echo > > set cd 5 > > set dial > > set login > > set redial 0 0 > > > > [snip] > > > >> = > >>= ===sysctl.conf > >> > >> = > >>= > >> > >> net.link.ether.bridge.config=rl0:0,ed0:0 > >> net.link.ether.bridge.ipfw=1 > >> net.link.ether.bridge.enable=1 > >> net.inet.ip.forwarding=1 > > > > This has nothing to do with modem bridging mode. > > This bridges your two ethernet segments. Disable it if > > that's not what you want. > > > >> ========= > >>= =ppp.log > >> == > >> ===== > >>= > >> > >> Aug 28 03:58:21 cp ppp[786]: Phase: Using interface: tun0 > >> Aug 28 03:58:21 cp ppp[786]: Phase: deflink: Created in closed state > >> Aug 28 03:58:21 cp ppp[786]: tun0: Phase: PPP Started (interactive > >> mode). Aug 28 03:58:22 cp ppp[801]: Phase: Using interface: tun1 > >> Aug 28 03:58:22 cp ppp[801]: Phase: deflink: Created in closed state > >> Aug 28 03:58:22 cp ppp[802]: tun1: Phase: PPP Started (auto mode). > >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: bundle: Establish > >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: closed -> opening > >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: Connected! > >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: opening -> dial > >> Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: dial -> carrier > >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Disconnected! > >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: carrier -> hangup > >> Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Connect time: 5 > >> secs: 0 octets in, 0 octets out > > > > ^^ > > Zero octets in and zero octets out. Is your modem in bridging mode? > > It may be called rfc1483. Enable it. > > > > check what goes on with tcpdump: > > root:0:/# tcpdump -nli rl0 > > tcpdump: verbose output suppressed, use -v or -vv for full protocol > > decode listening on rl0, link-type EN10MB (Ethernet), capture size 96 > > bytes 14:34:54.863275 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name] > > 14:34:56.862997 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name] > > 14:34:59.969272 PPPoE PADI [Host-Uniq 0xC00CFAC3] [Service-Name] > > > > This is not what you should see, you should see PADO and the rest. > > If
Re: i can't get ppp running
On Tuesday 28 August 2007 13:48, [EMAIL PROTECTED] wrote: > What does configuring the modem in bridging mode means? > > == > =ppp.conf= > == > > default: > set device PPPoE:rl0 > set MTU 1492 > set MRU 1492 > set crtscts off > set speed sync > #set timeout 0 > #set redial 0 0 > enable lqr > #disable deflate > #disable pred1 > #disable vjcomp > #disable acfcomp > #disable protocomp > set log Phase tun LCP IPCP CCP Warning Error Alert > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 > add default HISADDR > #enable proxy > #nat enable yes > #nat log yes > #nat same_ports yes > #nat unregistered_only yes > #nat deny_incoming yes > dsl: > set login > set authname [EMAIL PROTECTED] > set authkey asd12345 > This configuration file has several irrelevant settings. Try the one below, it's from here: /usr/share/examples/ppp/ppp.conf.sample I just added "set authname" & "set authkey", changed the NIC's name and removed the service name. pppoe: set authname "your_username" set authkey "your_password" set device PPPoE:rl0 enable lqr echo set cd 5 set dial set login set redial 0 0 [snip] > == > ===sysctl.conf > == > > net.link.ether.bridge.config=rl0:0,ed0:0 > net.link.ether.bridge.ipfw=1 > net.link.ether.bridge.enable=1 > net.inet.ip.forwarding=1 > This has nothing to do with modem bridging mode. This bridges your two ethernet segments. Disable it if that's not what you want. > ====== > =ppp.log== > ====== > > Aug 28 03:58:21 cp ppp[786]: Phase: Using interface: tun0 > Aug 28 03:58:21 cp ppp[786]: Phase: deflink: Created in closed state > Aug 28 03:58:21 cp ppp[786]: tun0: Phase: PPP Started (interactive > mode). Aug 28 03:58:22 cp ppp[801]: Phase: Using interface: tun1 > Aug 28 03:58:22 cp ppp[801]: Phase: deflink: Created in closed state > Aug 28 03:58:22 cp ppp[802]: tun1: Phase: PPP Started (auto mode). > Aug 28 03:59:40 cp ppp[786]: tun0: Phase: bundle: Establish > Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: closed -> opening > Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: Connected! > Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: opening -> dial > Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: dial -> carrier > Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Disconnected! > Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: carrier -> hangup > Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Connect time: 5 secs: > 0 octets in, 0 octets out ^^ Zero octets in and zero octets out. Is your modem in bridging mode? It may be called rfc1483. Enable it. check what goes on with tcpdump: root:0:/# tcpdump -nli rl0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on rl0, link-type EN10MB (Ethernet), capture size 96 bytes 14:34:54.863275 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name] 14:34:56.862997 PPPoE PADI [Host-Uniq 0xC0656EC3] [Service-Name] 14:34:59.969272 PPPoE PADI [Host-Uniq 0xC00CFAC3] [Service-Name] This is not what you should see, you should see PADO and the rest. If that's what you see, your modem is probably not in bridging mode. [snip] Hope this helps Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i can't get ppp running
What does configuring the modem in bridging mode means? == =ppp.conf= == default: set device PPPoE:rl0 set MTU 1492 set MRU 1492 set crtscts off set speed sync #set timeout 0 #set redial 0 0 enable lqr #disable deflate #disable pred1 #disable vjcomp #disable acfcomp #disable protocomp set log Phase tun LCP IPCP CCP Warning Error Alert set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0 add default HISADDR #enable proxy #nat enable yes #nat log yes #nat same_ports yes #nat unregistered_only yes #nat deny_incoming yes dsl: set login set authname [EMAIL PROTECTED] set authkey asd12345 == =rc.conf== == usbd_enable="YES" inetd_enable="YES" hostname="some.host.name" #defaultrouter="192.168.123.254" ifconfig_ed0="inet 192.168.123.251 netmask 255.255.255.0" ifconfig_rl0="up" rpcbind_enable="YES" nfs_server_enable="YES" nfs_client_enable="YES" mountd_flags="-r" firewall_enable="YES" firewall_type="open" #firewall_type="/etc/rc.firewall.local" #firewall_quiet="YES" firewall_logging="YES" #ppp_enable="YES" #ppp_mode="ddial" #ppp_profile="dsl" #ppp_nat="YES" gateway_enable="YES" #natd_enable="YES" #natd_interface="tun0" #natd_flags="-dynamic" #router_enable="NO" == ===sysctl.conf == net.link.ether.bridge.config=rl0:0,ed0:0 net.link.ether.bridge.ipfw=1 net.link.ether.bridge.enable=1 net.inet.ip.forwarding=1 ====== =ppp.log====== ========== Aug 28 03:58:21 cp ppp[786]: Phase: Using interface: tun0 Aug 28 03:58:21 cp ppp[786]: Phase: deflink: Created in closed state Aug 28 03:58:21 cp ppp[786]: tun0: Phase: PPP Started (interactive mode). Aug 28 03:58:22 cp ppp[801]: Phase: Using interface: tun1 Aug 28 03:58:22 cp ppp[801]: Phase: deflink: Created in closed state Aug 28 03:58:22 cp ppp[802]: tun1: Phase: PPP Started (auto mode). Aug 28 03:59:40 cp ppp[786]: tun0: Phase: bundle: Establish Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: closed -> opening Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: Connected! Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: opening -> dial Aug 28 03:59:40 cp ppp[786]: tun0: Phase: deflink: dial -> carrier Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Disconnected! Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: carrier -> hangup Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: 0 packets in, 0 packets out Aug 28 03:59:45 cp ppp[786]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Tue Aug 28 03:59:40 2007 Aug 28 03:59:45 cp ppp[786]: tun0: Phase: deflink: hangup -> closed Aug 28 03:59:45 cp ppp[786]: tun0: Phase: bundle: Dead Aug 28 03:59:46 cp ppp[786]: tun0: Phase: PPP Terminated (normal). Aug 28 04:10:05 cp ppp[802]: tun1: Phase: bundle: Establish Aug 28 04:10:05 cp ppp[802]: tun1: Phase: deflink: closed -> opening Aug 28 04:10:05 cp ppp[802]: tun1: Phase: deflink: Connected! Aug 28 04:10:05 cp ppp[802]: tun1: Phase: deflink: opening -> dial Aug 28 04:10:05 cp ppp[802]: tun1: Phase: deflink: dial -> carrier Aug 28 04:10:10 cp ppp[802]: tun1: Phase: deflink: Disconnected! Aug 28 04:10:10 cp ppp[802]: tun1: Phase: deflink: carrier -> hangup Aug 28 04:10:10 cp ppp[802]: tun1: Phase: deflink: Connect time: 5 secs: 0 octets in, 0 octets out Aug 28 04:10:10 cp ppp[802]: tun1: Phase: deflink: 0 packets in, 0 packets out Aug 28 04:10:10 cp ppp[802]: tun1: Phase: total 0 bytes/sec, peak 0 bytes/sec on Tue Aug 28 04:10:05 2007 Aug 28 04:10:10 cp ppp[802]: tun1: Phase: deflink: hangup -> closed Aug 28 04:10:10 cp ppp[802]: tun1: Phase: bundle: Dead Aug 28 04:10:12 cp ppp[802]: tun1: Phase: bundle: Establish Aug 28 04:10:12 cp ppp[802]: tun1: Phase: deflink: closed -> opening Aug 28 04:10:12 cp ppp[802]: tun1: Phase: deflink: Connected! Aug 28 04:10:12 cp ppp[802]: tun1: Phase: deflink: opening -> dial Aug 28 04:10:12 cp ppp[802]: tun1: Phase: deflink: dial -> carrier Aug 28 04:10:17 cp ppp[802]: t
Re: i can't get ppp running
The mail server is stripping attachments so you would have to send them as a part of message. You can NOT send attachment to freebsd lists. [EMAIL PROTECTED] wrote: I've read a lot of FreeBSD bridging and DSL router articles, but I still can't get PPPoE running. Topology:mycomp---ed0-FreeBSD-rl0---ADSL_modem---Internet Attached are some of the config and log files from the FreeBSD box. Currenly NAT settings are off. With these settings, in ppp interactive mode, I can't even get the first p capitalized. What could be the problem? From mycomp, I can mount the FreeBSD box's NFS, and get telnet access to the box. Bridging works, as shown: if I have a hardware router between the FreeBSD box and the modem, mycomp gets internet access. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i can't get ppp running
I've read a lot of FreeBSD bridging and DSL router articles, but I still can't get PPPoE running. Topology:mycomp---ed0-FreeBSD-rl0---ADSL_modem---Internet Attached are some of the config and log files from the FreeBSD box. Currenly NAT settings are off. With these settings, in ppp interactive mode, I can't even get the first p capitalized. What could be the problem? From mycomp, I can mount the FreeBSD box's NFS, and get telnet access to the box. Bridging works, as shown: if I have a hardware router between the FreeBSD box and the modem, mycomp gets internet access. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: add route failed for ppp
On 17/07/07 Steve Bertrand said: > What is the next hop for the route you are trying to add? > > This error generally means you have set a next-hop IP address of a > subnet of which you are not directly connected, and either a previous > line in your config(s) set an appropriate route (hisaddr for instance), > or a later line in the process as to make things work. Well, I guess it's supposed to set up my peer as the default gateway. tun0: flags=8051 mtu 1492 inet6 fe80::20a:e6ff:fe4a:56c2%tun0 prefixlen 64 scopeid 0x5 inet6 2001:410:90fc:4:20a:e6ff:fe4a:56c2 prefixlen 64 autoconf inet 216.106.102.70 --> 209.87.255.1 netmask 0x Opened by PID 79728 It's on a different network certainly. But, Internet: DestinationGatewayFlagsRefs Use Netif Expire default209.87.255.1 UGS 0 1276106 tun0 127.0.0.1 127.0.0.1 UH 0 619391lo0 192.168.1 link#1 UC 00 sis0 192.168.1.200:0a:e6:4a:56:c2 UHLW119380lo0 192.168.1.300:20:78:1f:32:55 UHLW1 29836087 sis0816 192.168.1.400:0d:56:6c:2d:0e UHLW1 3042 sis0945 192.168.1.199 00:14:bf:7f:da:42 UHLW1 1307213 sis0 1195 209.87.255.1 216.106.102.70 UH 10 tun0 it did put the default route in place. Perhaps it's just complaining because the route is already there, and ppp restarted. Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpkyHuHwdCyq.pgp Description: PGP signature
Re: add route failed for ppp
Michael P. Soulier wrote: > Hi, > > I'm on an ADSL connection at home, and ppp in BSD is working great. But, I get > this in the logs. > > Jul 16 17:34:54 kanga ppp[79728]: Phase: Pap Input: SUCCESS () > Jul 16 17:34:54 kanga ppp[79728]: Phase: deflink: lcp -> open > Jul 16 17:34:54 kanga ppp[79728]: Phase: bundle: Network > Jul 16 17:34:54 kanga ppp[79728]: Warning: Add! route failed: 0.0.0.0/0: > errno: Network is unreachable > > Now, everything is working fine, but I'm wondering why ppp is complaining > about not being able to set up the route. What is the next hop for the route you are trying to add? This error generally means you have set a next-hop IP address of a subnet of which you are not directly connected, and either a previous line in your config(s) set an appropriate route (hisaddr for instance), or a later line in the process as to make things work. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
add route failed for ppp
Hi, I'm on an ADSL connection at home, and ppp in BSD is working great. But, I get this in the logs. Jul 16 17:34:54 kanga ppp[79728]: Phase: Pap Input: SUCCESS () Jul 16 17:34:54 kanga ppp[79728]: Phase: deflink: lcp -> open Jul 16 17:34:54 kanga ppp[79728]: Phase: bundle: Network Jul 16 17:34:54 kanga ppp[79728]: Warning: Add! route failed: 0.0.0.0/0: errno: Network is unreachable Now, everything is working fine, but I'm wondering why ppp is complaining about not being able to set up the route. Thanks, Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpH5FtceLF0J.pgp Description: PGP signature
Re: ppp/peers/* files
Hmm, would it be easier for me to setup a 127.0.0.2 loopback and my gateway, and alway point that to the proper gateway, to make things easier when I'm switching between VPN and no VPN? Thanks -Jim Stapleton On 6/26/07, Artyom Viklenko <[EMAIL PROTECTED]> wrote: On Tue, 26 Jun 2007, Jim Stapleton wrote: > What man/handbook pages/sections should I look at to get a clue. I'm > so far from having one, I don't even know the direction... see handbook section about networking. simply speaking enter route add ip-of-vpn-server ip-of-your-lan-gateway then start MPD and check is all ok. if yes, you can add this route to /etc/rc.conf using static_routes variable. > > Thanks, > -Jim Stapleton > > On 6/26/07, Artyom Viklenko <[EMAIL PROTECTED]> wrote: >> Jim Stapleton wrote: >> > That partially worked. I could only ping 192.168.1.1 on my local setup >> > (router). >> > >> > I used >> > $ mpd pptp0 >> > >> > However, I couldn't access the work DNS either. The latter output of >> > MPD looked like: >> > == >> > pptp0] IPCP: rec'd Configure Ack #4 link 0 (Ack-Sent) >> > IPADDR >> > [pptp0] IPCP: state change Ack-Sent --> Opened >> > [pptp0] IPCP: LayerUp >> > -> >> > [pptp0] IFACE: Up event >> > [pptp0] setting interface ng0 MTU to 1396 bytes >> > [pptp0] exec: /sbin/ifconfig ng0 netmask >> > 0x -link0 >> > [pptp0] exec: /sbin/route add -iface lo0 >> > [pptp0] exec: /sbin/route add 0.0.0.0 >> > [pptp0] exec: command returned 256 >> > == >> > >> > >> > I could ping and after running mpd, but I >> > could not ping them before running it, or after shutting it down. Both >> > are valid IP addresses on my works internal network. >> > >> > Aside from my nve0 and l0 devices, which look normal, ifconfig >> > displays the following: >> > >> > == >> > ng0: flags=88d1 mtu 1396 >> >inet --> netmask 0x >> > == >> > >> > I could not ping the DNS servers. >> > >> > Any suggestions? >> >> I think you need static route to your VPN server. >> After setting up tullel your default route changes. >> This can lead to incorrect routing. >> >> >> -- >> Sincerely yours, >> Artyom Viklenko. >> --- >> [EMAIL PROTECTED] | http://www.aws-net.org.ua/~artem >> FreeBSD: The Power to Serve - http://www.freebsd.org >> > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Sincerely yours, Artyom Viklenko. --- [EMAIL PROTECTED] | http://www.aws-net.org.ua/~artem FreeBSD: The Power to Serve - http://www.freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Remote login via modem [coda] - PPP
On Sun, May 20, 2007 at 05:54:58PM +1000, Ian Smith wrote: > I'd address this also to [EMAIL PROTECTED], but my prior message evoked: > > On Sun, 20 May 2007 16:02:27 +1000 (EST), Mail Delivery Subsystem wrote: > > > The original message was received at Sun, 20 May 2007 16:02:09 +1000 (EST) > > from [EMAIL PROTECTED] > > > >- The following addresses had permanent fatal errors - > > <[EMAIL PROTECTED]> > > > >- Transcript of session follows - > > ... while talking to mail.metron.com.: > > >>> RCPT To:<[EMAIL PROTECTED]> > > <<< 571 5.0.0 Local Policy REFUSAL: Confirmed network-wide opt-out > > 554 <[EMAIL PROTECTED]>... Service unavailable > > I've not seen a 'Confirmed network-wide opt-out' SMTP response before. > > Any idea what it indicates, apart from the obvious rejection of mail? > > Ian I set my sendmail to issue that in response to some spammer foolishness about opt-in and opt-out and their bogus assertion regarding opting-out of their mailings. What is more to the point is that your message was rejected because your connecting domain, lnk.telstra.net was entered into my local, private, set-and-forget blocklist a long time ago for sending spam. Thank you for attempting to reply to my question, though. [The telstra.net entry in my blocklist has also been removed]. The pointers sent regarding incoming PPP have veen very useful. The last time I set this up I was on a BSDI system, and the protocol was handled by pppd, not the ppp client. I kept looking for pppd related info, and didn't look at the (newer) ppp client pages. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- -=[L]=- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pppoe (userland PPP) and nat 'loopback'
Can this be configured? What I need is a way to go from one LAN machine to the WAN and loopback to the other LAN machine. LAN->WAN->LAN simple pf.conf: binat on $bge1 from 192.168.82.170 to any -> 67.x.x.1 binat on $bge1 from 192.168.82.171 to any -> 67.x.x.2 binat on $bge1 from 192.168.82.172 to any -> 67.x.x.3 binat on $bge1 from 192.168.82.173 to any -> 67.x.x.4 and so on. I need to use 192.168.82.172 to go and connect to public 67.x.x.2 then loop back to 67.x.x.1 Why do I need this? - I run 2 external DNS servers (with views) and as such NS2 needs to talk to NS1 but using the WAN NAT loopbacks. thanks in advance for any tips. -JD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp & dhcp
On Friday 11 May 2007 06:52:08 pm you wrote:
> Hi,
> HISADDR is never offered in the transaction.
> the if for ppp looks like {registered addresss >> private address }
> The transaction should contain 2 registered addresses which are MYADDR and
> HISADDR.
> The latter is never offered. Ever.
> I need to find a way to make either ppp renegotiate the addresses or get
> dhclient to do it at link up.
>
> TCPdump only works on routable addresses at this point my end thinks it has
> a real HISADDR when it has a private addr, you end up with routing
> conflicts because his end is trying to route to my end of the pipe which
> has a completly different address.
>
> Windows which uses dhcp with it's ppp implementation has to renegotiate as
> well.
>
> BSD ppp has the dhcp client inbuilt.
>
> John
> - Original Message -
> From: "WizLayer" <[EMAIL PROTECTED]>
> To:
> Sent: Saturday, May 12, 2007 10:12 AM
> Subject: Re: ppp & dhcp
I seriously doubt you'll be able to get dhcp client to work that way unless
you apply some really ugly hacks to it. :) ppp uses IPCP. See link for
more details:
http://www.networksorcery.com/enp/protocol/IPCP.htm
Nobody on this list can really guess very well at what your setup is. If
you're looking for more specific advice, we need something to work with.
Is this PPOE? Dial-up? Do the logs show anything? What does your ppp.conf
look like? When you ppp manually and connect, are you able to get a
renegotiation with 'add! default HISADDR'? (I'm pretty sure it's a '!' for a
forced renegotiation if_exist, anyway).
I've had my share of brain-dead ISP "techs" too. If it's not on the
flow-chart they follow when they're talking to you, they're completely lost.
It's almost funny. :)
WizLayer
--
Life is better with a BSD.
For more info, www.bsd.org.
pgpTrMvz8W2D7.pgp
Description: PGP signature
Re: ppp & dhcp
On Friday 11 May 2007 05:53:18 pm Mulga wrote: > Hi, > I have a very brain dead and full of them self ISP who insist on having a > misconfigured dhcp server. > > One essential peice of infomation is missing from the ppp transaction > "HISADDR" the GW . > > As ppp handles the dhcp side of things internally, would anyone like to > suggest a way of getting the server to reveal its address. > > To date I have tried running dhclient after the linkup, telling the ISP he > had a small inconsistancy, and got a ear full of abuse for that. > > As this provider "Telstra AU" is the only provider of this service I can't > change. So I need to work around there problem. > > Regards John I'm not sure what you are getting at. Are you saying that the HISADDR in ppp doesn't work because of your ISPs configuration? Or are you saying that you're looking for your ISPs specifics for setup purposes? You could try a tcpdump on your if while connecting (or trying to connect). That should give you an idea of whats going on. whois, arpinfo...? HTH WizLayer -- Life is better with a BSD. For more info, www.bsd.org. pgph4jQCSnbAG.pgp Description: PGP signature
ppp & dhcp
Hi, I have a very brain dead and full of them self ISP who insist on having a misconfigured dhcp server. One essential peice of infomation is missing from the ppp transaction "HISADDR" the GW . As ppp handles the dhcp side of things internally, would anyone like to suggest a way of getting the server to reveal its address. To date I have tried running dhclient after the linkup, telling the ISP he had a small inconsistancy, and got a ear full of abuse for that. As this provider "Telstra AU" is the only provider of this service I can't change. So I need to work around there problem. Regards John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
Are you using the -ddial option? if you start ppp through rc.conf add ppp_mode="ddial" Yes, I was originally using it. Bob said that my rc.conf was obsolete, but he did not say why. Laszo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
On Thu, 10 May 2007 10:12:00 +0200 Nagy László Zsolt <[EMAIL PROTECTED]> wrote: > > > > >> The format of the statement to add > >> is ifconfig_=up where is the NIC's FBSD interface name > >> used by PPPoE that you specified in the /etc/ppp/ppp.conf file. > >> ee /etc/rc.conf # add following statements > >> ifconfig_=up > >> > > > > I've not needed to do this, > > > > > >> ifconfig_tun0="DHCP"# get your ISP assigned IP address > >> > > > > PPP has its own mechanism for getting an IP address and dns server > > addresses. You don't normally need to specify DHCP for the > > interface. > I'm now totally confused. I tried this configuration also, but the > connection still drops in every 3 hours. Can it be a problem with the > ISP? I'm going to do a stress test with another computer to see if > the ADSL line is stable or not. > Are you using the -ddial option? if you start ppp through rc.conf add ppp_mode="ddial" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
The format of the statement to add is ifconfig_=up where is the NIC's FBSD interface name used by PPPoE that you specified in the /etc/ppp/ppp.conf file. ee /etc/rc.conf # add following statements ifconfig_=up I've not needed to do this, ifconfig_tun0="DHCP"# get your ISP assigned IP address PPP has its own mechanism for getting an IP address and dns server addresses. You don't normally need to specify DHCP for the interface. I'm now totally confused. I tried this configuration also, but the connection still drops in every 3 hours. Can it be a problem with the ISP? I'm going to do a stress test with another computer to see if the ADSL line is stable or not. Regards, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
On Mon, 7 May 2007 10:25:20 -0400 "Bob" <[EMAIL PROTECTED]> wrote: > The format of the statement to add > is ifconfig_=up where is the NIC's FBSD interface name used > by PPPoE that you specified in the /etc/ppp/ppp.conf file. > ee /etc/rc.conf # add following statements > ifconfig_=up I've not needed to do this, > ifconfig_tun0="DHCP"# get your ISP assigned IP address PPP has its own mechanism for getting an IP address and dns server addresses. You don't normally need to specify DHCP for the interface. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
Bob írta: The method you are using is obsolete. The following is all you need. Take special note of rc.conf statements to use. start of DSL ppp.conf ### default: set log Phase tun #use to avoid excessive log sizes set timeout 0 # no idle time out, will not disconnect dialisp: set device PPPoE:XXX # replace xxx with your NIC device name set authname YOURLOGINNAME# Replace with your ISP account username set authkey YOURPASSWORD # Replace with your ISP account password add default HISADDR # Add a (sticky) default route (Mandatory) enable dns # Gets the ISP's DNS IP address & places them # in resolv.conf for reference by FBSD box. ### End of DSL ppp.conf # Replace the XXX in the [set device PPPoE:XXX] statement with the NIC's FBSD interface name. Sometimes it will be necessary to use a service tag to establish your connection depending on how your ISP and/or the phone company has its DSL network configured. Service tags are used to distinguish between different PPPoE servers attached to a given network. You should have been given any required service tag information in the documentation provided by your ISP. If you cannot locate it there, ask your ISP's tech support personnel. This is the format of the command with the service tag added: set device PPPoE::service_tag The is the FBSD interface name used by PPPoE. The interface must be UP (IE: enabled). It is only used as a transport, and does not need to be assigned an IP address. This can be done automatically at boot time by updating the /etc/rc.conf file. The format of the statement to add is ifconfig_=up where is the NIC's FBSD interface name used by PPPoE that you specified in the /etc/ppp/ppp.conf file. ee /etc/rc.conf # add following statements ifconfig_=up ifconfig_tun0="DHCP"# get your ISP assigned IP address Dear Bob, I installed a new OS (release 6.1) just for testing ADSL so others can work. What you wrote works fine, except that I had to use "papchap" label instead of "dialisp" and I also had to include ppp_enable="YES" in /etc/rc.conf. Now my only question is that, why my configuration was obsolete? I noticed that the example file installed by default is from 1999. :-) Thanks, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp is broken???
Bob wrote: The method you are using is obsolete. The following is all you need. Take special note of rc.conf statements to use. start of DSL ppp.conf ### default: set log Phase tun #use to avoid excessive log sizes set timeout 0 # no idle time out, will not disconnect dialisp: set device PPPoE:XXX # replace xxx with your NIC device name set authname YOURLOGINNAME# Replace with your ISP account username set authkey YOURPASSWORD # Replace with your ISP account password add default HISADDR # Add a (sticky) default route (Mandatory) enable dns # Gets the ISP's DNS IP address & places them Thank you, Bob. You have been very helpful. Right now about 10 people are using this computer (with the backup connection, that one uses DHCP). I can only try this tomorrow, but I'll write about the results. Thanks again Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ppp is broken???
The method you are using is obsolete. The following is all you need. Take special note of rc.conf statements to use. start of DSL ppp.conf ### default: set log Phase tun #use to avoid excessive log sizes set timeout 0 # no idle time out, will not disconnect dialisp: set device PPPoE:XXX # replace xxx with your NIC device name set authname YOURLOGINNAME# Replace with your ISP account username set authkey YOURPASSWORD # Replace with your ISP account password add default HISADDR # Add a (sticky) default route (Mandatory) enable dns # Gets the ISP's DNS IP address & places them # in resolv.conf for reference by FBSD box. ### End of DSL ppp.conf # Replace the XXX in the [set device PPPoE:XXX] statement with the NIC's FBSD interface name. Sometimes it will be necessary to use a service tag to establish your connection depending on how your ISP and/or the phone company has its DSL network configured. Service tags are used to distinguish between different PPPoE servers attached to a given network. You should have been given any required service tag information in the documentation provided by your ISP. If you cannot locate it there, ask your ISP's tech support personnel. This is the format of the command with the service tag added: set device PPPoE::service_tag The is the FBSD interface name used by PPPoE. The interface must be UP (IE: enabled). It is only used as a transport, and does not need to be assigned an IP address. This can be done automatically at boot time by updating the /etc/rc.conf file. The format of the statement to add is ifconfig_=up where is the NIC's FBSD interface name used by PPPoE that you specified in the /etc/ppp/ppp.conf file. ee /etc/rc.conf # add following statements ifconfig_=up ifconfig_tun0="DHCP"# get your ISP assigned IP address -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nagy László Zsolt Sent: Monday, May 07, 2007 8:53 AM To: [EMAIL PROTECTED]; freebsd-questions@freebsd.org Subject: Re: ppp is broken??? Bob wrote: > Add these statements to the end of your ppp.conf file. > > > > disable iface-alias # Stop adding old IP address as alias when ppp ># redials because line was lost. These old IPs ># showed using ifconfig -a on tun0. > > # Remove all previous IP address > I'll try this. > Post contents of your ppp.conf and rc.conf files for review for why you > keep losing your connection. > ppp.conf: papchap: # set log Phase Chat LCP IPCP CCP tun command set log phase tun command set device PPPoE:rl0 set speed sync set mru 1492 set mtu 1492 set ctsrts off set dial set login enable lqr add default HISADDR # enable dns # I use my own DNS server (named) enable tcpmssfixup # non-default below (hack for pptpd) set authname [EMAIL PROTECTED] set authkey i_am_not_telling_this nat enable yes nat port tcp 172.16.0.48:3389 51234 rc.conf: allscreens="80x30" font8x14="iso02-8x14" font8x16="iso02-8x16" font8x8="iso02-8x8" keymap="hu.iso2.102keys" keyrate="fast" scrnmap="iso-8859-1_to_cp437" gateway_enable="YES" hostname="not_telling.dyndns.org" ifconfig_vr0="inet 172.16.0.1 netmask 255.255.240.0" firewall_enable="YES" firewall_type="OPEN" firewall_logging="YES" # ADSL ppp_enable="YES" ppp_mode="ddial" ppp_nat="YES" named_enable="YES" kern_securelevel=2 kern_securelevel_enable="NO" saver="logo" sshd_enable="YES" usbd_enable="NO" moused_enable="YES" moused_port="/dev/psm0" moused_type="auto" apache2_enable="YES" apache2ssl_enable="YES" squid_enable="NO" mysql_enable="NO" postgresql_enable="YES" rpcbind_enable="YES" nfs_server_enable="YES" nfs_reserved_port_only="YES" mountd_flags="-r" inetd_enable="YES" dovecot_enable="YES" gdm_enable="YES" dhcpd_enable="YES" dhcpd_ifaces="vr0" tomcat50_enable="YES" samba_enable="YES" slapd_enable="YES" slapd_flags=' -h "ldap://127.0.0.1/ ldaps://0.0.0.0/"' #postfix_enable="YES" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
