Re: isp connection woes
- Original Message - From: "Aaron Burke" <[EMAIL PROTECTED]> To: "Brian Henning" <[EMAIL PROTECTED]> Sent: Wednesday, February 26, 2003 1:36 PM Subject: RE: isp connection woes (snip) > > i now know that i am having problems connecting to my dhcp server. > can you try the following? (after first changing the ip address to > 0.0.0.0? > dhclient > > Then do an ifconfig and see if you got an address? > > > i am in the process of changing the dhcp code (at line 159 in > > /usr/src/contrib/isc-dhcp/common/packet.c) > > i changed this to 128. Then i am going to rebuild everything. > > i was not able to find out the ip address of the dhcp server that > > my isp uses so > > i hope this solves the problem. any other suggestions? it seems > > odd that i would > > have to make this kind of a change to get dhcp to work.. do i need to add > > anything to my rc.conf to enable dhcp? > Yes, I use interface ed0 to get an internet ip from my ISP. > I use the following: > ifconfig_ed0="DHCP" > > > > > rebuild everything > > -- > > cd /usr/src && make buildworld > > cd /usr/src && make buildkernel > > cd /usr/src && make installkernel > > < reboot into single user mode > > > boot -s > > fsck -p > > mount -a > > cd /usr/src && mergemaster -p > > cd /usr/src && make installworld > > cd /usr/src && mergemaster > > reboot > This is way too much work to solve a dns issue. > I mentioned in a previous message on this thread > that you should be no more than a hop or two from > your dhcp server. And for the benefit of people > that are not aware of how DNS works, here is an > example: (For the record, this is off the top > of my head, I expect several people to see a flaw > in my description, but I am not here to argue about > that). > > Step 1: DHCP Client sends and ethernet broadcast > to the address 255.255.255.255:67 from address > 0.0.0.0:68 . (67=bootps, 68=bootpc) > > Step 2: All DHCP servers (sometimes there are more > than one) respond to the client via a standard > packet. The server knows the MAC address of the > client. Every packet on a local area network has > a unique MAC address. > > Step 3: If the client is happy with the address > it will respond to the server with a request for > the ip that the server proposed. > > Step 4: The server will make a note of this and > approve the connection. It will send a packet > back to the client saying that it has permission > to use the address. > > One thing to note is that ethernet broadcast > packets do not usually leave the network interface. > The default that you mention, 16, is a lot of hops > from the client. And DHCP packets are (not sure on > this) sent as UDP packets. Which are not guarenteed > to get to the destination (period). To think of this > a different way, I can be in New York City from my > location in Oregon in 13 hops. > > > > > Thanks, > > brian > Thats what we are here for. > Hello- Thanks to all who helped me get my bsd machine connected to my isp using dhcp. makeing the TTL change to /usr/src/contrib/isc-dhcp/common/packet.c seemed to fix my problem. i know it seems odd to some of you that I would need more than 16 hops, but apparently the ATTBI network is a little different. Going forward I plan on installing natd and some firewall software. Cheers, brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: isp connection woes
- Original Message - From: "Bill Moran" <[EMAIL PROTECTED]> To: "Brian Henning" <[EMAIL PROTECTED]> Cc: "freebsd" <[EMAIL PROTECTED]> Sent: Tuesday, February 25, 2003 11:16 AM Subject: Re: isp connection woes > Brian Henning wrote: > > - Original Message - > > From: "Bill Moran" <[EMAIL PROTECTED]> > >>Brian Henning wrote: > >> > >>> Their network design supports no more than 16 hops on the > >>> way to > >>>a DHCP server, > >>>but increasing the (hard-coded) TTL > >>>(at line 159 in /usr/src/contrib/isc-dhcp/common/packet.c) can help fix the > >>>problem. > >>>I would like to manually try to connect to my isp before i try changing the > >>> code > >>>for DHCP. > >>>I got my network info from my lrp operating system. I would like to switch > >>> that > >>>to bsd. > >>>can i use traceroute to find out the number of hops i am currently taking to > >>> get > >>>to my isp's dhcp server? > Ok, i am able to connect to my isp via a manual configuration of my network. i set my ip address and my default route in rc.conf and i set my dns in resolv.conf i now know that i am having problems connecting to my dhcp server. i am in the process of changing the dhcp code (at line 159 in /usr/src/contrib/isc-dhcp/common/packet.c) i changed this to 128. Then i am going to rebuild everything. i was not able to find out the ip address of the dhcp server that my isp uses so i hope this solves the problem. any other suggestions? it seems odd that i would have to make this kind of a change to get dhcp to work.. do i need to add anything to my rc.conf to enable dhcp? rebuild everything -- cd /usr/src && make buildworld cd /usr/src && make buildkernel cd /usr/src && make installkernel < reboot into single user mode > boot -s fsck -p mount -a cd /usr/src && mergemaster -p cd /usr/src && make installworld cd /usr/src && mergemaster reboot Thanks, brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: isp connection woes
Brian Henning wrote: - Original Message - From: "Bill Moran" <[EMAIL PROTECTED]> Brian Henning wrote: Their network design supports no more than 16 hops on the way to a DHCP server, but increasing the (hard-coded) TTL (at line 159 in /usr/src/contrib/isc-dhcp/common/packet.c) can help fix the problem. I would like to manually try to connect to my isp before i try changing the code for DHCP. I got my network info from my lrp operating system. I would like to switch that to bsd. can i use traceroute to find out the number of hops i am currently taking to get to my isp's dhcp server? Had another thought, can you traceroute from the machine that is properly connecting? Are you sure that you can't get an IP address because of the TTL? I find it very odd that the DHCP server would be that far away, but stranger things have happened. manual configuration ifconfig_rl0="inet 66.41.139.87 netmask 255.255.248.0"#66.41.139.87/21 ifconfig_rl1="inet 192.168.1.254 netmask 255.255.255.0" default_router="66.41.136.1 rl0" This should be: defaultrouter="66.41.136.1" default_router="192.168.1.254 rl1" ^ This is wrong. Don't put that in. Bill, Why do i not need to have two default routes, I have 2 networks? I am sure you are correct, I guess i just don't understand why. A "default route" or "default gateway" is defined as the place the software sends traffic when it doesn't know how else to reach the machine in question. The assumption is that the "default route" computer will know where to send it. Other routes are added automagically, without needing your intervention. For example, when you ifconfig the rl1 interface, the network software automatically adds a route to 192.168.1.*, based on the IP/netmask that you configured. The network software then knows that all computers in that range can be reached through that network card. Additionally, having a default route that points back to itself results in an infinite loop (if the machine will even let you do it). The effect is: machine doesn't know how to reach host, so sends to default route, doesn't know how to reach host, sends to default route. It just keeps receiving the same traffic that it doesn't know what to do with. is there a way i can find out the ip addr of my dhcp server? Call your ISP, or if you have a machine that is working properly, check where it got it's IP address. Most OSes will tell you (even Windows). does this even work: default_router="192.168.1.254 rl1" No. "default_router" is a syntax error, it should be "defaultrouter" and the interface name at the end is not supposed to be there. The system will automagically determine the interface that belongs to the route. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: isp connection woes
(snip) You asked if you can ping your DHCP server > > Don't see why not, assuming: > > 1) The DHCP server returns icmp echo requests > > 2) You know the IP of the DHCP server > > > > > manual configuration > > > > > > ifconfig_rl0="inet 66.41.139.87 netmask 255.255.248.0" > #66.41.139.87/21 If you are using DHCP you will want to set this to ifconfig_rl0="DHCP" > > > ifconfig_rl1="inet 192.168.1.254 netmask 255.255.255.0" > > > > > > default_router="66.41.136.1 rl0" > > This should be: > > defaultrouter="66.41.136.1" I agree. > > > default_router="192.168.1.254 rl1" > >^ > > This is wrong. Don't put that in. Thats correct, and also dont include the network adapter name. > > > domain the-matrix.net > > > nameserver 63.240.76.19 > > > nameserver 204.127.198.19 > > This goes in your /etc/resolv.conf > > Bill, > > Why do i not need to have two default routes, > I have 2 networks? The default routes have nothing to do with how many networks you are attached to. > I am sure you > are correct, I guess i just don't understand why. > is there a way i can find out the ip addr of my > dhcp server? Yes, see /var/db/dhclient.leases . Dont worry that there are serveral different addresses in there. dhclient just appends the current lease to the end of the file. > does this even work: default_router="192.168.1.254 rl1" I dont think that it does. You can find out by typing 'netstat -r'. It will give you a listing of your IP routes. > Thanks again for the help, > Brian Once again, thats what we are here for. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: isp connection woes
(snip) > I have ATTBI for an isp, someone told me that the IP TTL is > expiring on the way to the server. Their network design > supports no more than 16 hops on the way to a DHCP server, > but increasing the (hard-coded) TTL (at line 159 in > /usr/src/contrib/isc-dhcp/common/packet.c) can help fix the > problem. 99.9% of users are no more than two hops from the DHCP server. 16 hops seems way too high. But perhaps your isp doesnt agree with my observations. > I would like to manually try to connect to my isp > before i try changing the code for DHCP. > I got my network info from my lrp operating system. I would like > to switch that to bsd. > can i use traceroute to find out the number of hops i am > currently taking to get > to my isp's dhcp server? Yes, you can. The lease information should be in /var/db/dhclient.leases . > > > manual configuration > > ifconfig_rl0="inet 66.41.139.87 netmask 255.255.248.0"#66.41.139.87/21 > ifconfig_rl1="inet 192.168.1.254 netmask 255.255.255.0" > > default_router="66.41.136.1 rl0" > default_router="192.168.1.254 rl1" If this info is in your rc.conf file, you will want to comment out the second default router (rl1). Ethernet hosts dont need additional routes to be set up to communicate with other hosts on the same chunk of your ethernet. > domain the-matrix.net > nameserver 63.240.76.19 > nameserver 204.127.198.19 Are you serving out a domain called the-matrix.net? Are you running your own DNS server? > > is there anything else i need to manually connect to my isp? That depends on how they want to authenticate thier users. If they are using PPPoE then yes. If not, then it should work fine now. I think removing the second instance of default_router from your rc.conf file will fix the communication issues. > > thanks, Thats what we are here for. > > brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: isp connection woes
- Original Message - From: "Bill Moran" <[EMAIL PROTECTED]> To: "Brian Henning" <[EMAIL PROTECTED]> Cc: "freebsd" <[EMAIL PROTECTED]> Sent: Tuesday, February 25, 2003 9:53 AM Subject: Re: isp connection woes > Brian Henning wrote: > > I have ATTBI for an isp, someone told me that the IP TTL is expiring on the way > > to the server. Their network design supports no more than 16 hops on the way to > > a DHCP server, > > but increasing the (hard-coded) TTL > > (at line 159 in /usr/src/contrib/isc-dhcp/common/packet.c) can help fix the > > problem. > > I would like to manually try to connect to my isp before i try changing the code > > for DHCP. > > I got my network info from my lrp operating system. I would like to switch that > > to bsd. > > can i use traceroute to find out the number of hops i am currently taking to get > > to my isp's dhcp server? > > Don't see why not, assuming: > 1) The DHCP server returns icmp echo requests > 2) You know the IP of the DHCP server > > > manual configuration > > > > ifconfig_rl0="inet 66.41.139.87 netmask 255.255.248.0"#66.41.139.87/21 > > ifconfig_rl1="inet 192.168.1.254 netmask 255.255.255.0" > > > > default_router="66.41.136.1 rl0" > > This should be: > defaultrouter="66.41.136.1" > > > default_router="192.168.1.254 rl1" >^ > This is wrong. Don't put that in. > > > domain the-matrix.net > > nameserver 63.240.76.19 > > nameserver 204.127.198.19 > > This goes in your /etc/resolv.conf > > > is there anything else i need to manually connect to my isp? > > As long as they allow the use of that IP, no. You should be > good to go. > > -- > Bill Moran > Potential Technologies > http://www.potentialtech.com > Bill, Why do i not need to have two default routes, I have 2 networks? I am sure you are correct, I guess i just don't understand why. is there a way i can find out the ip addr of my dhcp server? does this even work: default_router="192.168.1.254 rl1" Thanks again for the help, Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: isp connection woes
Brian Henning wrote: I have ATTBI for an isp, someone told me that the IP TTL is expiring on the way to the server. Their network design supports no more than 16 hops on the way to a DHCP server, but increasing the (hard-coded) TTL (at line 159 in /usr/src/contrib/isc-dhcp/common/packet.c) can help fix the problem. I would like to manually try to connect to my isp before i try changing the code for DHCP. I got my network info from my lrp operating system. I would like to switch that to bsd. can i use traceroute to find out the number of hops i am currently taking to get to my isp's dhcp server? Don't see why not, assuming: 1) The DHCP server returns icmp echo requests 2) You know the IP of the DHCP server manual configuration ifconfig_rl0="inet 66.41.139.87 netmask 255.255.248.0"#66.41.139.87/21 ifconfig_rl1="inet 192.168.1.254 netmask 255.255.255.0" default_router="66.41.136.1 rl0" This should be: defaultrouter="66.41.136.1" default_router="192.168.1.254 rl1" ^ This is wrong. Don't put that in. domain the-matrix.net nameserver 63.240.76.19 nameserver 204.127.198.19 This goes in your /etc/resolv.conf is there anything else i need to manually connect to my isp? As long as they allow the use of that IP, no. You should be good to go. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
