Mailing List Archive

Jason Gerfen wrote:
>
> When attempting to setup tftpd I have found that it only utilized the
> last aliased interace in the list of ifconfig and handed out pxeboot
> requests on the one subnet vs. all subnets that any aliased interface is
> using.
>
> I did find a piece of code or patch someone submitted regarding this but
> it did not work correctly. Is this something that can modified to listen
> on any aliased interface or multiple network interfaces?
>

That's nonsense. At least tftp-hpa listens on the universal address
(*:tftp), and will attempt to respond using the same address that the
client sent the request to.

However, as required by the protocol, it doesn't have a continuous
connection, but opens a new socket for the connection.

You might have your routing tables set up incorrectly, or have
firewall/masquerading rules wrong.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Ok well if that is a valid statement then here is the setup I am working
with:

Slackware 9.1
i686
Kernel 2.4.20

Output of lspci:
...
00:08.0 Ethernet controller: Intel Corp. 82544EI Gigabit Ethernet
Controller (Copper) (rev 02)
...
02:08.0 Ethernet controller: 3Com Corporation 3c980-TX 10/100baseTX NIC
[Python-T] (rev 78)
02:09.0 Ethernet controller: 3Com Corporation 3c980-TX 10/100baseTX NIC
[Python-T] (rev 78)

output of ifconfig:
eth2 Link encap:Ethernet HWaddr 00:02:B3:BC:46:88
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52811863 errors:2929 dropped:2929 overruns:0 frame:0
TX packets:29963368 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1829756632 (1744.9 Mb) TX bytes:3530833562 (3367.2 Mb)
Interrupt:11 Base address:0x1800 Memory:f4020000-f4040000

eth2.461 Link encap:Ethernet HWaddr 00:02:B3:BC:46:88
inet addr:155.97.16.254 Bcast:155.97.16.255 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1698415 errors:0 dropped:0 overruns:0 frame:0
TX packets:572630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:181122922 (172.7 Mb) TX bytes:207826591 (198.1 Mb)

eth2.471 Link encap:Ethernet HWaddr 00:02:B3:BC:46:88
inet addr:155.97.17.166 Bcast:155.97.17.191 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25954039 errors:0 dropped:0 overruns:0 frame:0
TX packets:1013309 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2803177660 (2673.3 Mb) TX bytes:246954818 (235.5 Mb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2073 errors:0 dropped:0 overruns:0 frame:0
TX packets:2073 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:158102 (154.3 Kb) TX bytes:158102 (154.3 Kb)

Output of netstat:
udp 0 0 *:bootps *:*
udp 0 0 *:tftp *:*

I am looking at the following threads as well:
http://syslinux.zytor.com/archives/2006-February/006546.html
http://syslinux.zytor.com/archives/2006-February/006556.html

What else do you need? And I appreciate the prompt response on this.

H. Peter Anvin wrote:
> Jason Gerfen wrote:
>> When attempting to setup tftpd I have found that it only utilized the
>> last aliased interace in the list of ifconfig and handed out pxeboot
>> requests on the one subnet vs. all subnets that any aliased interface is
>> using.
>>
>> I did find a piece of code or patch someone submitted regarding this but
>> it did not work correctly. Is this something that can modified to listen
>> on any aliased interface or multiple network interfaces?
>>
>
> That's nonsense. At least tftp-hpa listens on the universal address
> (*:tftp), and will attempt to respond using the same address that the
> client sent the request to.
>
> However, as required by the protocol, it doesn't have a continuous
> connection, but opens a new socket for the connection.
>
> You might have your routing tables set up incorrectly, or have
> firewall/masquerading rules wrong.
>
> -hpa
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>


--
Jason Gerfen

"It's not my problem... Wooo Hooo!"

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Jason Gerfen wrote:
> Ok well if that is a valid statement then here is the setup I am working
> with:
>
> Slackware 9.1
> i686
> Kernel 2.4.20
>

Wow. Ancient. Your tftp-hpa is probably also prehistoric.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Thats what I needed. Thanks.


H. Peter Anvin wrote:
> Jason Gerfen wrote:
>> Ok well if that is a valid statement then here is the setup I am working
>> with:
>>
>> Slackware 9.1
>> i686
>> Kernel 2.4.20
>>
>
> Wow. Ancient. Your tftp-hpa is probably also prehistoric.
>
> -hpa
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX@zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>


--
Jason Gerfen

"It's not my problem... Wooo Hooo!"

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.