RE: [pfSense Support] MAC ADDRESS
Suresh, Please clarify your question. Are you asking about MAC cloning or something else? Chris From: suresh suresh [mailto:suresh.notion...@gmail.com] Sent: Tuesday, August 16, 2011 3:35 PM To: support@pfsense.com Subject: [pfSense Support] MAC ADDRESS HI, how to add the mac address please help me thank you,
RE: [pfSense Support] Imspector
Cleber, I've always configured the imspector package to log to a remote mysql server. IMSpector is also capable of logging to a local SQLite database, but I don't know whether the pfSense package has implemented this. Chris From: Cleber L. Medina [mailto:clebermed...@gmail.com] Sent: Tuesday, August 16, 2011 1:38 PM To: support@pfsense.com Subject: [pfSense Support] Imspector I´m using a imspector 0.9-4, my pfsense is 2.0-RC3 (amd64) , but it log nothing, I just set "Enable IMSpector" I need to set other option? I need to use a mysql server? How I install mysql on a pfsense machine? Thanks Cleber
RE: [pfSense Support] To integrate AD users to specific rule groups
Isamar, The captive portal in m0n0wall/pfSense isn’t capable of direct LDAP queries, unless something has changed recently. However, it is capable of RADIUS authentication. Since you have an Active Directory environment, it’s a trivial matter to setup IAS (2003) or NPS (2008) to handle RADIUS requests on one of your domain controllers. I’m not aware of a method to accomplish item two. Chris From: Isamar Maia [mailto:isa...@gmail.com] Sent: Saturday, July 30, 2011 7:15 AM To: support@pfsense.com Subject: [pfSense Support] To integrate AD users to specific rule groups Hi Folks, Is there any way with PfSense to integrate AD authenticated users with rules groups. I mean, we wish to: 1) Integrate the Captive portal functionality to authenticate users to the Windows AD server 2) Attach specific users to specific firewall and squid filtering rules. Like: HR departament users can access only HR related sites,etc. Is that currently possible ? -- Isamar Maia Cel. VIVO SSA: (55) 71-9146-8575 Cel. TIM SSA: (55) 71-9185-5264 Fixo: (55) 71-4062-8688 日本: +81-(0)3-4550-1212 Skype ID: isamar.maia
RE: [pfSense Support] pfSense change logging
Authentication events should be recorded in the system log. -Original Message- From: Scott Benson [mailto:sben...@a-1networks.com] Sent: Friday, July 29, 2011 11:41 AM To: support@pfsense.com Subject: [pfSense Support] pfSense change logging Is there a way to see who(based on IP) made a change to the webgui causing a new /cf/conf/backup/ to be created? is it something in that file, or logged anywhere? -- Scott Benson A1 Networks (707)570-2021 x203 - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] how to make dvd
Nick, The image file you downloaded is to be written to a 1 GB flash card, not a DVD. This is the file which is to be written to optical media: ftp://reflection.ncsa.uiuc.edu/pub/pfSense/downloads/pfSense-2.0-RC3-i386-20110621-1650.iso.gz However, it hardly warrants a DVD, since it won't even occupy an entire CD. From: Nick Upson [mailto:n...@telensa.com] Sent: Friday, July 29, 2011 11:03 AM To: support pfsense Subject: [pfSense Support] how to make dvd I know I'm not totally daft but this is getting me stuck right now, I've downloaded pfSense-2.0-RC3-1g-i386-20110621-1821-nanobsd.img.gz and gunzipped it but how do I make that .img into a DVD (dvd writers available are on winXP or WIN7) -- Nick Upson (01799 533252)
RE: [pfSense Support] Fwd: GB-1200
Brian, Have you tried the method to resolve such an issue described here: http://forum.pfsense.org/index.php?topic=21194.msg109995#msg109995 ? If you haven't and have a spare pfSense/FreeBSD box, give it a try. -Original Message- From: Brian Henson [mailto:marin...@gmail.com] Sent: Friday, July 29, 2011 2:45 AM To: support@pfsense.com Subject: [pfSense Support] Fwd: GB-1200 I have a problem booting both 1.2.3 and 2.0 rc3 on the GB-1200. It hangs each time on Trying to mount root from ufs:/dev/ufs/pfsense0. below is the boot log up until that point. thank you in advance 1 FreeBSD 2 FreeBSD Boot: 1 /boot.config: -h Consoles: serial port BIOS drive C: is disk0 BIOS 639kB/129984kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org, Mon Dec 7 23:00:35 EST 2009) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x739788 data=0x13cf6c+0x51c80 / \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE-p5 #0: Mon Dec 7 23:21:27 EST 2009 sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.7.i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(TM) CPU 1200MHz (1196.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 134152192 (127 MB) avail memory = 117354496 (111 MB) wlan: mac acl policy registered cryptosoft0: on motherboard padlock0: No ACE support. acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7ef (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x40f7 on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on pci0 pci2: on pcib2 fxp0: port 0xa800-0xa83f mem 0xd7081000-0xd7081fff,0xd704-0xd705 irq 12 at device 4.0 on pci2 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:d0:68:04:a4:0e fxp0: [ITHREAD] fxp1: port 0xa000-0xa03f mem 0xd708-0xd7080fff,0xd700-0xd701 irq 11 at device 5.0 on pci2 miibus1: on fxp1 inphy1: PHY 1 on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:d0:68:04:a4:0f fxp1: [ITHREAD] fxp2: port 0xa400-0xa43f mem 0xd7083000-0xd7083fff,0xd702-0xd703 irq 10 at device 6.0 on pci2 miibus2: on fxp2 inphy2: PHY 1 on miibus2 inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp2: Ethernet address: 00:d0:68:04:a4:10 fxp2: [ITHREAD] pcib3: at device 7.0 on pci2 pci3: on pcib3 dc0: port 0x9000-0x907f mem 0xd600-0xd60003ff irq 10 at device 4.0 on pci3 miibus3: on dc0 ukphy0: PHY 1 on miibus3 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:50:c2:11:ff:5f dc0: [ITHREAD] dc1: port 0x9400-0x947f mem 0xd6001000-0xd60013ff irq 9 at device 5.0 on pci3 miibus4: on dc1 ukphy1: PHY 1 on miibus4 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc1: Ethernet address: 00:50:c2:11:ff:60 dc1: [ITHREAD] dc2: port 0x9800-0x987f mem 0xd6002000-0xd60023ff irq 12 at device 6.0 on pci3 miibus5: on dc2 ukphy2: PHY 1 on miibus5 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc2: Ethernet address: 00:50:c2:11:ff:61 dc2: [ITHREAD] dc3: port 0x9c00-0x9c7f mem 0xd6003000-0xd60033ff irq 11 at device 7.0 on pci3 miibus6: on dc3 ukphy3: PHY 1 on miibus6 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc3: Ethernet address: 00:50:c2:11:ff:62 dc3: [ITHREAD] fxp3: port 0xac00-0xac3f mem 0xd7082000-0xd7082fff,0xd706-0xd707 irq 9 at device 10.0 on pci2 miibus7: on fxp3 inphy3: PHY 1 on miibus7 inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp3: Ethernet address: 00:d0:68:04:a4:11 fxp3: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] uhci0: port 0xb000-0xb01f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb400-0xb41f irq 5 at device 31.4 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered acpi_tz
RE: [pfSense Support] RE: (Update) Pantech UML290
Thanks Adam, I'm not attempting to use this in a multilink setup; just as the primary WAN interface. -Original Message- From: Adam Thompson [mailto:athom...@athompso.net] Sent: Sunday, July 24, 2011 3:58 PM To: support@pfsense.com Subject: RE: [pfSense Support] RE: (Update) Pantech UML290 > -Original Message- > From: Chris Clark [mailto:ch...@belthasar.com] > Sent: Sunday, July 24, 2011 14:47 > To: support@pfsense.com > Subject: [pfSense Support] RE: (Update) Pantech UML290 > > After reading the last two posts in this thread: > http://forum.pfsense.org/index.php?topic=28649.0 > I'm fairly certain that the problem displayed in the logs below is > also due the problem described with mpd. However, I've noticed that > there are two different mpd binaries present in > /usr/local/sbin: > -r-xr-xr-x 1 root wheel 460256 Jun 21 16:51 mpd4 > -r-xr-xr-x 1 root wheel 519364 Jun 21 16:51 mpd5 > > Does anyone know which one is being used and from where it's called? Based on ermal's post to that thread, I would presume 2.0 uses mpd5, and I would also presume that the fix will make it into a snapshot in the very near future. I don't think fixing mpd5 could fix the kernel overflow problem suggested elsewhere, however, so I suggest you not try to use this in a multilink setup for now. -Adam Thompson athom...@athompso.net - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] RE: (Update) Pantech UML290
After reading the last two posts in this thread: http://forum.pfsense.org/index.php?topic=28649.0 I'm fairly certain that the problem displayed in the logs below is also due the problem described with mpd. However, I've noticed that there are two different mpd binaries present in /usr/local/sbin: -r-xr-xr-x 1 root wheel 460256 Jun 21 16:51 mpd4 -r-xr-xr-x 1 root wheel 519364 Jun 21 16:51 mpd5 Does anyone know which one is being used and from where it's called? -Original Message----- From: Chris Clark [mailto:ch...@belthasar.com] Sent: Sunday, July 24, 2011 12:34 PM To: support@pfsense.com Subject: [pfSense Support] Pantech UML290 Greetings everyone, I bought a Pantech UML290 for Verizon's LTE service yesterday and have been attempting to get it working with pfSense 2.0RC3 since then. This morning I've been able to get connection established, but something in pfSense immediately terminates it, citing an invalid argument. This is my procedure and what I've had to do: Configuration (with UML290 connected): Comment out this line in /usr/local/mpd.script: set $modemCmd "+CGDCONT=$APNum, \"IP\", \"$APN\" Go through this procedure here: http://doc.pfsense.org/index.php/Configuring_3G_modems Enter Username: [Number]@vzw4g.com Enter Password: vzw Phone Number: *99***3# Add PPP interface to WAN/OPT1 and leave interface disabled. Procedure: Connect UML290 to a Windows box running VZAM and establish connection there. Remove from Windows box and connect to pfSense box. Enable WAN/OPT1 interface. I then see the following in the logs (taken from both WAN and OPT1 association tries)(also attached): Jul 24 08:24:26 ppp: [opt1_link0] chat: Connected at 1. Jul 24 08:24:26 ppp: [opt1_link0] MODEM: chat script succeeded Jul 24 08:24:26 ppp: [opt1_link0] Link: UP event Jul 24 08:24:26 ppp: [opt1_link0] LCP: Up event Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Starting --> Req-Sent Jul 24 08:24:26 ppp: [opt1_link0] LCP: SendConfigReq #1 Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x000a Jul 24 08:24:26 ppp: [opt1_link0] MRU 1500 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM 72df4860 Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Configure Request #0 (Req-Sent) Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x Jul 24 08:24:26 ppp: [opt1_link0] AUTHPROTO CHAP MD5 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM cf64b9c6 Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] LCP: SendConfigAck #0 Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x Jul 24 08:24:26 ppp: [opt1_link0] AUTHPROTO CHAP MD5 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM cf64b9c6 Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Req-Sent --> Ack-Sent Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Configure Ack #1 (Ack-Sent) Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x000a Jul 24 08:24:26 ppp: [opt1_link0] MRU 1500 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM 72df4860 Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Ack-Sent --> Opened Jul 24 08:24:26 ppp: [opt1_link0] LCP: auth: peer wants CHAP, I want nothing Jul 24 08:24:26 ppp: [opt1_link0] LCP: LayerUp Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Discard Request #1 (Opened) Jul 24 08:24:26 ppp: [opt1_link0] CHAP: rec'd CHALLENGE #1 len: 35 Jul 24 08:24:26 ppp: [opt1_link0] Name: "UMTS_CHAP_SRVR" Jul 24 08:24:26 ppp: [opt1_link0] CHAP: Using authname "8035221...@vzw4g.com" Jul 24 08:24:26 ppp: [opt1_link0] CHAP: sending RESPONSE #1 len: 41 Jul 24 08:24:26 ppp: [opt1_link0] CHAP: rec'd SUCCESS #1 len: 4 Jul 24 08:24:26 ppp: [opt1_link0] LCP: authorization successful Jul 24 08:24:26 ppp: [opt1_link0] Link: Matched action 'bundle "opt1" ""' Jul 24 08:24:26 ppp: [opt1_link0] Link: Join bundle "opt1" Jul 24 08:24:26 ppp: [opt1] Bundle: Status update: up 1 link, total bandwidth 1 bps Jul 24 08:24:26 ppp: [opt1] can't config [21]:: Invalid argument Jul 24 08:24:26 ppp: fatal error, exiting Jul 24 08:24:26 ppp: [opt1] IFACE: Close event Jul 24 08:24:26 ppp: [opt1] IPCP: Close event Jul 24 08:24:26 ppp: [opt1] Bundle: Shutdown Jul 24 08:24:26 ppp: [opt1_link0] Link: S
[pfSense Support] Pantech UML290
Greetings everyone, I bought a Pantech UML290 for Verizon's LTE service yesterday and have been attempting to get it working with pfSense 2.0RC3 since then. This morning I've been able to get connection established, but something in pfSense immediately terminates it, citing an invalid argument. This is my procedure and what I've had to do: Configuration (with UML290 connected): Comment out this line in /usr/local/mpd.script: set $modemCmd "+CGDCONT=$APNum, \"IP\", \"$APN\" Go through this procedure here: http://doc.pfsense.org/index.php/Configuring_3G_modems Enter Username: [Number]@vzw4g.com Enter Password: vzw Phone Number: *99***3# Add PPP interface to WAN/OPT1 and leave interface disabled. Procedure: Connect UML290 to a Windows box running VZAM and establish connection there. Remove from Windows box and connect to pfSense box. Enable WAN/OPT1 interface. I then see the following in the logs (taken from both WAN and OPT1 association tries)(also attached): Jul 24 08:24:26 ppp: [opt1_link0] chat: Connected at 1. Jul 24 08:24:26 ppp: [opt1_link0] MODEM: chat script succeeded Jul 24 08:24:26 ppp: [opt1_link0] Link: UP event Jul 24 08:24:26 ppp: [opt1_link0] LCP: Up event Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Starting --> Req-Sent Jul 24 08:24:26 ppp: [opt1_link0] LCP: SendConfigReq #1 Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x000a Jul 24 08:24:26 ppp: [opt1_link0] MRU 1500 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM 72df4860 Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Configure Request #0 (Req-Sent) Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x Jul 24 08:24:26 ppp: [opt1_link0] AUTHPROTO CHAP MD5 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM cf64b9c6 Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] LCP: SendConfigAck #0 Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x Jul 24 08:24:26 ppp: [opt1_link0] AUTHPROTO CHAP MD5 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM cf64b9c6 Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Req-Sent --> Ack-Sent Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Configure Ack #1 (Ack-Sent) Jul 24 08:24:26 ppp: [opt1_link0] ACFCOMP Jul 24 08:24:26 ppp: [opt1_link0] PROTOCOMP Jul 24 08:24:26 ppp: [opt1_link0] ACCMAP 0x000a Jul 24 08:24:26 ppp: [opt1_link0] MRU 1500 Jul 24 08:24:26 ppp: [opt1_link0] MAGICNUM 72df4860 Jul 24 08:24:26 ppp: [opt1_link0] LCP: state change Ack-Sent --> Opened Jul 24 08:24:26 ppp: [opt1_link0] LCP: auth: peer wants CHAP, I want nothing Jul 24 08:24:26 ppp: [opt1_link0] LCP: LayerUp Jul 24 08:24:26 ppp: [opt1_link0] LCP: rec'd Discard Request #1 (Opened) Jul 24 08:24:26 ppp: [opt1_link0] CHAP: rec'd CHALLENGE #1 len: 35 Jul 24 08:24:26 ppp: [opt1_link0] Name: "UMTS_CHAP_SRVR" Jul 24 08:24:26 ppp: [opt1_link0] CHAP: Using authname "8035221...@vzw4g.com" Jul 24 08:24:26 ppp: [opt1_link0] CHAP: sending RESPONSE #1 len: 41 Jul 24 08:24:26 ppp: [opt1_link0] CHAP: rec'd SUCCESS #1 len: 4 Jul 24 08:24:26 ppp: [opt1_link0] LCP: authorization successful Jul 24 08:24:26 ppp: [opt1_link0] Link: Matched action 'bundle "opt1" ""' Jul 24 08:24:26 ppp: [opt1_link0] Link: Join bundle "opt1" Jul 24 08:24:26 ppp: [opt1] Bundle: Status update: up 1 link, total bandwidth 1 bps Jul 24 08:24:26 ppp: [opt1] can't config [21]:: Invalid argument Jul 24 08:24:26 ppp: fatal error, exiting Jul 24 08:24:26 ppp: [opt1] IFACE: Close event Jul 24 08:24:26 ppp: [opt1] IPCP: Close event Jul 24 08:24:26 ppp: [opt1] Bundle: Shutdown Jul 24 08:24:26 ppp: [opt1_link0] Link: Shutdown Jul 24 08:24:26 ppp: process 38992 terminated Jul 24 08:32:35 ppp: [wan_link0] chat: Connected at 1. Jul 24 08:32:35 ppp: [wan_link0] MODEM: chat script succeeded Jul 24 08:32:35 ppp: [wan_link0] Link: UP event Jul 24 08:32:35 ppp: [wan_link0] LCP: Up event Jul 24 08:32:35 ppp: [wan_link0] LCP: state change Starting --> Req-Sent Jul 24 08:32:35 ppp: [wan_link0] LCP: SendConfigReq #1 Jul 24 08:32:35 ppp: [wan_link0] ACFCOMP Jul 24 08:32:35 ppp: [wan_link0] PROTOCOMP Jul 24 08:32:35 ppp: [wan_link0] ACCMAP 0x000a Jul 24 08:32:35 ppp: [wan_link0] MRU 1500 Jul 24 08:32:35 ppp: [wan_link0] MAGICNUM 24c14c1c Jul 24 08:32:35 ppp: [wan_link0] LCP: rec'd Configure Request #0 (Req-Sent) Jul 2
