Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have until now been using a squid with ISDN dial-up as a proxy. Now I'm trying to get it to work with ADSL.
The internal network is on eth1, the DSL on eth0. Then a router and finally the clients.
I have brougt the ADSL up on a standalone PC.
I can get the proxy to connect, but the log says it cannot inbcrease level to 1500 (whatever that means). And using a local browser makes the connection go down immediately, log says sending PADO, waiting for PADI (timeout), disconnecting. I think it may possibly be a routing problem? And now I cannot get the clients to find the proxy. Urgh.....
It's the DHCP client that fails. This is what the sysmes says (I have googled and it seems to be a common problem that somehow appears irrespective of client, no appearent clear solutions):
(nnnn = my client)
Dec 6 13:27:20 nnnn dhcpcd[2581]: broadcasting DHCP_DISCOVER
Dec 6 13:27:20 nnnn dhcpcd[2581]: broadcastAddr option is missing in DHCP server response. Assuming 10.0.0.255
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpIPaddrLeaseTime=7200 in DHCP server response.
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec
Dec 6 13:27:21 nnnn dhcpcd[2581]: DHCP_OFFER received from (10.0.0.138)
Dec 6 13:27:21 nnnn dhcpcd[2581]: broadcasting DHCP_REQUEST for 10.0.0.1
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpIPaddrLeaseTime=7200 in DHCP server response.
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpT1value is missing in DHCP server response. Assuming 3600 sec
Dec 6 13:27:21 nnnn dhcpcd[2581]: dhcpT2value is missing in DHCP server response. Assuming 6300 sec
Dec 6 13:27:21 nnnn dhcpcd[2581]: DHCP_ACK received from (10.0.0.138)
Dec 6 13:27:22 nnnn dhcpcd[2583]: terminating on signal 15
Further, I have found that it is only this PC where the dhcp doesn't work. And it doesn't work on any of the interfaces. Could it be anything in my Squid setup that stops the dhcp client from working properly?
You're definitely right. I tried booting the PC from a KNOPPIX CD. It came up with eth0 as a dhcp client, while eth1 and the on-board eth2 failed. Physical connection is there, and the program find them as candidates for config. But no luck.
No, I can't ping a thing (sorry, couldn't resist :-) )
But the lights indicate a physical connetion on the LAN. And while, say, eth1 may turn up in KDE Info center as up I can't reach it, and it will spontanously go down.
I did notice that eth1 did seem to share IRQ11 with usb-uchi (to which nothing is connected).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.