http://localhost/phpmyadmin
___ 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: pppoe configuration and dns name resolution
On 16 Oct 2012, at 16:08, Jack jacks.1...@gmail.com wrote: Hi I'm new as a FreeBSD user, and trying to configure my pppoe connection. [snip] fxp0 is the ethernet interface of my PC via which adsl modem is connected. Any suggestions ... Consider using the ports mpd5 daemon for a PPPoE connection instead. I had a lot of trouble getting PPPoE to work with userland 'ppp', but mpd5 worked fine. - Mark ___ 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: pppoe configuration and dns name resolution
On Tue, Oct 16, 2012 at 8:49 PM, Mark Blackman m...@exonetric.com wrote: On 16 Oct 2012, at 16:08, Jack jacks.1...@gmail.com wrote: Hi I'm new as a FreeBSD user, and trying to configure my pppoe connection. [snip] fxp0 is the ethernet interface of my PC via which adsl modem is connected. Any suggestions ... Consider using the ports mpd5 daemon for a PPPoE connection instead. I had a lot of trouble getting PPPoE to work with userland 'ppp', but mpd5 worked fine. - Mark I 'll try mpd5. Thanks. Actually, I was concerned with userland ppp, becoz of the scenarios where we have a FreeBSD machine and the only way to connect to internet is an adsl modem in bridge mode (assuming the mode in modem, can't be changed). In such case the only utilty is ppp, which can be of help. I'm using FreeBSD 9.1 RC-2. Regards -- Jack ___ 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: pppoe configuration and dns name resolution
On 16 Oct 2012, at 16:38, Jack jacks.1...@gmail.com wrote: I 'll try mpd5. Thanks. Actually, I was concerned with userland ppp, becoz of the scenarios where we have a FreeBSD machine and the only way to connect to internet is an adsl modem in bridge mode (assuming the mode in modem, can't be changed). In such case the only utilty is ppp, which can be of help. Ok, usually bridge mode implies PPPoE and mpd5 does PPPoE. Maybe I'm missing your point. - Mark ___ 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: pppoe configuration and dns name resolution
On 16 Oct 2012, at 16:49, Mark Blackman m...@exonetric.com wrote: On 16 Oct 2012, at 16:38, Jack jacks.1...@gmail.com wrote: I 'll try mpd5. Thanks. Actually, I was concerned with userland ppp, becoz of the scenarios where we have a FreeBSD machine and the only way to connect to internet is an adsl modem in bridge mode (assuming the mode in modem, can't be changed). In such case the only utilty is ppp, which can be of help. Ok, usually bridge mode implies PPPoE and mpd5 does PPPoE. Maybe I'm missing your point. More accurately, bridge mode (on the modem) means your FreeBSD box will need to be the termination point of the PPPoE link rather than the modem itself and so you need to run something to terminate the PPPoE packets and mpd5 will do that (among other things). - Mark ___ 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
clang options question
From looking at the clang(1) man page, it is not clear to me what the difference is between the -arch option and the -march= option. Would someone please summarize the difference(s) for me? Thanks much! Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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: pppoe configuration and dns name resolution
On Tue 2012-10-16 20:38:47 UTC+0530, Jack (jacks.1...@gmail.com) wrote: I'm new as a FreeBSD user, and trying to configure my pppoe connection. After reading handbook and searching on various forums, I prepared the ppp.conf file, and tried starting the ppp via # ppp -ddial adsl Here 'adsl' is the profile name, in /etc/ppp/ppp.conf. I also tried #ppp -auto adsl but the error message was same. ... I use a similar setup here except I use static IPs for both the ADSL modem (in bridge mode) and the FreeBSD box connecting to it. The FreeBSD box then runs a DHCP server (dns/dnsmasq in ports) for any other machines on my LAN to talk to. I'm pasting my related configuration files if they can help. Please tell me if any other files are needed. Nothing really stands out glancing at your configs. I'd be looking for clues in /var/log/ppp.log. tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL Opened by PID 1907 tun0 should have been reassigned a public address here by the remote PPP host (your ISP). Also the MTU is still stuck at 1500 despite you correctly configuring 1492 in ppp.conf. So I think the PPP negotiation is failing. ppp.log may explain why. Mine looks like this: tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1492 options=8LINKSTATE inet 58.6.247.132 -- 203.215.15.252 netmask 0x Opened by PID 45904 Below is my (edited) rc.conf ppp.conf. I simply start stop the PPP session with service ppp start service ppp stop as root. ## /etc/rc.conf hostname=blizzard.phoenix ifconfig_bge0=inet 192.168.1.4 netmask 255.255.255.0 zfs_enable=YES syslogd_flags=-c gateway_enable=YES sshd_enable=YES inetd_enable=YES fusefs_enable=YES openntpd_enable=YES dovecot_enable=YES named_enable=NO dnsmasq_enable=YES postfix_enable=YES sendmail_enable=NO sendmail_submit_enable=NO sendmail_outbound_enable=NO sendmail_msp_queue_enable=NO ppp_enable=YES ppp_mode=ddial ppp_nat=YES ppp_profile=iinet firewall_enable=YES firewall_script=/etc/ipfw.rules firewall_logging=YES ## /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 myusername set authkey mypassword set dial set login set mru 1492 set mtu 1492 set redial 15 0 add default HISADDR ___ 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: 0
1 On 10/15/12, abdou massnoue abdoumassnoue2...@gmail.com wrote: ___ 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: IPCS resource access within a down-level jail?
David Wolfskill wrote: [Please include me in responses; I've set Reply-To as a hint. Thanks!] A colleague had been running a program that makes use of IPCS message queues in a 7.x/i386 environment. He was moved to a 32-bit 7.x-based jail instantiated on an 8.x/amd64 host. Within that jail, ipcs -a now fails to come anywhere near close to reporting what it does outside the jail. I then performed an experiment: I created a 7.x/i386 jail on my 9.x/i386 laptop. I verified that ipcs -a (outside the jail) shows Stuff: d134(9.1-P)[1] ipcs -a Message Queues: T ID KEY MODEOWNERGROUPCREATOR CGROUP CBYTES QNUM QBYTESLSPIDLRPID STIMERTIMECTIME Shared Memory: T ID KEY MODEOWNERGROUPCREATOR CGROUP NATTCHSEGSZ CPID LPID ATIMEDTIMECTIME m 3932160 --rw--- daviddaviddaviddavid 2 393216 3671 3147 8:23:37 no-entry 8:23:37 m 8519690 --rw--- daviddaviddaviddavid 2 262080 3861 3147 9:24:09 no-entry 9:24:09 m 4587540 --rw--- daviddaviddaviddavid 2 384000 3861 3147 9:24:09 no-entry 9:24:09 Semaphores: T ID KEY MODEOWNERGROUPCREATOR CGROUP NSEMS OTIMECTIME d134(9.1-P)[2] Inside the jail, using the 7.x version of ipcs, I get: %ipcs -a ipcs: sysctlbyname: kern.ipc.msqids: Cannot allocate memory % I then recompiled the 9.x versions of ipcs ipcrm and linked them statically; running that verion of ipcs, I see: %~/bin/!! ~/bin/ipcs -a Message Queues: T ID KEY MODEOWNERGROUPCREATOR CGROUP CBYTES QNUM QBYTESLSPIDLRPID STIMERTIMECTIME Shared Memory: T ID KEY MODEOWNERGROUPCREATOR CGROUP NATTCHSEGSZ CPID LPID ATIMEDTIMECTIME m 3932160 --rw--- daviddaviddaviddavid 2 393216 3671 3147 15:23:37 no-entry 15:23:37 m 6553620 --rw--- daviddaviddaviddavid 2 262080 3861 3147 18:39:30 no-entry 18:39:30 Semaphores: T ID KEY MODEOWNERGROUPCREATOR CGROUP NSEMS OTIMECTIME % Is this (inability to access IPCS resources properly within a down-level jail) expected behavior? Is there a sane(?) way to provide IPCS resources inside a down-level jail? Thanks! Peace, david Your problem is in the way you are trying to use jails. The jail has to be at the same major release level as the host. Host being 9.2 with a jail at 9.0 may work. But 9.x or 8.x host with 7.x jail for sure will not work. ___ 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: Fetched Ports index falling out of date
On 17/10/2012 09:10, Paul Macdonald wrote: For the past 4 days or so, i have noticed an issue where the ports INDEX is out of date. Yes, the published INDEX-n files (for make fetchindex) haven't been updated since Saturday. ozsrv03 curl -I http://www.FreeBSD.org/ports/INDEX-8.bz2 HTTP/1.1 200 OK Content-Type: application/x-bzip Accept-Ranges: bytes ETag: 3485320067 Last-Modified: Sat, 13 Oct 2012 09:05:08 GMT Content-Length: 1661371 Date: Wed, 17 Oct 2012 01:11:59 GMT Server: httpd/1.4.x LaHonda ozsrv03 curl -I http://www.FreeBSD.org/ports/INDEX-9.bz2 HTTP/1.1 200 OK Content-Type: application/x-bzip Accept-Ranges: bytes ETag: 3948082461 Last-Modified: Sat, 13 Oct 2012 10:24:02 GMT Content-Length: 1658256 Date: Wed, 17 Oct 2012 01:12:03 GMT Server: httpd/1.4.x LaHonda ozsrv03 curl -I http://www.FreeBSD.org/ports/INDEX-10.bz2 HTTP/1.1 200 OK Content-Type: application/x-bzip Accept-Ranges: bytes ETag: 219974981 Last-Modified: Sat, 13 Oct 2012 11:40:03 GMT Content-Length: 1658256 Date: Wed, 17 Oct 2012 01:12:08 GMT Server: httpd/1.4.x LaHonda -- John Marshall signature.asc Description: OpenPGP digital signature
Re: pppoe configuration and dns name resolution
On Tue, 16 Oct 2012 20:38:47 +0530, Jack wrote: I'm new as a FreeBSD user, and trying to configure my pppoe connection. I've been using PPPoE with a DSL modem for many years, using FreeBSD 4, 5 and 7 with the system's PPPoE tools. The IP was provided to the computer directly, so no DHCP in the modem involved (real modem mode). In /etc/ppp/ppp.conf, I did simply define: myispname: set device PPPoE:xl0 set authname customer1234567@myispname set authkey X set dial set login add default HISADDR No further changes to that file. Note that here, xl0 is the interface directly connected to the modem. And in /etc/rc.conf: ifconfig_xl0=192.168.0.1 netmask 0xff00 ppp_enable=YES ppp_profile=myispname ppp_mode=ddial ppp_nat=YES So the system would automatically start the connection at boot time. The tun0 interface would then be associated the public IP designated when the PPPoE connection was up and running. Note that ppp_nat only has been needed to transition the connection through a 2nd NIC into the local net, making my machine a gateway (including related services, such as natd and dhcpd). I also think initializing the NIC xl0 is not entirely needed, maybe up would have been sufficient. For actually being able to use PPPoE, I did add the required components to the kernel, because that approach was state of the art at those times. :-) In /etc/resolv.conf I did add the nameservers published by my ISP. Anything worked automatically, I did not need to make further changes. Basically my setup looks like yours, except that (as I said) I did not use any additional features of the DSL modem (as it did not have such features). :-) -- 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
