RE: routing and networking help. (urgent help please)
FIXED, ignore this email.. However no one has answered. Hello Gurus, This is an Urgent help, as everything pending, waiting.. a FreeBSD Solution. and I appologize if I will explain in details, please be patient with me. Just yesterday, our ISP installed 2 routers (both 3com) at our main office. One router acting for Datalink between the office and the branch (datarouter) One for the internet connection.(internet router) one short cable connected from the internet router to datalink router So everyone on the WAN has internet access which we donot want. So we decided to have our FreeBSD 6.1-R server, managing all the job. So I installed a FreeBSD box, with NATd enabled, this is how it works Internet router --- rl0 192.168.0.3 freebsd dc0 192.168.1.1 --- switch --- all clinets also a cat5 cable hookedup from the datalink router to the switch. So the switch having the clinets+datalink router + lan freebsd cable. The datalink router connected to the branch site also WAN. the internet router has the following configurations. IP 192.168.0.2 gateway 192.168.0.254 and the datalink configuration has the follow gateway 192.168.0.253 WAN (branch site) IPs of 192.168.2.xx gateway 192.168.0.254 ALL can ping each other and see each other..(if there is no freebsd server) also wan works perfectly.. with no FreeBSD server.. Here is the problem the problem when I configure my fbsd lan interface to 192.168.1.1 and my clinets will have the IP 192.168.1.x/24 with gateway 192.168.0.254 wthey will have the internet.. and will NOT see any datalink clients, nor will see the WAN on the branch site. (diffrences of IPs and gateways) because clinets directed to the fbsd server which regonize 192.168.0.254 (internet router) If I configure my clients behind fbsd nat server to IPs of 192.168.0.x/24 and gateway 192.168.0.253 (Insted of 192.168.1.x and gw 192.168.0.254) they will see the datalink and wan but no internet. How would I make all clinets have my fbsd lan ips 192.168.1.x/24 and freebsd will have the ability to see the two gateways 192.168.0.254 (internet router) and 192.168.0.253 (datalink router) In short words, all clinets should be connected to FreeBSD server lan interface but in the same time, freebsd will route and manage to the requests for wan. Second problem: If i have rl0 to host my internet router real IP and defautlrouter to the NAT ip, internet will not work. ifconfig_rl0=inet 62.215.x.6 netmask 255.255.255.252 defaultrouter=62.215.x.5 #internet router IP No Internet. but if i host my rl0 to 192.168.0.3 and defaultrouter to 192.168.0.254 (internet router gateway) internet will work... ifconfig_rl0=inet 192.168.0.3 netmask 255.255.255.0 defaultrouter=192.168.0.254 The first case, disabling nat from router and having it to freebsd only second case, having the router to NAT and again freebsd doing another nat. Sorry Gurus for the long emails, excuse me, and waiting your reply asap. -Marwan Sultan. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
routing and networking help. (urgent help please)
Hello Gurus, This is an Urgent help, as everything pending, waiting.. a FreeBSD Solution. and I appologize if I will explain in details, please be patient with me. Just yesterday, our ISP installed 2 routers (both 3com) at our main office. One router acting for Datalink between the office and the branch (datarouter) One for the internet connection.(internet router) one short cable connected from the internet router to datalink router So everyone on the WAN has internet access which we donot want. So we decided to have our FreeBSD 6.1-R server, managing all the job. So I installed a FreeBSD box, with NATd enabled, this is how it works Internet router --- rl0 192.168.0.3 freebsd dc0 192.168.1.1 --- switch --- all clinets also a cat5 cable hookedup from the datalink router to the switch. So the switch having the clinets+datalink router + lan freebsd cable. The datalink router connected to the branch site also WAN. the internet router has the following configurations. IP 192.168.0.2 gateway 192.168.0.254 and the datalink configuration has the follow gateway 192.168.0.253 WAN (branch site) IPs of 192.168.2.xx gateway 192.168.0.254 ALL can ping each other and see each other..(if there is no freebsd server) also wan works perfectly.. with no FreeBSD server.. Here is the problem the problem when I configure my fbsd lan interface to 192.168.1.1 and my clinets will have the IP 192.168.1.x/24 with gateway 192.168.0.254 wthey will have the internet.. and will NOT see any datalink clients, nor will see the WAN on the branch site. (diffrences of IPs and gateways) because clinets directed to the fbsd server which regonize 192.168.0.254 (internet router) If I configure my clients behind fbsd nat server to IPs of 192.168.0.x/24 and gateway 192.168.0.253 (Insted of 192.168.1.x and gw 192.168.0.254) they will see the datalink and wan but no internet. How would I make all clinets have my fbsd lan ips 192.168.1.x/24 and freebsd will have the ability to see the two gateways 192.168.0.254 (internet router) and 192.168.0.253 (datalink router) In short words, all clinets should be connected to FreeBSD server lan interface but in the same time, freebsd will route and manage to the requests for wan. Second problem: If i have rl0 to host my internet router real IP and defautlrouter to the NAT ip, internet will not work. ifconfig_rl0=inet 62.215.x.6 netmask 255.255.255.252 defaultrouter=62.215.x.5 #internet router IP No Internet. but if i host my rl0 to 192.168.0.3 and defaultrouter to 192.168.0.254 (internet router gateway) internet will work... ifconfig_rl0=inet 192.168.0.3 netmask 255.255.255.0 defaultrouter=192.168.0.254 The first case, disabling nat from router and having it to freebsd only second case, having the router to NAT and again freebsd doing another nat. Sorry Gurus for the long emails, excuse me, and waiting your reply asap. -Marwan Sultan. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Please help - URGENT - disk/fsck problems!--SOLVED!
I'm in need of urgent help. I have a production 4.9-RELEASE server. I track STABLE, last cvsup/make world was about two months ago. After powering on after an extended power outage (was given advanced notice by electric company and I shut the server down before the outage occurred), the server hung with disk problems and suggested I run fsck. I ran fsck and came up with thousands of errors. I re-ran fsck and came up with less. I repeated this process for what seems like a hundred times. No matter what I do, though, I still have errors that fsck seems unable to repair. HELP!! Well, seeing as that I didn't get a single response to my URGENT plea for help, and noting that necessity is the mother of all invention, I managed to solve this problem myself (48 hours after the fact with users screaming at me for 6 of them). I'm repling to my own post in the hopes it'll be archived and help some poor SOB like myself should they encounter the same problem. I don't know if it was the *right* way to solve the problem, or even if there were alternative ways. This method did work, though. It resulted in some data loss, but I was illing to live with that since I have good tape backups to restore from. Here's how I fixed my problem. After RTFM on fsck (man fsck) for the 4,341st time, I noticed under the see also section a utility called fsdb, the FFS debugging/editing tool. While messing with inodes and such as always scared the hell out of me, I figured I had nothing to loose at this point. I went back to my fsck output and noted that certain errors seemed to never go away, like this one: INCORRECT BLOCK COUNT I=447212 (5280 should be 4064) I assumed that the I above was an Inode number. I fired up fsdb with the disk slice in question as a paramenter, like this: fsdb /dev/da0s1g This gave me a fsdb prompt. From there I issued the command: clri i-number (e.g., clri 447212). This apparently nukes the Inode number given to it. I did this for all the Inode numbers that continually re-appeared after numerous fsck's. I typed quit (or was it exit?) to leave fsdb and then re-ran fsck. Problem sovled. Restored from tape (love AMANDA!) and I was good-to-go! Hopes this helps somebody... Thanks, --Sean Noonan * No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another party by email without express written confirmation by an Officer of the company. In addition, any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, L.P. Employees of Watkins Contracting, L.P., are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SOLVED! : Please help - URGENT - disk/fsck problems!
I'm in need of urgent help. I have a production 4.9-RELEASE server. I track STABLE, last cvsup/make world was about two months ago. After powering on after an extended power outage (was given advanced notice by electric company and I shut the server down before the outage occurred), the server hung with disk problems and suggested I run fsck. I ran fsck and came up with thousands of errors. I re-ran fsck and came up with less. I repeated this process for what seems like a hundred times. No matter what I do, though, I still have errors that fsck seems unable to repair. HELP!! Well, seeing as that I didn't get a single response to my URGENT plea for help, and noting that necessity is the mother of all invention, I managed to solve this problem myself (48 hours after the fact with users screaming at me for 6 of them). I'm repling to my own post in the hopes it'll be archived and help some poor SOB like myself should they encounter the same problem. I don't know if it was the *right* way to solve the problem, or even if there were alternative ways. This method did work, though. It resulted in some data loss, but I was illing to live with that since I have good tape backups to restore from. Here's how I fixed my problem. After RTFM on fsck (man fsck) for the 4,341st time, I noticed under the see also section a utility called fsdb, the FFS debugging/editing tool. While messing with inodes and such as always scared the hell out of me, I figured I had nothing to loose at this point. I went back to my fsck output and noted that certain errors seemed to never go away, like this one: INCORRECT BLOCK COUNT I=447212 (5280 should be 4064) I assumed that the I above was an Inode number. I fired up fsdb with the disk slice in question as a paramenter, like this: fsdb /dev/da0s1g This gave me a fsdb prompt. From there I issued the command: clri i-number (e.g., clri 447212). This apparently nukes the Inode number given to it. I did this for all the Inode numbers that continually re-appeared after numerous fsck's. I typed quit (or was it exit?) to leave fsdb and then re-ran fsck. Problem sovled. Restored from tape (love AMANDA!) and I was good-to-go! Hopes this helps somebody... Thanks, --Sean Noonan * No employee or agent is authorized to conclude any binding agreement on behalf of Watkins Contracting, L.P., with another party by email without express written confirmation by an Officer of the company. In addition, any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Watkins Contracting, L.P. Employees of Watkins Contracting, L.P., are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Please help - URGENT - disk/fsck problems!
I'm in need of urgent help. I have a production 4.9-RELEASE server. I track STABLE, last cvsup/make world was about two months ago. After powering on after an extended power outage (was given advanced notice by electric company and I shut the server down before the outage occurred), the server hung with disk problems and suggested I run fsck. I ran fsck and came up with thousands of errors. I re-ran fsck and came up with less. I repeated this process for what seems like a hundred times. No matter what I do, though, I still have errors that fsck seems unable to repair. HELP!! What are my options? Is there any way to repair the file system? How, exactly? I backup every night with AMANDA to a DLT drive. Would restoring from tape also restore the errors to the file system? I'm desperate, if any one could assist I'd be very grateful! TIA, --Sean Noonan P.S. - Here's the output from fsck (yes, I realize the volume is mounted in this output and therefore the filesystem is read-only): bash-2.05b# fsck ** /dev/da0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2004 files, 38340 used, 90659 free (307 frags, 11294 blocks, 0.2% fragmentation) ** /dev/da0s1f (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 10301 files, 26910 used, 231121 free (169 frags, 28869 blocks, 0.1% fragmentation) ** /dev/da0s1g (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=447212 (5280 should be 4064) CORRECT? no ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts LINK COUNT FILE I=648323 OWNER=man MODE=0 SIZE=0 MTIME=Feb 16 13:35 2004 COUNT 0 SHOULD BE -1 ADJUST? no ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no ALLOCATED FRAG 890704 MARKED FREE ALLOCATED FRAG 890705 MARKED FREE . . . ALLOCATED FRAG 4937333 MARKED FREE ALLOCATED FRAG 4937334 MARKED FREE ALLOCATED FRAG 4937335 MARKED FREE 253019 files, 2151531 used, 3184970 free (57794 frags, 390897 blocks, 1.1% fragmentation) ** /dev/da0s1e (NO WRITE) ** Last Mounted on /var ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=151455 (6912 should be 640) CORRECT? no INCORRECT BLOCK COUNT I=151456 (95008 should be 225856) CORRECT? no ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no ALLOCATED FRAG 646592 MARKED FREE ALLOCATED FRAG 646593 MARKED FREE ALLOCATED FRAG 646594 MARKED FREE . . . ALLOCATED FRAG 679445 MARKED FREE ALLOCATED FRAG 679446 MARKED FREE ALLOCATED FRAG 679447 MARKED FREE BLK(S) MISSING IN BIT MAPS SALVAGE? no 1760 files, 98086 used, 1997709 free (1317 frags, 249549 blocks, 0.1% fragmentation) bash-2.05b# ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help-urgent
Don't think these lists are the best place for this question but alas... On Mon, Jan 06, 2003 at 06:25:13AM +, shubha mr wrote: If I have to write to a register at offset say x,in the pci configuration space,how do I do it? If it is using pci_read_config and pci_write_config,how does the system know where the pci reg base address of my device is? val = pci_read_config(dev, OFFSET, len); dev: the PCI device your driver is working on OFFSET: the position you want to read from len: the number of bytes you want to read Because you specify the pci dev the system knows where to read from. Look at any random pci driver in sys/ and it will all become clear. Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
help-urgent
Hi, If I have to write to a register at offset say x,in the pci configuration space,how do I do it? If it is using pci_read_config and pci_write_config,how does the system know where the pci reg base address of my device is? plese help urgent shubha __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
mountroot Please Help / URGENT..
Date: 12-22-02 Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) Situation: I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. After successful replication has taken place I reboot the machine and everything runs flawlessly as it should... However, here is the problem: The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... Upon booting it brings me to this prompt: === Manual root filesystem specification: fstype:device Mount device using filesystem fstype Example: ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input Mountroot === I then type: mountroot ufs:/dev/ar0s1a and receive this message: Mounting root from ufs:/dev/ar0s1a No such device 'ar' Getrootbyname failed mfs_mountroot: can't find rootvp root mount failed: 6 - I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access and browsing is limited to the /root /dev /etc directory. I then 'cat' the FSTAB directory to see this configuration: /dev/ar0s1b none swap sw 0 0 /dev/ar0s1a / ufs rw 1 1 /dev/ar0s1e /usr ufs rw 2 2 /dev/acodoc /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 - Would anyone able to help me out with this situation ? The data on the backup drive is VERY IMPORTANT and I can't get to it... I can be reached via email and I will reply immediately!! Please have the subject line pertaining to FreeBSD / Backup Drives or something comparable to that so I do not accidentally delete it thinking it is spam... [EMAIL PROTECTED] Thanks, Ethan _ MSN 8 with e-mail virus protection service: 3 months FREE*. http://join.msn.com/?page=features/virusxAPID=42PS=47575PI=7324DI=7474SU= http://www.hotmail.msn.com/cgi-bin/getmsgHL=1216hotmailtaglines_eliminateviruses_3mf To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access and browsing is limited to the /root /dev /etc directory. once there, just type % mount / % mount /usr that will at least get you access to your data. -randall -- :// randall s. ehren :// voice 805.893.5632 :// systems administrator:// isber|survey|avss.ucsb.edu :// institute for social, behavioral, and economic research To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
# [EMAIL PROTECTED] / 2002-12-23 01:23:53 +: Date: 12-22-02 Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. After successful replication has taken place I reboot the machine and everything runs flawlessly as it should... However, here is the problem: The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... Upon booting it brings me to this prompt: Manual root filesystem specification: fstype:device Mount device using filesystem fstype Example: ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input Mountroot I then type: mountroot ufs:/dev/ar0s1a and receive this message: Mounting root from ufs:/dev/ar0s1a No such device 'ar' Getrootbyname failed mfs_mountroot: can't find rootvp root mount failed: 6 right. when you plug the drive into a regular IDE controller it's not /dev/ar* anymore. I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access right. the drive is ad0* now, and it's mounted read-only because the system assumes a problem, and stays on the safe side. and browsing is limited to the /root /dev /etc directory. right. see below. I then 'cat' the FSTAB directory to see this configuration: you mean /etc/fstab, right? it's fstab, not FSTAB (the case matters; I've seen someone rename the file to Fstab and then wonder what broke), and it's a file, not a directory. /dev/ar0s1b none swap sw 0 0 /dev/ar0s1a / ufs rw 1 1 /dev/ar0s1e /usr ufs rw 2 2 the system can't mount /usr because it is listed being in ar0s1e, but that device is not present now. /dev/acodoc /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 Would anyone able to help me out with this situation ? The data on the backup drive is VERY IMPORTANT and I can't get to it... have you read the Handbook? http://www.freebsd.org/doc/handbook/mount-unmount.html also, you *do* know mount(8), why don't you use your knowledge? # mount -u /dev/ad0s1a / # mount /dev/ad0s1e /usr # sed -E 's/ar0/ad0/' /etc/fstab /tmp/fstab # cat /tmp/fstab (check that it's ok) # mv /tmp/fstab /etc (/etc/fstab should be root:wheel 644, chown/chmod it if it's not) # swapon -a and you're set. since you will most probably be in singleuser at this point, you'll want to finish the booting procedure: # exit -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
- Original Message - From: Ethan Akins [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 23, 2002 2:23 AM Subject: mountroot Please Help / URGENT.. Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) Situation: I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. Lemme guess, you're using a FastTrack RAID controller? I use the exact same method of backing up as you do (on my ASUS A7V333), down to the same rotation scheme even. :) The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... How odd. On my ASUS A7V333 board I can yank out either of the two disks, and even though the BIOS complains a bit about my array being in a critical state, it will still boot, of course. I say of course, for that is the whole point of having a RAID 1, right? That if one of the drives fails, you can continue with the other. Naturally, FreeBSD 4.7R still notices the drive missing from the array, but unless you checked the logs, you would not know it. Would anyone able to help me out with this situation ? Have you tried physically removing (disconnecting) the first drive? That may help. It could be a FreeBSD issue (though I doubt it; it is hard to imagine the difference between 4.6 and 4.7 would be this major). I have heard people say here that FreeBSD could not possibly mount the single drive partitions as they are part of an array. Well, I cannot speak for others, but there have been several occassions where I had to do exactly what you want: boot from the backup disk to retrieve data; and, like I said, unless I checked the logs, FreeBSD ran just as it always does: smoothly. :) - Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
