Majordomo results
-- subscribe freebsd-net You are trying to subscribe one mailing list another. Your subscription request has been rejected. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: - TFTP: Time out -
Ok. guys First, you only need one tftp configuration from /etc/inetd.conf file Either use /tftpboot or /usr/home/jcv. And killall -HUP inetd Then use following. get /c3640-i-mz.120-9.bin Remember that if you use -s /directory, actually tftp consider /directory as it's own / (root) directory. -s is used to change it's root directory to other . Because tftpd actually try to read "/tftpboot/c3640-i-mz.120-9.bin" from /tftpboot/tftpboot/c3640-i-mz.120-9.bin, it didn't work. Hyun Jean-Christophe Varaillon wrote: > > It is still not working between my machine and the cisco #( > > So, let summurize what I should fixe: > > === Make my FreeBSD machine as a tftp server === > > vi /etc/inetd.conf: > -- > tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot > tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /usr/home/jcv > -- > > -- > homer# ps auwx | grep inetd > root 108 0.0 0.5 1044 604 ?? Is 27Feb01 0:00.19 inetd -wW > jcv 23629 0.0 0.9 1548 1136 pc I+4:15PM 0:00.02 vi > /etc/inetd.conf > homer# kill -HUP 108 > -- > > I can see that the server is actually listening: > -- > %netstat -a | grep tftp > udp4 0 0 *.tftp *.* > % > -- > > = TFTP LOCALHOST TEST = > %su > Password: > > homer# cd /tftpboot > homer# ls -l > total 8544 > -rw-r--r-- 1 nobody nobody 4991380 Mar 6 15:39 > c3640-i-mz.120-7.XK1.bin > -rw-r--r-- 1 nobody nobody 3731009 Mar 6 15:03 c3640-i-mz.120-9.bin > > homer# cd /usr/home/jcv > homer# ls -l c3640-i-mz.120-9.bin > -rw-r--r-- 1 nobody nobody 0 Mar 6 16:03 c3640-i-mz.120-9.bin > homer# tftp 127.0.0.1 > > tftp> status > Connected to 127.0.0.1. > Mode: netascii Verbose: off Tracing: off > Rexmt-interval: 5 seconds, Max-timeout: 25 seconds > tftp> get /tftpboot/c3640-i-mz.120-9.bin > Transfer timed out. > > tftp> quit > > homer#vi /var/log/messages > ... > Mar 6 16:29:03 homer tftpd[23756]: read: Connection refused > Mar 6 16:29:08 homer tftpd[23758]: read: Connection refused > > = > > Oh by the way, when you make your IOS upgrade form your tftp server to > your router, you don't have to creat a blank file in flash ? > > Regards, > Jean-Christophe. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message begin:vcard n:Ryu;Hyunseig tel;fax:262-792-7655 tel;work:262-792-7965 x-mozilla-html:FALSE org:Norlight Telecommunications;Applications Engineering adr:;;275 North Corporate Drive;Brookfield;WI;53045;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Network Engineer note:MCSE, CCDA fn:Hyunseig Ryu end:vcard
Re: - TFTP: Time out -
Check the /etc/hosts.allow file. Put this in the first of the file. ALL : localhost 127.0.0.1 : allow ALL : your_router_ip_address : allow ALL : your_fbsd_ip_address : allow Hyun Jean-Christophe Varaillon wrote: > > On Tue, 6 Mar 2001, Andy [TECC NOPS] wrote: > > > OK, from that all seems fine. But remeber > > that doing %tftp localhost and then trying > > a local get failed, so I suspect that there > > is something wrong with the local setup somewhere. > > > > Right, how come you have two lines beginning "tftp" > > in your /etc/inetd.conf ?? Thought there should be > > only one (the one ending -s /tftpboot). > > I uncommented the first line and I add another line to allow also an tftp > access to /usr/home/jcv. > > > Big point here is that inetd is invoked -wW so it's > > wrapping. Check /etc/hosts.allow (or is it > > /usr/local/etc/hosts.allow > > these days? dunno, check up on it). > > Do a man inetd and check this yourself. > > -wW turn on TCP Wrapping. > By "vi /etc/inted.conf" we can see that tftp is using UDP > > wrapping is used in a matter of security, no ? > If yes, my router is , for the moment just close to my desk an it is not a > remote router. > > > Try doing %telnet localhost 69 and see if your > > daemon will even allow a connection. > > Even as a super user, the daemon does not allow the connection. > --- > %telnet localhost 69 > Trying 127.0.0.1... > telnet: connect to address 127.0.0.1: Connection refused > Trying ::1... > telnet: connect to address ::1: Connection refused > telnet: Unable to connect to remote host > % > --- > > If none of these we'll try again > > > > Regards > > Andy > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Christophe > > > Varaillon > > > Sent: 06 March 2001 16:37 > > > To: Andy [TECC NOPS] > > > Cc: [EMAIL PROTECTED] > > > Subject: RE: - TFTP: Time out - > > > > > > > > > It is still not working between my machine and the cisco #( > > > > > > So, let summurize what I should fixe: > > > > > > === Make my FreeBSD machine as a tftp server === > > > > > > vi /etc/inetd.conf: > > > -- > > > tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot > > > tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /usr/home/jcv > > > -- > > > > > > -- > > > homer# ps auwx | grep inetd > > > root 108 0.0 0.5 1044 604 ?? Is 27Feb01 0:00.19 inetd -wW > > > jcv 23629 0.0 0.9 1548 1136 pc I+4:15PM 0:00.02 vi > > > /etc/inetd.conf > > > homer# kill -HUP 108 > > > -- > > > > > > I can see that the server is actually listening: > > > -- > > > %netstat -a | grep tftp > > > udp4 0 0 *.tftp *.* > > > % > > > -- > > > > > > = TFTP LOCALHOST TEST = > > > %su > > > Password: > > > > > > homer# cd /tftpboot > > > homer# ls -l > > > total 8544 > > > -rw-r--r-- 1 nobody nobody 4991380 Mar 6 15:39 > > > c3640-i-mz.120-7.XK1.bin > > > -rw-r--r-- 1 nobody nobody 3731009 Mar 6 15:03 c3640-i-mz.120-9.bin > > > > > > homer# cd /usr/home/jcv > > > homer# ls -l c3640-i-mz.120-9.bin > > > -rw-r--r-- 1 nobody nobody 0 Mar 6 16:03 c3640-i-mz.120-9.bin > > > homer# tftp 127.0.0.1 > > > > > > tftp> status > > > Connected to 127.0.0.1. > > > Mode: netascii Verbose: off Tracing: off > > > Rexmt-interval: 5 seconds, Max-timeout: 25 seconds > > > tftp> get /tftpboot/c3640-i-mz.120-9.bin > > > Transfer timed out. > > > > > > tftp> quit > > > > > > homer#vi /var/log/messages > > > ... > > > Mar 6 16:29:03 homer tftpd[23756]: read: Connection refused > > > Mar 6 16:29:08 homer tftpd[23758]: read: Connection refused > > > > > > = > > > > > > Oh by the way, when you make your IOS upgrade form your tftp server to > > > your router, you don't have to creat a blank file in flash ? > > > > > > > > > Regards, > > > Jean-Christophe. > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-net" in the body of the message > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message begin:vcard n:Ryu;Hyunseig tel;fax:262-792-7655 tel;work:262-792-7965 x-mozilla-html:FALSE org:Norlight Telecommunications;Applications Engineering adr:;;275 North Corporate Drive;Brookfield;WI;53045;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Network Engineer note:MCSE, CCDA fn:Hyunseig Ryu end:vcard
Re: Netgraph is leaking node references
Harti Brandt wrote: > > Hi, > > it seems that netgraph is leaking references. One simple experiment to do > is to repeat 'ngctl types' several times: [fix just checked in] I won't say what it was exactlt but I must have been REALLY TIRED when I checked that bug in.. send pointy hat and C language tutorial to: julian -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: call for testers: port aggregation netgraph module
>Each link is checked once every second to see if the link is still up. >An attempt to send a packet over a dead link will cause the packet to >be shifted over to the next link in the bundle. Any chance this can be done through an async event rather than by polling? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: call for testers: port aggregation netgraph module
At 03:42 PM 03/10/2001, Justin T. Gibbs wrote: > >Each link is checked once every second to see if the link is still up. > >An attempt to send a packet over a dead link will cause the packet to > >be shifted over to the next link in the bundle. > >Any chance this can be done through an async event rather >than by polling? I've been meaning to ask about this...is there a reason that ethernet drivers dont call if_up and if_down like serial drivers on cable events? This is needed for load balancing so that the UP flag can be used instead of polling or an event. Of course a polling protocol is needed also. Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: call for testers: port aggregation netgraph module
> >Each link is checked once every second to see if the link is still up. > >An attempt to send a packet over a dead link will cause the packet to > >be shifted over to the next link in the bundle. > > Any chance this can be done through an async event rather > than by polling? If there was, I would have done it. MII transceivers can't send an interrupt back through the MAC unless the MAC supports it, and many don't. Consequently, the MII spec says nothing about async notification of anything. You have to poll. Resistance is futile. Gigabit MII transceivers are another matter. Polling and gigabit speeds don't go to gether very well. All of the GMII transceivers I've seen (Tigon and SysKonnect cards) have an signal pin of some kind that's wired to an external interrupt source pin on the MAC. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: call for testers: port aggregation netgraph module
>> >Each link is checked once every second to see if the link is still up. >> >An attempt to send a packet over a dead link will cause the packet to >> >be shifted over to the next link in the bundle. >> >> Any chance this can be done through an async event rather >> than by polling? > >If there was, I would have done it. Perhaps it would be best to create an interface that allows async notification but to provide a default implementation of the interface that polls? This would allow hardware that has a mechanism to detect the state change to override the default method while all other cards "just work" without modification by polling. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: call for testers: port aggregation netgraph module
> >> >Each link is checked once every second to see if the link is still up. > >> >An attempt to send a packet over a dead link will cause the packet to > >> >be shifted over to the next link in the bundle. > >> > >> Any chance this can be done through an async event rather > >> than by polling? > > > >If there was, I would have done it. > > Perhaps it would be best to create an interface that allows async > notification but to provide a default implementation of the interface > that polls? This would allow hardware that has a mechanism to detect > the state change to override the default method while all other > cards "just work" without modification by polling. Perhaps somebody who is not me should investigate this then. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
