- 1. How to determine source ip address (score: 1)
- Author: nnis@xxxxxxxxx>
- Date: Mon, 10 Sep 2001 20:23:17 +0100
- I'm writing a network app (currently on linux 2.2.18, but soon moving to 2.4) that needs to build up ip & tcp packets manually. So my question is how do I determine the source ip address to use for
- /archives/netdev/2001-09/msg00057.html (8,440 bytes)
- 2. Re: How to determine source ip address (score: 1)
- Author: een <ak@xxxxxx>
- Date: Mon, 10 Sep 2001 16:42:44 -0400
- How low in the protocol stack are you going? If you use an IP raw socket with IP_HDRINCL and just leave the sending address filled with zeros, then it will be filled in with the default address for t
- /archives/netdev/2001-09/msg00060.html (9,051 bytes)
- 3. Re: How to determine source ip address (score: 1)
- Author: xxxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 01:43:14 +0000 (GMT)
- Looking in udp_sendmsg and raw_sendmsg() I don't see the saddr argument in the route lookup call to depend on the IP_HDRINCL option (which is an raw socket option only). The same mistake (as your as
- /archives/netdev/2001-09/msg00068.html (10,313 bytes)
- 4. Re: How to determine source ip address (score: 1)
- Author: xxxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 18:47:07 +0100
- On Mon, 10 Sep 2001, Christopher Friesen wrote: Padraig Brady wrote: I'm writing a network app (currently on linux 2.2.18, but soon moving to 2.4) that needs to build up ip & tcp packets manually. So
- /archives/netdev/2001-09/msg00072.html (12,087 bytes)
- 5. Re: How to determine source ip address (score: 1)
- Author: @xxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 22:32:45 +0000 (GMT)
- The checksum is calculated for you in raw_getrawfrag() getsockname() gives it to you after connect() to the DGRAM socket. You have to, if you need the source address Hm, then you have to create a no
- /archives/netdev/2001-09/msg00073.html (8,864 bytes)
- 6. Re: How to determine source ip address (score: 1)
- Author: sov <ja@xxxxxx>
- Date: Tue, 11 Sep 2001 16:44:17 -0400
- Minor problem with this: what if you're routing based on source addresses? If the outgoing address that you pick influences which route/interface you use, this won't work. By far the simplest method
- /archives/netdev/2001-09/msg00074.html (9,130 bytes)
- 7. Re: How to determine source ip address (score: 1)
- Author: sov <ja@xxxxxx>
- Date: Tue, 11 Sep 2001 21:50:36 +0200
- Hello! When sending IP datagram, source IP address is choosen by the kernel just picking up the one bound to the outgoing interface (actually I never thought about this could work when multiple addr
- /archives/netdev/2001-09/msg00076.html (10,540 bytes)
- 8. Re: How to determine source ip address (score: 1)
- Author: @xxxxxxxxxxxxx>
- Date: Wed, 12 Sep 2001 12:06:12 +0100
- On Tue, 11 Sep 2001, Padraig Brady wrote: Chris, I'm only filling in the TCP header, and I realise the IP header will be filled appropriately when sent. However I need to calculate the checksum for t
- /archives/netdev/2001-09/msg00077.html (10,389 bytes)
- 9. How to determine source ip address (score: 1)
- Author: Padraig Brady <padraig@xxxxxxxxxxxxx>
- Date: Mon, 10 Sep 2001 20:23:17 +0100
- Hi, I'm writing a network app (currently on linux 2.2.18, but soon moving to 2.4) that needs to build up ip & tcp packets manually. So my question is how do I determine the source ip address to use f
- /archives/netdev/2001-09/msg00194.html (8,224 bytes)
- 10. Re: How to determine source ip address (score: 1)
- Author: "Christopher Friesen" <cfriesen@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Sep 2001 16:42:44 -0400
- How low in the protocol stack are you going? If you use an IP raw socket with IP_HDRINCL and just leave the sending address filled with zeros, then it will be filled in with the default address for t
- /archives/netdev/2001-09/msg00197.html (9,075 bytes)
- 11. Re: How to determine source ip address (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Tue, 11 Sep 2001 01:43:14 +0000 (GMT)
- Hello, Looking in udp_sendmsg and raw_sendmsg() I don't see the saddr argument in the route lookup call to depend on the IP_HDRINCL option (which is an raw socket option only). The same mistake (as y
- /archives/netdev/2001-09/msg00205.html (10,338 bytes)
- 12. Re: How to determine source ip address (score: 1)
- Author: Padraig Brady <padraig@xxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 18:47:07 +0100
- Hello, I'm writing a network app (currently on linux 2.2.18, but soon moving to 2.4) that needs to build up ip & tcp packets manually. So my question is how do I determine the source ip address to u
- /archives/netdev/2001-09/msg00209.html (11,958 bytes)
- 13. Re: How to determine source ip address (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Tue, 11 Sep 2001 22:32:45 +0000 (GMT)
- Hello, The checksum is calculated for you in raw_getrawfrag() getsockname() gives it to you after connect() to the DGRAM socket. You have to, if you need the source address Hm, then you have to creat
- /archives/netdev/2001-09/msg00210.html (8,888 bytes)
- 14. Re: How to determine source ip address (score: 1)
- Author: "Christopher Friesen" <cfriesen@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 16:44:17 -0400
- Minor problem with this: what if you're routing based on source addresses? If the outgoing address that you pick influences which route/interface you use, this won't work. By far the simplest method
- /archives/netdev/2001-09/msg00211.html (9,228 bytes)
- 15. Re: How to determine source ip address (score: 1)
- Author: Gigi Sullivan <sullivan@xxxxxxxxxxxxx>
- Date: Tue, 11 Sep 2001 21:50:36 +0200
- Aiee :) Hello! When sending IP datagram, source IP address is choosen by the kernel just picking up the one bound to the outgoing interface (actually I never thought about this could work when multip
- /archives/netdev/2001-09/msg00213.html (10,678 bytes)
- 16. Re: How to determine source ip address (score: 1)
- Author: Padraig Brady <padraig@xxxxxxxxxxxxx>
- Date: Wed, 12 Sep 2001 12:06:12 +0100
- Hello, Chris, I'm only filling in the TCP header, and I realise the IP header will be filled appropriately when sent. However I need to calculate the checksum for the TCP header which is actually ca
- /archives/netdev/2001-09/msg00214.html (10,496 bytes)
This search system is powered by
Namazu