Mark Sargent wrote:
Mark Sargent wrote:
Alexander Apprich wrote:
Mark Sargent wrote:
Alexander Apprich wrote:
Mark,
Mark Sargent wrote:
[snip]
Hmmm, can you ping 192.168.168.12 from the switch? gw-lan-1#ping 10.0.0.129
Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.0.0.129, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Mark Sargent.
Alex
Hi All,
yes, Alex, it's pingable from the switch,
Switch>ping 192.168.168.12
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.168.12, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/202/1006 ms
Cheers.
Tell me if I should give up on this :-)
could you try tftp from another linux box...
apprich@cassini apprich $ tftp tftp> connect (to) elmstreet tftp> status Connected to elmstreet.science-computing.de. Mode: netascii Verbose: off Tracing: off Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
Mark Sargent.
Alex
Hi All,
Alex, I don't have another Linux box here at work. I have 2 @ home, though, and have installed tftp-server/client on both. Over the weekend, I hope to get a chance to test tftp on them. I may even take home a switch and realy test it. Keep you posted. Cheers.
Mark Sargent.
Hi All,
1 question I do have with this; why does netstat -nutlp show xinetd listening 3 times on port 69..? Shouldn't there only be 1 instance.?
udp 0 0 0.0.0.0:69 0.0.0.0:* 4940/xinetd
udp 0 0 0.0.0.0:69 0.0.0.0:* 4940/xinetd
udp 0 0 0.0.0.0:69 0.0.0.0:* 4940/xinetd
Cheers.
Mark Sargent.
Hi All,
at home, connected 2 linux machines, allowed tftp connections through firestarter, and whoom, it worked. I truly believe it's to do with xinetd.d running on port 69 x 3 as both machines here at home aren't. Any suggestioins for fixing this.? Cheers.
Mark Sargent.
