Re: Link and network level in the tcp/ip stack
On 5/7/2011 6:41 PM, Erik Nørgaard wrote: So the question is which behaviour is correct, recommended or accepted? Stripping the link layer and reply according to the network layer, or keeping the link layer? This is the way it in every TCP/IP stack out there. The routing decision for the reply IP packet of the ICMP message is made independently of the upper-OSI-layer TCP state. In this instance, its a bit inconvenient for you, but having these layers abstracted makes for incredible flexibility in TCP/IP; the same thinking as small POSIX utilities work independently is more flexible. -- Brian A. Seklecki CE-Pro Bikes, LLC 412-378-3823 (m) PGP Key Available Upon Request ___ 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: Link and network level in the tcp/ip stack
On 7/5/11 4:12 PM, Arun wrote: Just add default route at your node 10.225.162.28, and make the default GW for this route as 192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could NOT forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1. Thanks. Hi: There can only be one default gateway, anything else doesn't make sense. I did try adding a specific route on SRV for RN such that pings arriving on 10.225.162.28 would be responded correctly. But, then RN can no longer reach 192.168.28.196. No surprise there really. So, why do we have this setup? Well, some services like ssh that is used for administration must arrive on 192.168.28/24 where as the commercial service has a dedicated network on 10.225.162/24 and to ensure availability and bandwidth we cannot accept to have ssh coming in on that network. I should add that this is a Red Hat Linux, I ask here since the FBSD implementation of the tcp/ip stack is considered the reference implementation. So the question is which behaviour is correct, recommended or accepted? Stripping the link layer and reply according to the network layer, or keeping the link layer? Thanks, Erik ___ 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: Link and network level in the tcp/ip stack
Correction - read NOT in line : "If your SRV node could NOT forward the ping reply then add a ..." Niether it is a problem of small subnet nor NIC card. The problem is of routing entries. Just add default route at your node 10.225.162.28, and make the default GW for this route as 192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could NOT forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1. Thanks. __ Before printing, think about your ENVIRONMENTAL responsibility. --- On Sun, 5/8/11, Arun wrote: From: Arun Subject: Re: Link and network level in the tcp/ip stack To: "Erik Nørgaard" , "Lokadamus" Cc: questi...@freebsd.org Received: Sunday, May 8, 2011, 2:00 AM Niether it is a problem of small subnet not NIC card. The problem is of routing entries. Just add default route at your node 10.225.162.28, and make the default GW for this route as 192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1. Thanks. __ Before printing, think about your ENVIRONMENTAL responsibility. --- On Sun, 5/8/11, Lokadamus wrote: From: Lokadamus Subject: Re: Link and network level in the tcp/ip stack To: "Erik Nørgaard" Cc: questi...@freebsd.org Received: Sunday, May 8, 2011, 12:22 AM Am 06.05.2011 23:17, schrieb Erik Nørgaard: > Hi: > > This is a generic question about may, should and must: > > I have the following setup: > > 192.168.28/24 > +---+ > |.196 |.1 > SRV GW- RN > |.28 |.1 > +---+ > 10.225.162/24 > > The server, SRV, has default gateway set to 192.168.28.1, no routing has been > configured for the 10.225.162/24 network. The gateway is a router, no NAT or > firewall. Yup, we do have this setup, don't ask why. > > Now, the remote node RN pings the server on 192.168.28.196 fine, no problem. > Then it pings 10.225.162.28 and get destination unreachable. > > OK, so I did tcpdump first on the 10.225.162.28 interface, and saw icmp echo > requests coming in, but no replies going out. Then I did tcpdump on the other > interface and got this: > > 13:39:43.233419 arp who-has 192.168.28.1 tell 10.225.162.28 > > obviously no reply, wrong network. > Can your SRV (10.225.162.28) ping anything in 192.168.28? I don't think, because your SRV is looking for its gateway, but never get an answer from it. It's subnetmask is to small to reach another subnet. Put another network card in it with an ip of 192.168.28 and all will working. Sorry for my bad english ;( > Thanks, Erik > ___ > 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: Link and network level in the tcp/ip stack
Niether it is a problem of small subnet not NIC card. The problem is of routing entries. Just add default route at your node 10.225.162.28, and make the default GW for this route as 192.168.28.0/24 or the connected interface. Your SRV node should pass it to its default gw 192.168.28.1 which should take care of forwarding it to the destination RN. If your SRV node could forward the ping reply then add a specific route there like - "pkt comes from 10.225.162.0 then forward it to 192.168.28.1. Thanks. __ Before printing, think about your ENVIRONMENTAL responsibility. --- On Sun, 5/8/11, Lokadamus wrote: From: Lokadamus Subject: Re: Link and network level in the tcp/ip stack To: "Erik Nørgaard" Cc: questi...@freebsd.org Received: Sunday, May 8, 2011, 12:22 AM Am 06.05.2011 23:17, schrieb Erik Nørgaard: > Hi: > > This is a generic question about may, should and must: > > I have the following setup: > > 192.168.28/24 > +---+ > |.196 |.1 > SRV GW- RN > |.28 |.1 > +---+ > 10.225.162/24 > > The server, SRV, has default gateway set to 192.168.28.1, no routing has been > configured for the 10.225.162/24 network. The gateway is a router, no NAT or > firewall. Yup, we do have this setup, don't ask why. > > Now, the remote node RN pings the server on 192.168.28.196 fine, no problem. > Then it pings 10.225.162.28 and get destination unreachable. > > OK, so I did tcpdump first on the 10.225.162.28 interface, and saw icmp echo > requests coming in, but no replies going out. Then I did tcpdump on the other > interface and got this: > > 13:39:43.233419 arp who-has 192.168.28.1 tell 10.225.162.28 > > obviously no reply, wrong network. > Can your SRV (10.225.162.28) ping anything in 192.168.28? I don't think, because your SRV is looking for its gateway, but never get an answer from it. It's subnetmask is to small to reach another subnet. Put another network card in it with an ip of 192.168.28 and all will working. Sorry for my bad english ;( > Thanks, Erik > ___ > 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: Link and network level in the tcp/ip stack
Am 06.05.2011 23:17, schrieb Erik Nørgaard: Hi: This is a generic question about may, should and must: I have the following setup: 192.168.28/24 +---+ |.196 |.1 SRVGW- RN |.28 |.1 +---+ 10.225.162/24 The server, SRV, has default gateway set to 192.168.28.1, no routing has been configured for the 10.225.162/24 network. The gateway is a router, no NAT or firewall. Yup, we do have this setup, don't ask why. Now, the remote node RN pings the server on 192.168.28.196 fine, no problem. Then it pings 10.225.162.28 and get destination unreachable. OK, so I did tcpdump first on the 10.225.162.28 interface, and saw icmp echo requests coming in, but no replies going out. Then I did tcpdump on the other interface and got this: 13:39:43.233419 arp who-has 192.168.28.1 tell 10.225.162.28 obviously no reply, wrong network. Can your SRV (10.225.162.28) ping anything in 192.168.28? I don't think, because your SRV is looking for its gateway, but never get an answer from it. It's subnetmask is to small to reach another subnet. Put another network card in it with an ip of 192.168.28 and all will working. Sorry for my bad english ;( Thanks, Erik ___ 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
Dnia 19.01.2010 Diego Montalvo napisał/a: > Been trying to install /usr/ports/java/jdk16 and get an error stating > need to place "tzupdater-1_3_21-2009p.zip" into > /usr/ports/distfiles... have gone to sun and file is no longer there, > and have searched internet for it but to no avail. For the archives: http://42.pl/u/27NV_tzupdater-1321 (or https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/DownloadSingleSoftware-Start?ProductRef=tzupdater-1.3.21-oth-JPR_Multi-language_with_Generic%40CDS-CDS_Developer). --Marcin ___ 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
Thank you all so much for the links and files. I got jdk16 installed correctly "hopefully"! 2010/1/19 Darrell D Rajala : > Diego Montalvo wrote: >> >> Been trying to install /usr/ports/java/jdk16 and get an error stating >> need to place "tzupdater-1_3_21-2009p.zip" into >> /usr/ports/distfiles... have gone to sun and file is no longer there, >> and have searched internet for it but to no avail. >> >> Does someone have link where I can download the file? or can someone >> email me the file? >> >> Thanks, >> Diego >> ___ >> 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
On Tue, 19 Jan 2010, Diego Montalvo wrote: Been trying to install /usr/ports/java/jdk16 and get an error stating need to place "tzupdater-1_3_21-2009p.zip" into /usr/ports/distfiles... have gone to sun and file is no longer there, and have searched internet for it but to no avail. Does someone have link where I can download the file? or can someone email me the file? You can use 'make config' in the port to disable the need for that file entirely. I don't know what the down side is to that. -Warren Block * Rapid City, South Dakota USA ___ 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
--On Tuesday, January 19, 2010 11:39:21 -0600 Diego Montalvo wrote: Been trying to install /usr/ports/java/jdk16 and get an error stating need to place "tzupdater-1_3_21-2009p.zip" into /usr/ports/distfiles... have gone to sun and file is no longer there, and have searched internet for it but to no avail. Does someone have link where I can download the file? or can someone email me the file? Thanks, Diego ___ 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" http://java.sun.com/javase/downloads/index.jsp#timezone -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson ___ 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
http://ftp.play.ufanet.ru/post/distfiles/ On Tue, 2010-01-19 at 09:39 -0800, Diego Montalvo wrote: > tzupdater-1_3_21-2009p.zip ___ 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: Link to File for JDK16 tzupdater-1_3_21-2009p.zip
> Been trying to install /usr/ports/java/jdk16 and get an error stating > need to place "tzupdater-1_3_21-2009p.zip" into > /usr/ports/distfiles... have gone to sun and file is no longer there, > and have searched internet for it but to no avail. > > Does someone have link where I can download the file? or can someone > email me the file? Here is a temporary link to the file. This link will stay for only a couple of weeks at most. http://daffy.nerius.com/temp/tzupdater-1_3_21-2009p.zip ___ 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: link to dos2unix
On Sun, 1 Mar 2009, Fbsd1 wrote: I get message ==oops you renamed me using unix2dos instead. Someone else has already replied that the binary only knows what to do by checking the name used to call it. The way to do what you want is to use an alias in your shell. In BASH this would be alias d2u='dos2unix' in .profile. Then run source .profile, or log out and log in. This may vary according to which shell you use. Consult the man for your shell. The reason this works is that the shell resolves the alias before it calls the command, so the command never knows what you really typed. A number of applications are like this. Aliasing is the right way to make shortcut names, rather than creating links. If you want the alias to work system-wide, edit the system confifuration file for the particular shell. If users use several different shell, you do have to add the alias to each distinct configuration file. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: link to dos2unix
Roland Smith wrote: On Sun, Mar 01, 2009 at 05:00:27PM +0800, Fbsd1 wrote: I use the dos2unix console command all the time. I am tried to typing in that long name. I tried to do a hard link on it. ln /usr/local/bin/dos2unix /usr/local/bin/d2u This command is accepted without error, but when it execute it d2u .txt I get message ==oops you renamed me using unix2dos instead. I also tried ln -s /usr/local/bin/dos2unix /usr/local/bin/d2u and got same results. ls -l does not show dos2unix as linked all ready. What am I doing wrong here? Usually, programs like this perform dos2unix or unix2dos translations depending on how they are called. So renaming them won't work. Try adding an alias to your favorite shell. That should work. E.g.put 'alias d2u dos2unix' and 'alias u2d unix2dos' in your .cshrc. Roland Thank you. That worked. ___ 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: link to dos2unix
On Sun, Mar 01, 2009 at 05:00:27PM +0800, Fbsd1 wrote: > I use the dos2unix console command all the time. I am tried to typing in > that long name. I tried to do a hard link on it. > ln /usr/local/bin/dos2unix /usr/local/bin/d2u > This command is accepted without error, but when it execute it > d2u .txt > I get message ==oops you renamed me using unix2dos instead. > I also tried > ln -s /usr/local/bin/dos2unix /usr/local/bin/d2u > and got same results. ls -l does not show dos2unix as linked all ready. > > What am I doing wrong here? Usually, programs like this perform dos2unix or unix2dos translations depending on how they are called. So renaming them won't work. Try adding an alias to your favorite shell. That should work. E.g.put 'alias d2u dos2unix' and 'alias u2d unix2dos' in your .cshrc. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpBuXLQC5oa5.pgp Description: PGP signature
Re: link to dos2unix
long name. I tried to do a hard link on it. ln /usr/local/bin/dos2unix /usr/local/bin/d2u This command is accepted without error, but when it execute it d2u .txt I get message ==oops you renamed me using unix2dos instead. I also tried ln -s /usr/local/bin/dos2unix /usr/local/bin/d2u and got same results. ls -l does not show dos2unix as linked all ready. What am I doing wrong here? it HAS to be called dos2unix - this program reacts on the name it was called as because dos2unix and unix2dos are the same binary. if called as d2u - it doesn't know what to do. use shell aliases ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
-Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 10 February 2009 17:22 To: Graeme Dargie Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 Graeme Dargie a écrit : > > -Original Message- > From: FreeBSD [mailto:free...@optiksecurite.com] > Sent: 06 February 2009 16:47 > To: Graeme Dargie > Cc: freebsd-questions@freebsd.org > Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 > > Graeme Dargie a écrit : >> -Original Message- >> From: FreeBSD [mailto:free...@optiksecurite.com] >> Sent: 04 February 2009 21:55 >> Cc: freebsd-questions@freebsd.org >> Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 >> >> FreeBSD a écrit : >>> Graeme Dargie a écrit : >>>> If you do a dmesg are you also showing a watchdog time out for the nic ? >>>> >>>> I only ask as I am having the exact same problem with the exact same >>>> card and I have yet to find a solution, if I come across something I >>>> will let you know. >>>> >>>> Regards >>>> Graeme >>> Not a single time...sorry. >>> >>>> -Original Message- >>>> From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 >>>> 18:58 >>>> To: freebsd-questions@freebsd.org >>>> Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 >>>> >>>> FreeBSD a écrit : >>>>> Hi everyone, >>>>> >>>>> Just to put you in context, I applied the following patch to make the >>>>> card available: >>>>> >>>>> SVN rev 186389 on 2008-12-22 00:46:22Z by yongari >>>>> >>>>> Since we don't request reset for rlphy(4), the link state 'UP' >>>>> event from mii(4) may not be delivered if valid link was already >>>>> established. To address the issue, check current link state after >>>>> driving MII_TICK. This should fix a regression introduced in >>>>> r185753 on fast ethernet controllers. >>>>> >>>>> --- >>>>> >>>>> I don't have any issue related to that anymore. The problem is that I >>>>> get link UP/DOWN a few times per hour on 3 identical machines that I >>>>> dumped/restored. They are all pluged in a Cisco switch that works >>>>> fine for every other PCs. >>>>> >>>>> Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN >>>>> Jan 26 06:09:17 term005 kernel: re0: link state changed to UP >>>>> >>>>> I tried to switch cables, but I got the same result. >>>>> >>>>> There is the pciconf -lv output: >>>>> >>>>> r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec >>>>> rev=0x02 hdr=0x00 >>>>> vendor = 'Realtek Semiconductor' >>>>> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' >>>>> class = network >>>>> subclass = ethernet >>>>> >>>>> There is the output of vmstat -i: >>>>> >>>>> interrupt total rate >>>>> irq18: re0 ehci0++ 63766 0 >>>>> irq19: atapci0277001 3 >>>>> cpu0: timer156068748 1961 >>>>> Total 156409515 1966 >>>>> >>>>> Could it be related to the fact that there is re0 and ehci0++ on the >>>>> same IRQ? >>>>> >>>>> Thank you for your help, >>>>> >>>>> Martin >>>> I just tried with a brand new Dell 2708 switch and the problem is >>>> still there. I just confirmed that the UP/DOWN occurs every 10 minutes >>>> (+- a few seconds). >>>> >>>> Thanks again, >>>> >>>> Martin >>>> >> Just to follow-up on my own problem... >> >> I tried to disable some options of the card with : >> ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag >> >> but nothing as changed. I just tried to download a big file (FreeBSD >> 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a >> transfer. The DVD downloaded successfully and I verified that the MD5 >> are OK. BUT, /var/log/messages continue to
Re: Link UP/DOWN problem with re0 on FreeBSD 7.1
Graeme Dargie a écrit : -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 06 February 2009 16:47 To: Graeme Dargie Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 Graeme Dargie a écrit : -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 04 February 2009 21:55 Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Graeme Dargie a écrit : If you do a dmesg are you also showing a watchdog time out for the nic ? I only ask as I am having the exact same problem with the exact same card and I have yet to find a solution, if I come across something I will let you know. Regards Graeme Not a single time...sorry. -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 18:58 To: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Hi everyone, Just to put you in context, I applied the following patch to make the card available: SVN rev 186389 on 2008-12-22 00:46:22Z by yongari Since we don't request reset for rlphy(4), the link state 'UP' event from mii(4) may not be delivered if valid link was already established. To address the issue, check current link state after driving MII_TICK. This should fix a regression introduced in r185753 on fast ethernet controllers. --- I don't have any issue related to that anymore. The problem is that I get link UP/DOWN a few times per hour on 3 identical machines that I dumped/restored. They are all pluged in a Cisco switch that works fine for every other PCs. Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN Jan 26 06:09:17 term005 kernel: re0: link state changed to UP I tried to switch cables, but I got the same result. There is the pciconf -lv output: r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet There is the output of vmstat -i: interrupt total rate irq18: re0 ehci0++ 63766 0 irq19: atapci0277001 3 cpu0: timer156068748 1961 Total 156409515 1966 Could it be related to the fact that there is re0 and ehci0++ on the same IRQ? Thank you for your help, Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin Just to follow-up on my own problem... I tried to disable some options of the card with : ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag but nothing as changed. I just tried to download a big file (FreeBSD 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a transfer. The DVD downloaded successfully and I verified that the MD5 are OK. BUT, /var/log/messages continue to tell me that: Feb 4 16:09:29 term003 kernel: re0: link state changed to UP Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN Feb 4 16:19:30 term003 kernel: re0: link state changed to UP Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN during the transfer (which worked OK). I don't know if that can help someone to help me ;) Thanks, Martin ___ 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" I have a solution to this well a work around. Add -tso to the relevant line in /etc/rc.conf ifconfig_re0="inet 192.168.1.103 netmask 255.255.255.0 -tso" Adding -tso stops the link up / link down problem. Now I am understand that this may increase cpu if the traffic on the nic is high. I am sure some one the list will know of any other implications this may have. It is a known problem and I site I read the bug had been submitted so hopefully it wont exist in 8.0 Regards Graeme As I stated in my last post, I tried to disable a few options, including TSO. Still, I gived a try to your workaround. I now have this line in rc.conf: ifconfig_re0="DHCP -tso" but I have the same problem (it disconnect every 10 minutes and ask for an IP to the DHCP). Thanks for your suggestion, Martin ___ 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" I don't use DHCP so it never causes me a problem, have you considered setting a static IP address ? Regard
RE: Link UP/DOWN problem with re0 on FreeBSD 7.1
-Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 06 February 2009 16:47 To: Graeme Dargie Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 Graeme Dargie a écrit : > -Original Message- > From: FreeBSD [mailto:free...@optiksecurite.com] > Sent: 04 February 2009 21:55 > Cc: freebsd-questions@freebsd.org > Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 > > FreeBSD a écrit : >> Graeme Dargie a écrit : >>> If you do a dmesg are you also showing a watchdog time out for the nic ? >>> >>> I only ask as I am having the exact same problem with the exact same >>> card and I have yet to find a solution, if I come across something I >>> will let you know. >>> >>> Regards >>> Graeme >> Not a single time...sorry. >> >>> -Original Message- >>> From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 >>> 18:58 >>> To: freebsd-questions@freebsd.org >>> Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 >>> >>> FreeBSD a écrit : >>>> Hi everyone, >>>> >>>> Just to put you in context, I applied the following patch to make the >>>> card available: >>>> >>>> SVN rev 186389 on 2008-12-22 00:46:22Z by yongari >>>> >>>> Since we don't request reset for rlphy(4), the link state 'UP' >>>> event from mii(4) may not be delivered if valid link was already >>>> established. To address the issue, check current link state after >>>> driving MII_TICK. This should fix a regression introduced in >>>> r185753 on fast ethernet controllers. >>>> >>>> --- >>>> >>>> I don't have any issue related to that anymore. The problem is that I >>>> get link UP/DOWN a few times per hour on 3 identical machines that I >>>> dumped/restored. They are all pluged in a Cisco switch that works >>>> fine for every other PCs. >>>> >>>> Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN >>>> Jan 26 06:09:17 term005 kernel: re0: link state changed to UP >>>> >>>> I tried to switch cables, but I got the same result. >>>> >>>> There is the pciconf -lv output: >>>> >>>> r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec >>>> rev=0x02 hdr=0x00 >>>> vendor = 'Realtek Semiconductor' >>>> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' >>>> class = network >>>> subclass = ethernet >>>> >>>> There is the output of vmstat -i: >>>> >>>> interrupt total rate >>>> irq18: re0 ehci0++ 63766 0 >>>> irq19: atapci0277001 3 >>>> cpu0: timer156068748 1961 >>>> Total 156409515 1966 >>>> >>>> Could it be related to the fact that there is re0 and ehci0++ on the >>>> same IRQ? >>>> >>>> Thank you for your help, >>>> >>>> Martin >>> I just tried with a brand new Dell 2708 switch and the problem is >>> still there. I just confirmed that the UP/DOWN occurs every 10 minutes >>> (+- a few seconds). >>> >>> Thanks again, >>> >>> Martin >>> > > Just to follow-up on my own problem... > > I tried to disable some options of the card with : > ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag > > but nothing as changed. I just tried to download a big file (FreeBSD > 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a > transfer. The DVD downloaded successfully and I verified that the MD5 > are OK. BUT, /var/log/messages continue to tell me that: > Feb 4 16:09:29 term003 kernel: re0: link state changed to UP > Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN > Feb 4 16:19:30 term003 kernel: re0: link state changed to UP > Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN > > during the transfer (which worked OK). I don't know if that can help > someone to help me ;) > > Thanks, > > Martin > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mai
Re: Link UP/DOWN problem with re0 on FreeBSD 7.1
Graeme Dargie a écrit : -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 04 February 2009 21:55 Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Graeme Dargie a écrit : If you do a dmesg are you also showing a watchdog time out for the nic ? I only ask as I am having the exact same problem with the exact same card and I have yet to find a solution, if I come across something I will let you know. Regards Graeme Not a single time...sorry. -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 18:58 To: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Hi everyone, Just to put you in context, I applied the following patch to make the card available: SVN rev 186389 on 2008-12-22 00:46:22Z by yongari Since we don't request reset for rlphy(4), the link state 'UP' event from mii(4) may not be delivered if valid link was already established. To address the issue, check current link state after driving MII_TICK. This should fix a regression introduced in r185753 on fast ethernet controllers. --- I don't have any issue related to that anymore. The problem is that I get link UP/DOWN a few times per hour on 3 identical machines that I dumped/restored. They are all pluged in a Cisco switch that works fine for every other PCs. Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN Jan 26 06:09:17 term005 kernel: re0: link state changed to UP I tried to switch cables, but I got the same result. There is the pciconf -lv output: r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet There is the output of vmstat -i: interrupt total rate irq18: re0 ehci0++ 63766 0 irq19: atapci0277001 3 cpu0: timer156068748 1961 Total 156409515 1966 Could it be related to the fact that there is re0 and ehci0++ on the same IRQ? Thank you for your help, Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin Just to follow-up on my own problem... I tried to disable some options of the card with : ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag but nothing as changed. I just tried to download a big file (FreeBSD 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a transfer. The DVD downloaded successfully and I verified that the MD5 are OK. BUT, /var/log/messages continue to tell me that: Feb 4 16:09:29 term003 kernel: re0: link state changed to UP Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN Feb 4 16:19:30 term003 kernel: re0: link state changed to UP Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN during the transfer (which worked OK). I don't know if that can help someone to help me ;) Thanks, Martin ___ 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" I have a solution to this well a work around. Add -tso to the relevant line in /etc/rc.conf ifconfig_re0="inet 192.168.1.103 netmask 255.255.255.0 -tso" Adding -tso stops the link up / link down problem. Now I am understand that this may increase cpu if the traffic on the nic is high. I am sure some one the list will know of any other implications this may have. It is a known problem and I site I read the bug had been submitted so hopefully it wont exist in 8.0 Regards Graeme As I stated in my last post, I tried to disable a few options, including TSO. Still, I gived a try to your workaround. I now have this line in rc.conf: ifconfig_re0="DHCP -tso" but I have the same problem (it disconnect every 10 minutes and ask for an IP to the DHCP). Thanks for your suggestion, Martin ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
-Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 04 February 2009 21:55 Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : > Graeme Dargie a écrit : >> If you do a dmesg are you also showing a watchdog time out for the nic ? >> >> I only ask as I am having the exact same problem with the exact same >> card and I have yet to find a solution, if I come across something I >> will let you know. >> >> Regards >> Graeme > > Not a single time...sorry. > >> >> -Original Message- >> From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 >> 18:58 >> To: freebsd-questions@freebsd.org >> Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 >> >> FreeBSD a écrit : >>> Hi everyone, >>> >>> Just to put you in context, I applied the following patch to make the >>> card available: >>> >>> SVN rev 186389 on 2008-12-22 00:46:22Z by yongari >>> >>> Since we don't request reset for rlphy(4), the link state 'UP' >>> event from mii(4) may not be delivered if valid link was already >>> established. To address the issue, check current link state after >>> driving MII_TICK. This should fix a regression introduced in >>> r185753 on fast ethernet controllers. >>> >>> --- >>> >>> I don't have any issue related to that anymore. The problem is that I >>> get link UP/DOWN a few times per hour on 3 identical machines that I >>> dumped/restored. They are all pluged in a Cisco switch that works >>> fine for every other PCs. >>> >>> Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN >>> Jan 26 06:09:17 term005 kernel: re0: link state changed to UP >>> >>> I tried to switch cables, but I got the same result. >>> >>> There is the pciconf -lv output: >>> >>> r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec >>> rev=0x02 hdr=0x00 >>> vendor = 'Realtek Semiconductor' >>> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' >>> class = network >>> subclass = ethernet >>> >>> There is the output of vmstat -i: >>> >>> interrupt total rate >>> irq18: re0 ehci0++ 63766 0 >>> irq19: atapci0277001 3 >>> cpu0: timer156068748 1961 >>> Total 156409515 1966 >>> >>> Could it be related to the fact that there is re0 and ehci0++ on the >>> same IRQ? >>> >>> Thank you for your help, >>> >>> Martin >> >> I just tried with a brand new Dell 2708 switch and the problem is >> still there. I just confirmed that the UP/DOWN occurs every 10 minutes >> (+- a few seconds). >> >> Thanks again, >> >> Martin >> Just to follow-up on my own problem... I tried to disable some options of the card with : ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag but nothing as changed. I just tried to download a big file (FreeBSD 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a transfer. The DVD downloaded successfully and I verified that the MD5 are OK. BUT, /var/log/messages continue to tell me that: Feb 4 16:09:29 term003 kernel: re0: link state changed to UP Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN Feb 4 16:19:30 term003 kernel: re0: link state changed to UP Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN during the transfer (which worked OK). I don't know if that can help someone to help me ;) Thanks, Martin ___ 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" I have a solution to this well a work around. Add -tso to the relevant line in /etc/rc.conf ifconfig_re0="inet 192.168.1.103 netmask 255.255.255.0 -tso" Adding -tso stops the link up / link down problem. Now I am understand that this may increase cpu if the traffic on the nic is high. I am sure some one the list will know of any other implications this may have. It is a known problem and I site I read the bug had been submitted so hopefully it wont exist in 8.0 Regards Graeme ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
FreeBSD a écrit : Graeme Dargie a écrit : If you do a dmesg are you also showing a watchdog time out for the nic ? I only ask as I am having the exact same problem with the exact same card and I have yet to find a solution, if I come across something I will let you know. Regards Graeme Not a single time...sorry. -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 18:58 To: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Hi everyone, Just to put you in context, I applied the following patch to make the card available: SVN rev 186389 on 2008-12-22 00:46:22Z by yongari Since we don't request reset for rlphy(4), the link state 'UP' event from mii(4) may not be delivered if valid link was already established. To address the issue, check current link state after driving MII_TICK. This should fix a regression introduced in r185753 on fast ethernet controllers. --- I don't have any issue related to that anymore. The problem is that I get link UP/DOWN a few times per hour on 3 identical machines that I dumped/restored. They are all pluged in a Cisco switch that works fine for every other PCs. Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN Jan 26 06:09:17 term005 kernel: re0: link state changed to UP I tried to switch cables, but I got the same result. There is the pciconf -lv output: r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet There is the output of vmstat -i: interrupt total rate irq18: re0 ehci0++ 63766 0 irq19: atapci0277001 3 cpu0: timer156068748 1961 Total 156409515 1966 Could it be related to the fact that there is re0 and ehci0++ on the same IRQ? Thank you for your help, Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin Just to follow-up on my own problem... I tried to disable some options of the card with : ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag but nothing as changed. I just tried to download a big file (FreeBSD 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a transfer. The DVD downloaded successfully and I verified that the MD5 are OK. BUT, /var/log/messages continue to tell me that: Feb 4 16:09:29 term003 kernel: re0: link state changed to UP Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN Feb 4 16:19:30 term003 kernel: re0: link state changed to UP Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN during the transfer (which worked OK). I don't know if that can help someone to help me ;) Thanks, Martin ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
Graeme Dargie a écrit : If you do a dmesg are you also showing a watchdog time out for the nic ? I only ask as I am having the exact same problem with the exact same card and I have yet to find a solution, if I come across something I will let you know. Regards Graeme Not a single time...sorry. -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 18:58 To: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : Hi everyone, Just to put you in context, I applied the following patch to make the card available: SVN rev 186389 on 2008-12-22 00:46:22Z by yongari Since we don't request reset for rlphy(4), the link state 'UP' event from mii(4) may not be delivered if valid link was already established. To address the issue, check current link state after driving MII_TICK. This should fix a regression introduced in r185753 on fast ethernet controllers. --- I don't have any issue related to that anymore. The problem is that I get link UP/DOWN a few times per hour on 3 identical machines that I dumped/restored. They are all pluged in a Cisco switch that works fine for every other PCs. Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN Jan 26 06:09:17 term005 kernel: re0: link state changed to UP I tried to switch cables, but I got the same result. There is the pciconf -lv output: r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet There is the output of vmstat -i: interrupt total rate irq18: re0 ehci0++ 63766 0 irq19: atapci0277001 3 cpu0: timer156068748 1961 Total 156409515 1966 Could it be related to the fact that there is re0 and ehci0++ on the same IRQ? Thank you for your help, Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
If you do a dmesg are you also showing a watchdog time out for the nic ? I only ask as I am having the exact same problem with the exact same card and I have yet to find a solution, if I come across something I will let you know. Regards Graeme -Original Message- From: FreeBSD [mailto:free...@optiksecurite.com] Sent: 26 January 2009 18:58 To: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a écrit : > Hi everyone, > > Just to put you in context, I applied the following patch to make the > card available: > > SVN rev 186389 on 2008-12-22 00:46:22Z by yongari > > Since we don't request reset for rlphy(4), the link state 'UP' > event from mii(4) may not be delivered if valid link was already > established. To address the issue, check current link state after > driving MII_TICK. This should fix a regression introduced in > r185753 on fast ethernet controllers. > > --- > > I don't have any issue related to that anymore. The problem is that I > get link UP/DOWN a few times per hour on 3 identical machines that I > dumped/restored. They are all pluged in a Cisco switch that works fine > for every other PCs. > > Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN > Jan 26 06:09:17 term005 kernel: re0: link state changed to UP > > I tried to switch cables, but I got the same result. > > There is the pciconf -lv output: > > r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > There is the output of vmstat -i: > > interrupt total rate > irq18: re0 ehci0++ 63766 0 > irq19: atapci0277001 3 > cpu0: timer156068748 1961 > Total 156409515 1966 > > Could it be related to the fact that there is re0 and ehci0++ on the > same IRQ? > > Thank you for your help, > > Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin ___ 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: Link UP/DOWN problem with re0 on FreeBSD 7.1
FreeBSD a écrit : Hi everyone, Just to put you in context, I applied the following patch to make the card available: SVN rev 186389 on 2008-12-22 00:46:22Z by yongari Since we don't request reset for rlphy(4), the link state 'UP' event from mii(4) may not be delivered if valid link was already established. To address the issue, check current link state after driving MII_TICK. This should fix a regression introduced in r185753 on fast ethernet controllers. --- I don't have any issue related to that anymore. The problem is that I get link UP/DOWN a few times per hour on 3 identical machines that I dumped/restored. They are all pluged in a Cisco switch that works fine for every other PCs. Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN Jan 26 06:09:17 term005 kernel: re0: link state changed to UP I tried to switch cables, but I got the same result. There is the pciconf -lv output: r...@pci0:3:0:0: class=0x02 card=0x02831028 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet There is the output of vmstat -i: interrupt total rate irq18: re0 ehci0++ 63766 0 irq19: atapci0277001 3 cpu0: timer156068748 1961 Total 156409515 1966 Could it be related to the fact that there is re0 and ehci0++ on the same IRQ? Thank you for your help, Martin I just tried with a brand new Dell 2708 switch and the problem is still there. I just confirmed that the UP/DOWN occurs every 10 minutes (+- a few seconds). Thanks again, Martin ___ 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: Link to PPP NAT tutorial ?
you are mixing up ppp nat and ipfw nat. these belong to ipfw nat natd_enable="YES"( I tried with NO too) natd_interface="tun0" natd_flags="-dynamic" you do nat in ppp or in the furewall but not both places. you need to post the desrciption of your over all network layout -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Sent: Monday, June 20, 2005 3:49 PM To: freebsd-questions@freebsd.org Subject: Link to PPP NAT tutorial ? Hello , can you please point me to some tutorial regarding NAT and PPP. I have successfully set up PPPoE connection on 1 of the interface, I am able to make ssh and ping the server from the other interface but I am still not able to make to make the system forward the packages. gateway_enable="YES ppp_nat="YES" natd_enable="YES"( I tried with NO too) natd_interface="tun0" natd_flags="-dynamic" I saw a few tutorials and I think I get confused :-) Can you please point me some that works with PPPoE and NATS ? Thanks a lot :-) -- Best regards, Peter http://AboutSupport.com ___ 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: link in handbook appears to be broken
Steven Friedrich <[EMAIL PROTECTED]> wrote: > On Monday 06 June 2005 01:16 am, Ted Mittelstaedt wrote: > > So the next step is trying to substitute a different vendor's burner in > > the FreeBSD > > system. If it gives you the same errors, the problem is most likely not > > in the > > burner, and most likely in the software drivers. With that done, you > > would > > have enough data to write a GOOD pr and submit it. If the substitute > > works > > OK then you know it's firmware bugs in the burner you have, and a PR > > would not > > be warranted. > > > > Ted > I've gotten newer firmware from Toshiba but it didn't help from > http://sdd.toshiba.com > > The asc, ascq codes are available at http://www.t10.org/lists/asc-num.htm > In an attempt to determine if buffer underruns are the problem, I've used > nice > -18 (even -35) cdrecord... Buffer underruns cause cdrecord to stop burning if you aren't using the burnfree driver option. If you can write the whole image, you probably have no buffer underruns. If you use burnfree, you can use the -v option to see a count of the prevented buffer underruns. > If I'm burning an iso image, do I need to use SAO (DAO) instead of TAO? You should burn SAO whenever possible, but this has nothing to do with the image type. Fabian -- http://www.fabiankeil.de/ pgptm6CBMiZ5x.pgp Description: PGP signature
Re: link in handbook appears to be broken
"Steven Friedrich" <[EMAIL PROTECTED]> wrote: >> If I'm burning an iso image, do I need to use SAO (DAO) instead of TAO? "Ted Mittelstaedt" <[EMAIL PROTECTED]> wrote: > Yes, use DAO. But the software should know that since it's an ISO to > do that automatically. An ISO image on a multisession CD would be > senseless, of course. An ISO image needs to be written and the CD > closed in a single session. Why do you think an ISO image on a multisession CD would be senseless? The usual way to create multisession CDs is to put one ISO image after the other. If you close the CD after burning the ISO image or not doesn't matter. Fabian -- http://www.fabiankeil.de/ pgp6wrAGbU598.pgp Description: PGP signature
Re: link in handbook appears to be broken
Ted Mittelstaedt wrote: Hi Steven Please don't waste time with this. development of burncd is pretty much dead. Even the CD's on the list that it supported (of which I have one) often didn't work right. And all of them are old, no longer in production. burncd is there so if you have a burner sitting around you can plug it in and see if it works. These days most people use the ATAPI/CAM driver with IDE burners, see: Is it recommended to remove the device atapicd (assuming that drops the /dev/acd0) from the kernel config file if you are using the ATAPI/CAM driver? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.ht ml#ATAPICAM Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Steven Friedrich Sent: Friday, June 03, 2005 7:48 PM To: freebsd-questions@freebsd.org Subject: link in handbook appears to be broken I'm trying to follow the link http://www.freebsd.dk/ata/ on page http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati ng-cds.html Anybody know where else I might find this info? -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ 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]" -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: link in handbook appears to be broken
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Steven >Friedrich >Sent: Monday, June 06, 2005 6:23 PM >To: Ted Mittelstaedt >Cc: freebsd-questions@freebsd.org >Subject: Re: link in handbook appears to be broken > [some deleted] >I have two physical systems and I have mobile racks in them. I >can pull out >freeBSD 4.11 and insert freeBSD 5.4. I have discovered that I >can write to >the 4x-12x media when using freeBSD 5.4. I don't even have to >use DAO (SAO) >mode, I can use TAO. > >I have freeBSD 4.11 set up the same as 5.4 as far as I can. I >have atapicam, >and the scsi bus and devices mentioned in the handbook. cd0 is >reported when >I boot, but 4.11 doesn't have devfs, so it's not a usable device. But >cdrecord is using dev=1,0,0 anyway. After I write it with >cdrecord, I try to >mount it and I get an i/o error reported. When I use cdrecord >blank=all, >cdrecord reports errors indicating the media format is corrupt. > Perhaps the >write operation didn't complete under 4.11 but it does under 5.4? > >Anyway to determine what happened? >I don't believe that devfs is available under 4.11, but I >really don't believe >that's the culprit. Any ideas? > Use FreeBSD 5.4? Please keep in mind that 4.11 was the last release in the 4.X line. Yours is not the first screwy atapi bug reported for 4.11 that isn't in 5.X and it won't be the last. There are already now I think too many changes in the atapi code to make backporting a bug fix to be anything other than a tremendous chore. And some of the bugs people will run into are only fixed by the structural changes that went into 5.X Your only recourse I think if you want to burn CD's under 4.X is to find a different burner. I would look for something that is PIO mode only, that probably means finding an older one on EBay for a few bucks. I myself have had mixed sucess with atapi burners under FreeBSD as a matter of fact. And in fact I have also had some issues with readers. Just 2 weeks ago for example I brought up a new server on 5.4, and it wouldn't read it's CD reader. I pulled the reader out, took it home, exchanged it with a reader in one of my machines that was the same speed, (and it worked fine in that system) took that machine's reader back to the server whereupon it worked fine. You can read about this stupidity here: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/81082 I filed this bug mainly in case it might be useful for the atapi driver author, and in case it might be useful for a user with a similar problem, not because I expected it to be fixed. The motherboard in question isn't even in production anymore. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: link in handbook appears to be broken
On Monday 06 June 2005 02:58 pm, Ted Mittelstaedt wrote: > Yes, use DAO. But the software should know that since it's an ISO to > do that automatically. An ISO image on a multisession CD would be > senseless, of course. An ISO image needs to be written and the CD > closed in a single session. > > Ted > > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >Friedrich > >Sent: Monday, June 06, 2005 10:03 AM > >To: Ted Mittelstaedt > >Cc: freebsd-questions@freebsd.org > >Subject: Re: link in handbook appears to be broken > > > >On Monday 06 June 2005 01:16 am, Ted Mittelstaedt wrote: > >> >-Original Message- > >> >From: [EMAIL PROTECTED] > >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >> >Friedrich > >> >Sent: Sunday, June 05, 2005 7:24 PM > >> >To: Ted Mittelstaedt > >> >Cc: freebsd-questions@freebsd.org > >> >Subject: Re: link in handbook appears to be broken > >> > > >> >On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote: > >> >> >-Original Message- > >> >> >From: [EMAIL PROTECTED] > >> >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >> >> >Friedrich > >> >> >Sent: Sunday, June 05, 2005 8:20 AM > >> >> >To: Ted Mittelstaedt > >> >> >Cc: freebsd-questions@freebsd.org > >> >> >Subject: Re: link in handbook appears to be broken > >> >> > > >> >> >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: > >> >> >> Hi Steven > >> >> >> > >> >> >> Please don't waste time with this. development of > >> > > >> >burncd is pretty > >> > > >> >> >> much > >> >> >> dead. Even the CD's on the list that it supported (of which > >> >> > > >> >> >I have one) > >> >> > > >> >> >> often didn't work right. And all of them are old, no longer in > >> >> >> production. > >> >> >> burncd is there so if you have a burner sitting around > > > >you can plug > > > >> >> >> it in and see if it works. > >> >> >> > >> >> >> These days most people use the ATAPI/CAM driver with IDE > >> >> > > >> >> >burners, see: > >> >> > > >> >> > > >> >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati > >> >> >ng-cds.ht > >> >> > > >> >> >> ml#ATAPICAM > >> >> >> > >> >> >> Ted > >> >> > > >> >> >Ok, but I'm getting nearly the same error with cdrecord. > >> >> > > >> >> >cdrecord -blank=all -eject dev=toshiba seemed to work ok. > >> >> >cdrecord dev=toshiba cd1.iso didn't complain > >> >> >but then mount /cdrom produced > >> >> >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 > >> >> > > >> >> > > >> >> >Can someone tell me where to find the meanings of these codes? > >> >> > >> >> What you see is what you get - the error "MEDIUM ERROR" > > > >seems pretty > > > >> >> clear to me - it means that the CD you burned isn't readable. What > >> >> are you after - a masters thesis spewed out for every little error? > >> >> That would bloat the code. > >> >> > >> >> FreeBSD tells you there's an error it's your job to find out why > >> >> there is one. > >> >> > >> >> Since as you said in your other posting you are making good CD's at > >> >> low-speed burn, and frizbees at high speed burn, there is a > >> > > >> >good chance > >> > > >> >> you > >> >> are underrunning the buffer in the burner. Get a faster CPU > >> > > >> >or live with > >> > > >> >> lower speed burns. > >> >> > >> >> UNIX is a preemptive operating system. That means that > > > >during your CD > > > >> >> burn, if something else goes on in the system by some > > > >other proce
RE: link in handbook appears to be broken
Yes, use DAO. But the software should know that since it's an ISO to do that automatically. An ISO image on a multisession CD would be senseless, of course. An ISO image needs to be written and the CD closed in a single session. Ted >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Steven >Friedrich >Sent: Monday, June 06, 2005 10:03 AM >To: Ted Mittelstaedt >Cc: freebsd-questions@freebsd.org >Subject: Re: link in handbook appears to be broken > > >On Monday 06 June 2005 01:16 am, Ted Mittelstaedt wrote: >> >-Original Message- >> >From: [EMAIL PROTECTED] >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven >> >Friedrich >> >Sent: Sunday, June 05, 2005 7:24 PM >> >To: Ted Mittelstaedt >> >Cc: freebsd-questions@freebsd.org >> >Subject: Re: link in handbook appears to be broken >> > >> >On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote: >> >> >-Original Message- >> >> >From: [EMAIL PROTECTED] >> >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven >> >> >Friedrich >> >> >Sent: Sunday, June 05, 2005 8:20 AM >> >> >To: Ted Mittelstaedt >> >> >Cc: freebsd-questions@freebsd.org >> >> >Subject: Re: link in handbook appears to be broken >> >> > >> >> >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: >> >> >> Hi Steven >> >> >> >> >> >> Please don't waste time with this. development of >> > >> >burncd is pretty >> > >> >> >> much >> >> >> dead. Even the CD's on the list that it supported (of which >> >> > >> >> >I have one) >> >> > >> >> >> often didn't work right. And all of them are old, no longer in >> >> >> production. >> >> >> burncd is there so if you have a burner sitting around >you can plug >> >> >> it in and see if it works. >> >> >> >> >> >> These days most people use the ATAPI/CAM driver with IDE >> >> > >> >> >burners, see: >> >> > >> >> > >> >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati >> >> >ng-cds.ht >> >> > >> >> >> ml#ATAPICAM >> >> >> >> >> >> Ted >> >> > >> >> >Ok, but I'm getting nearly the same error with cdrecord. >> >> > >> >> >cdrecord -blank=all -eject dev=toshiba seemed to work ok. >> >> >cdrecord dev=toshiba cd1.iso didn't complain >> >> >but then mount /cdrom produced >> >> >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 >> >> > >> >> > >> >> >Can someone tell me where to find the meanings of these codes? >> >> >> >> What you see is what you get - the error "MEDIUM ERROR" >seems pretty >> >> clear to me - it means that the CD you burned isn't readable. What >> >> are you after - a masters thesis spewed out for every little error? >> >> That would bloat the code. >> >> >> >> FreeBSD tells you there's an error it's your job to find out why >> >> there is one. >> >> >> >> Since as you said in your other posting you are making good CD's at >> >> low-speed burn, and frizbees at high speed burn, there is a >> > >> >good chance >> > >> >> you >> >> are underrunning the buffer in the burner. Get a faster CPU >> > >> >or live with >> > >> >> lower speed burns. >> >> >> >> UNIX is a preemptive operating system. That means that >during your CD >> >> burn, if something else goes on in the system by some >other process, >> >> then your burning process gets paused. If the burner you are >> > >> >using has >> > >> >> a very small internal buffer than it will run out of data >and you will >> >> produce a frisbee. >> >> >> >> WinXP by contrast lets apps like Roxio basically halt the OS while >> >> your doing some time-critical operation. That's fine for a >> > >> >single-user >> > >> >> OS but pretty stupid for a server what has lots of people using it >> >> all the time. Tha
Re: link in handbook appears to be broken
On Monday 06 June 2005 01:16 am, Ted Mittelstaedt wrote: > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >Friedrich > >Sent: Sunday, June 05, 2005 7:24 PM > >To: Ted Mittelstaedt > >Cc: freebsd-questions@freebsd.org > >Subject: Re: link in handbook appears to be broken > > > >On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote: > >> >-Original Message- > >> >From: [EMAIL PROTECTED] > >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >> >Friedrich > >> >Sent: Sunday, June 05, 2005 8:20 AM > >> >To: Ted Mittelstaedt > >> >Cc: freebsd-questions@freebsd.org > >> >Subject: Re: link in handbook appears to be broken > >> > > >> >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: > >> >> Hi Steven > >> >> > >> >> Please don't waste time with this. development of > > > >burncd is pretty > > > >> >> much > >> >> dead. Even the CD's on the list that it supported (of which > >> > > >> >I have one) > >> > > >> >> often didn't work right. And all of them are old, no longer in > >> >> production. > >> >> burncd is there so if you have a burner sitting around you can plug > >> >> it in and see if it works. > >> >> > >> >> These days most people use the ATAPI/CAM driver with IDE > >> > > >> >burners, see: > >> > > >> > > >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati > >> >ng-cds.ht > >> > > >> >> ml#ATAPICAM > >> >> > >> >> Ted > >> > > >> >Ok, but I'm getting nearly the same error with cdrecord. > >> > > >> >cdrecord -blank=all -eject dev=toshiba seemed to work ok. > >> >cdrecord dev=toshiba cd1.iso didn't complain > >> >but then mount /cdrom produced > >> >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 > >> > > >> > > >> >Can someone tell me where to find the meanings of these codes? > >> > >> What you see is what you get - the error "MEDIUM ERROR" seems pretty > >> clear to me - it means that the CD you burned isn't readable. What > >> are you after - a masters thesis spewed out for every little error? > >> That would bloat the code. > >> > >> FreeBSD tells you there's an error it's your job to find out why > >> there is one. > >> > >> Since as you said in your other posting you are making good CD's at > >> low-speed burn, and frizbees at high speed burn, there is a > > > >good chance > > > >> you > >> are underrunning the buffer in the burner. Get a faster CPU > > > >or live with > > > >> lower speed burns. > >> > >> UNIX is a preemptive operating system. That means that during your CD > >> burn, if something else goes on in the system by some other process, > >> then your burning process gets paused. If the burner you are > > > >using has > > > >> a very small internal buffer than it will run out of data and you will > >> produce a frisbee. > >> > >> WinXP by contrast lets apps like Roxio basically halt the OS while > >> your doing some time-critical operation. That's fine for a > > > >single-user > > > >> OS but pretty stupid for a server what has lots of people using it > >> all the time. That is why people don't use WinXP for servers. > >> > >> You cna try playing with the nice command and your cd burns and see if > >> you can make any difference. > >> > >> Ted > > > >My machines (2) are 2.4 GHz pentium 4s. > > OK, in that case chances it's a buffer underrun are much lower. > > >I use the same drive > >and media under > >winXP and using Roxio, I've burned freeBSD 4.11 ISOs and booted > >from them. > >The Memorex 1x-4x media worked with cdrecord but the Memorex > >4x-12x media > >doesn't, even when I tell it to burn at 4x like the 1x-4x media did. > > > >I'm not expecting the software to decode the asc, ascq, and > >error codes, but I > >do expect to find them documented in a header or a book, man > >page, somewhere. > > They are document
RE: link in handbook appears to be broken
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Steven >Friedrich >Sent: Sunday, June 05, 2005 7:24 PM >To: Ted Mittelstaedt >Cc: freebsd-questions@freebsd.org >Subject: Re: link in handbook appears to be broken > > >On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote: >> >-Original Message- >> >From: [EMAIL PROTECTED] >> >[mailto:[EMAIL PROTECTED] Behalf Of Steven >> >Friedrich >> >Sent: Sunday, June 05, 2005 8:20 AM >> >To: Ted Mittelstaedt >> >Cc: freebsd-questions@freebsd.org >> >Subject: Re: link in handbook appears to be broken >> > >> >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: >> >> Hi Steven >> >> >> >> Please don't waste time with this. development of >burncd is pretty >> >> much >> >> dead. Even the CD's on the list that it supported (of which >> > >> >I have one) >> > >> >> often didn't work right. And all of them are old, no longer in >> >> production. >> >> burncd is there so if you have a burner sitting around you can plug >> >> it in and see if it works. >> >> >> >> These days most people use the ATAPI/CAM driver with IDE >> > >> >burners, see: >> > >> > >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati >> >ng-cds.ht >> > >> >> ml#ATAPICAM >> >> >> >> Ted >> > >> >Ok, but I'm getting nearly the same error with cdrecord. >> > >> >cdrecord -blank=all -eject dev=toshiba seemed to work ok. >> >cdrecord dev=toshiba cd1.iso didn't complain >> >but then mount /cdrom produced >> >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 >> > >> > >> >Can someone tell me where to find the meanings of these codes? >> >> What you see is what you get - the error "MEDIUM ERROR" seems pretty >> clear to me - it means that the CD you burned isn't readable. What >> are you after - a masters thesis spewed out for every little error? >> That would bloat the code. >> >> FreeBSD tells you there's an error it's your job to find out why >> there is one. >> >> Since as you said in your other posting you are making good CD's at >> low-speed burn, and frizbees at high speed burn, there is a >good chance >> you >> are underrunning the buffer in the burner. Get a faster CPU >or live with >> lower speed burns. >> >> UNIX is a preemptive operating system. That means that during your CD >> burn, if something else goes on in the system by some other process, >> then your burning process gets paused. If the burner you are >using has >> a very small internal buffer than it will run out of data and you will >> produce a frisbee. >> >> WinXP by contrast lets apps like Roxio basically halt the OS while >> your doing some time-critical operation. That's fine for a >single-user >> OS but pretty stupid for a server what has lots of people using it >> all the time. That is why people don't use WinXP for servers. >> >> You cna try playing with the nice command and your cd burns and see if >> you can make any difference. >> >> Ted >My machines (2) are 2.4 GHz pentium 4s. OK, in that case chances it's a buffer underrun are much lower. >I use the same drive >and media under >winXP and using Roxio, I've burned freeBSD 4.11 ISOs and booted >from them. >The Memorex 1x-4x media worked with cdrecord but the Memorex >4x-12x media >doesn't, even when I tell it to burn at 4x like the 1x-4x media did. > >I'm not expecting the software to decode the asc, ascq, and >error codes, but I >do expect to find them documented in a header or a book, man >page, somewhere. > They are documented, these guys have the docs: http://www.t13.org/ You will have to pay them for them. Or, go to the technical library of your nearest university and make copies of the appropriate pages of the standards. ASC = Associated Sense Code ASCQ = Associated Sense Code Qualifier These are codes returned to the driver by the CD reader, unexpectedly of course, which is why it errored. The software driver decoded enough to know that the cd reader is reporting a medium error, so it tells you that, then passes the sense code that the reader is returning. You could look up the sense code in the documentation provided by the manufacturer of the cdrom reader drive if you really want t
Re: link in handbook appears to be broken
On Sunday 05 June 2005 06:48 pm, Ted Mittelstaedt wrote: > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] Behalf Of Steven > >Friedrich > >Sent: Sunday, June 05, 2005 8:20 AM > >To: Ted Mittelstaedt > >Cc: freebsd-questions@freebsd.org > >Subject: Re: link in handbook appears to be broken > > > >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: > >> Hi Steven > >> > >> Please don't waste time with this. development of burncd is pretty > >> much > >> dead. Even the CD's on the list that it supported (of which > > > >I have one) > > > >> often didn't work right. And all of them are old, no longer in > >> production. > >> burncd is there so if you have a burner sitting around you can plug > >> it in and see if it works. > >> > >> These days most people use the ATAPI/CAM driver with IDE > > > >burners, see: > > > > > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati > >ng-cds.ht > > > >> ml#ATAPICAM > >> > >> Ted > > > >Ok, but I'm getting nearly the same error with cdrecord. > > > >cdrecord -blank=all -eject dev=toshiba seemed to work ok. > >cdrecord dev=toshiba cd1.iso didn't complain > >but then mount /cdrom produced > >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 > > > > > >Can someone tell me where to find the meanings of these codes? > > What you see is what you get - the error "MEDIUM ERROR" seems pretty > clear to me - it means that the CD you burned isn't readable. What > are you after - a masters thesis spewed out for every little error? > That would bloat the code. > > FreeBSD tells you there's an error it's your job to find out why > there is one. > > Since as you said in your other posting you are making good CD's at > low-speed burn, and frizbees at high speed burn, there is a good chance > you > are underrunning the buffer in the burner. Get a faster CPU or live with > lower speed burns. > > UNIX is a preemptive operating system. That means that during your CD > burn, if something else goes on in the system by some other process, > then your burning process gets paused. If the burner you are using has > a very small internal buffer than it will run out of data and you will > produce a frisbee. > > WinXP by contrast lets apps like Roxio basically halt the OS while > your doing some time-critical operation. That's fine for a single-user > OS but pretty stupid for a server what has lots of people using it > all the time. That is why people don't use WinXP for servers. > > You cna try playing with the nice command and your cd burns and see if > you can make any difference. > > Ted My machines (2) are 2.4 GHz pentium 4s. I use the same drive and media under winXP and using Roxio, I've burned freeBSD 4.11 ISOs and booted from them. The Memorex 1x-4x media worked with cdrecord but the Memorex 4x-12x media doesn't, even when I tell it to burn at 4x like the 1x-4x media did. I'm not expecting the software to decode the asc, ascq, and error codes, but I do expect to find them documented in a header or a book, man page, somewhere. -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: link in handbook appears to be broken
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Steven >Friedrich >Sent: Sunday, June 05, 2005 8:20 AM >To: Ted Mittelstaedt >Cc: freebsd-questions@freebsd.org >Subject: Re: link in handbook appears to be broken > > >On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: >> Hi Steven >> >> Please don't waste time with this. development of burncd is pretty >> much >> dead. Even the CD's on the list that it supported (of which >I have one) >> often didn't work right. And all of them are old, no longer in >> production. >> burncd is there so if you have a burner sitting around you can plug >> it in and see if it works. >> >> These days most people use the ATAPI/CAM driver with IDE >burners, see: >> >> >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati >ng-cds.ht >> ml#ATAPICAM >> >> Ted > >Ok, but I'm getting nearly the same error with cdrecord. > >cdrecord -blank=all -eject dev=toshiba seemed to work ok. >cdrecord dev=toshiba cd1.iso didn't complain >but then mount /cdrom produced >acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 > > >Can someone tell me where to find the meanings of these codes? > What you see is what you get - the error "MEDIUM ERROR" seems pretty clear to me - it means that the CD you burned isn't readable. What are you after - a masters thesis spewed out for every little error? That would bloat the code. FreeBSD tells you there's an error it's your job to find out why there is one. Since as you said in your other posting you are making good CD's at low-speed burn, and frizbees at high speed burn, there is a good chance you are underrunning the buffer in the burner. Get a faster CPU or live with lower speed burns. UNIX is a preemptive operating system. That means that during your CD burn, if something else goes on in the system by some other process, then your burning process gets paused. If the burner you are using has a very small internal buffer than it will run out of data and you will produce a frisbee. WinXP by contrast lets apps like Roxio basically halt the OS while your doing some time-critical operation. That's fine for a single-user OS but pretty stupid for a server what has lots of people using it all the time. That is why people don't use WinXP for servers. You cna try playing with the nice command and your cd burns and see if you can make any difference. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: link in handbook appears to be broken
On Saturday 04 June 2005 01:04 am, Ted Mittelstaedt wrote: > Hi Steven > > Please don't waste time with this. development of burncd is pretty > much > dead. Even the CD's on the list that it supported (of which I have one) > often didn't work right. And all of them are old, no longer in > production. > burncd is there so if you have a burner sitting around you can plug > it in and see if it works. > > These days most people use the ATAPI/CAM driver with IDE burners, see: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.ht > ml#ATAPICAM > > Ted Ok, but I'm getting nearly the same error with cdrecord. cdrecord -blank=all -eject dev=toshiba seemed to work ok. cdrecord dev=toshiba cd1.iso didn't complain but then mount /cdrom produced acd0: READ_BIG - MEDIUM ERROR asc=0x15 ascq=0x00 error=0x00 Man pages for burncd and cdrecord don't mention error codes. I looked briefly in the source and didn't see a header file referenced with the codes. I'm using Memorex CD-RW media in a Toshiba DVD-RW drive and this combo works under WinXP with Roxio, so I know the drive and media work. Can someone tell me where to find the meanings of these codes? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: link in handbook appears to be broken
Hi Steven Please don't waste time with this. development of burncd is pretty much dead. Even the CD's on the list that it supported (of which I have one) often didn't work right. And all of them are old, no longer in production. burncd is there so if you have a burner sitting around you can plug it in and see if it works. These days most people use the ATAPI/CAM driver with IDE burners, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.ht ml#ATAPICAM Ted >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Steven >Friedrich >Sent: Friday, June 03, 2005 7:48 PM >To: freebsd-questions@freebsd.org >Subject: link in handbook appears to be broken > > >I'm trying to follow the link http://www.freebsd.dk/ata/ on page >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creati >ng-cds.html > >Anybody know where else I might find this info? >-- >i386 FreeBSD 4.11-STABLE >There are 10 types of people in this world. Ones that >understand binary and >then, the others. >___ >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: Link to your website
> >I am working on a website featuring linux distributions and articles. >I read the legal page but I am still unclear on a few things. If I put >a picture feating your Powerlogo.gif on my site and add a link to >freebsd, will that be acceptable ? > Generally, yes. Of course, we are assuming you will say nice things about FreeBSD along with that link... Now, you realize that FreeBSD has nothing to do with Linux, other than it is capable of running most Linux applications along with its own. FreeBSD is a completely different [and superior in many people's estimation] OS, based on BSD UNIX, not on Linux or SVR4. jerry > > >[1]www.forsberg.at > > > >Chris Forsberg > > References > >1. http://www.forsberg.at/ > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Link to your website
[EMAIL PROTECTED] wrote: I am working on a website featuring linux distributions and articles. I read the legal page but I am still unclear on a few things. If I put a picture feating your Powerlogo.gif on my site and add a link to freebsd, will that be acceptable ? Some of the ports (mailman?) configure themselves to display the powerlogo.gif, so I'm pretty sure it would be fine for you, too. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: link to devfs
On Wed, Apr 13, 2005 at 01:47:47AM +0200, Piotr Ni?y?ski wrote: > Hi, > > It seems that linking to devfs (or at least /dev/random) does something > weird with the filesystem... How can I return from this state? Please explain your problem in more detail, showing e.g. what commands you ran and what problem you encountered. Kris pgpYddtvBc77k.pgp Description: PGP signature
Re: Link to new Russian FreeBSD searchpage. Plz. repost.
http://freebsd.rambler.ru/ On Friday 01 August 2003 22.24, Hasse wrote: > Hi. > Saw a link to a new Russian FreeBSD searchpage here in the archive a couple > of days ago. Unfortunately I've lost it and am not able to search the > mailarchives at FreeBSD.org > > Will sombody please post the link again ? -- Best Regards Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsupit broken (Re: Link??)
On Friday 28 March 2003 10:07 pm, Jordan K Hubbard wrote: > The maintainer is on vacation in Maui and will fix it just as soon as > he returns. He has only sporadic email connectivity and very slow > connectivity at that, too slow to actually do any "work" (nor would his > girlfriend look kindly on that during a vacation :). Well we can't have him in the doghouse can we? btw, nice to see you around here Jordan, how is golden delicious treating you? Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsupit broken (Re: Link??)
The maintainer is on vacation in Maui and will fix it just as soon as he returns. He has only sporadic email connectivity and very slow connectivity at that, too slow to actually do any "work" (nor would his girlfriend look kindly on that during a vacation :). On Friday, March 28, 2003, at 02:59 PM, Kris Kennaway wrote: On Fri, Mar 28, 2003 at 05:45:15PM -0500, taxman wrote: On Friday 28 March 2003 05:22 am, Eqab Almutairi wrote: Hello, seems this link dosnt work anymore right? ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/All/cvsupit-3.1.tgz at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current- stable.ht ml is there any other place? well the link is fine, the file's just not there. I don't know why. In the cvsupit is currently broken, and the maintainer hasn't yet fixed it. I've CC'ed him on this message as a friendly reminder. Kris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsupit broken (Re: Link??)
On Fri, Mar 28, 2003 at 05:45:15PM -0500, taxman wrote: > On Friday 28 March 2003 05:22 am, Eqab Almutairi wrote: > > Hello, > > > > seems this link dosnt work anymore right? > > > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/All/cvsupit-3.1.tgz > > > > at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.ht > >ml > > > > is there any other place? > > well the link is fine, the file's just not there. I don't know why. In the cvsupit is currently broken, and the maintainer hasn't yet fixed it. I've CC'ed him on this message as a friendly reminder. Kris pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Link??
On Friday 28 March 2003 05:22 am, Eqab Almutairi wrote: > Hello, > > seems this link dosnt work anymore right? > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/All/cvsupit-3.1.tgz > > at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.ht >ml > > is there any other place? well the link is fine, the file's just not there. I don't know why. In the meantime you can try: ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/All/cvsup-without-gui-16.1g.tgz read the handbook appendix on cvsup and you should be fine using that. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Link??
seems this link dosnt work anymore right? ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/All/cvsupit-3.1.tgz at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html I do not see that one around either... but I would just move ahead if I were you. install the cvsup-without-gui-16.1g.tgz package that can be found at: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All/ and look at the sample cvsup configuration in /usr/share/examples/cvsup/ If you have any questions, just ask again here. _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Link equalization?
On Fri, Nov 15, 2002 at 01:00:50PM +, Matthew Seaman wrote: > It certainly is. You can use Netgraph ng_one2many(4) to make a > sythetic NIC by bundling together a number of network cards. You > might find this page interesting: > > http://bsdvault.net/sections.php?op=viewarticle&artid=98 > > Cheers, > > Matthew Thanks for the pointer! - Tillman -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. Robert Heinlein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Link equalization?
On Thu, Nov 14, 2002 at 06:27:48PM -0600, Tillman wrote: > Is it possible to do something similar to Linux 2.4's ethernet link > "equalization" (round-robin'ing, really) as described at > http://www.linuxguruz.org/iptables/howto/2.4routing-10.html under > FreeBSD? I'm trying to extract more speed from my NFS server, and I've > already gotten about all I can out of 100Mbps by tuning :-) It certainly is. You can use Netgraph ng_one2many(4) to make a sythetic NIC by bundling together a number of network cards. You might find this page interesting: http://bsdvault.net/sections.php?op=viewarticle&artid=98 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Link Help Plz :) --no such file or dir???????
> > > i did it your way and i get 550 error says no such file or dir > any more suggestions? > RD Well, if it is from ftp, you probably have ftp set up to not allow them outside of their own directory - which is a normal thing to do. Check out ftp documentation. There is lots both in man and tutorials on the net. Do some Google searches and some archive and FAQ searches. jerry > > -Original Message- > From: Jerry McAllister [mailto:jerrymc@;clunix.cl.msu.edu] > Sent: Thursday, November 14, 2002 2:44 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: Link Help Plz :) > > > Wuzzup guys, > > > > I've found a few achived mails about linking to directories... I'm > > still confused a bit here... > > > > babybear-p200-128rm- > > 6-gig hdd for FreeBSD > > 40-gig hdd mounted at /www > > 80-gig hdd mounted at /myftp > > > > What I have is ftpusers home dir at /www/home/userdir > > I need a link inside their home dir that takes them to /myftp for read > > > only. > > > > Ln [options] link_name?link_to_dir? > > > > I'm not sure about the correct options... > > '-s' as in: > ln -s /home/some/dir lnname > > > > > Some give me a couple examples tx > > try 'man ln' > > and read only means you set permissions to only allow read > > check out 'man chmod' > > jerry > > > > > rd > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Link Help Plz :)
> > Wuzzup guys, > > I've found a few achived mails about linking to directories... > I'm still confused a bit here... > > babybear-p200-128rm- > 6-gig hdd for FreeBSD > 40-gig hdd mounted at /www > 80-gig hdd mounted at /myftp > > What I have is ftpusers home dir at /www/home/userdir > I need a link inside their home dir that takes them to /myftp for read > only. > > Ln [options] link_name?link_to_dir? > > I'm not sure about the correct options... '-s' as in: ln -s /home/some/dir lnname > > Some give me a couple examples tx try 'man ln' and read only means you set permissions to only allow read check out 'man chmod' jerry > > rd > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
