LinuxQuestions.org - Unable to connect to DHCP Network

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Unable to connect to DHCP Network (https://www.linuxquestions.org/questions/debian-26/unable-to-connect-to-dhcp-network-583492/)

shouldn't that ping be
129.100.196.1
err wait..
129.100.193.1

Are you in a different location now than you were before ? the dhcp server is handing out a completely different Network address to you... you are on a different subnet now than you were before.

I notice the default gateway was missing from your route.. so do you have any experience with wireshark ? personally I'd be grabbing a packet capture of that dhcp exchange to look for anything out of the ordinary.. something is not right..

Hello.

I am also having a problem with UWO RezNet, however I am using Arch Linux (this installation worked fine back home). Interestingly enough, I used to Reznet last year as well, and I didn't have any problems even with defaults setting given by many LiveCDs. This year, neither my Arch Linux nor any liveCDs I tried work..

Looking at RezNet guidebook (following instructions for Mac, to be precise), I also set my account name as DHCP client ID, and set uwo.ca as my hostname, but still it is not working. I did register my network card using my windows Vista though, so maybe that is why. But the it didn't cause problems last year. (and BTW, you have to register your network card at registerme.uwo.ca before using internet, but I imagine you've already done that). I've emailed reznet staff, but so far I am getting no reply. I am afraid that I have to call them sometimes next week, it is frustrating....

Hey guys. I am online again. farslayer: how do I use wireshark? I have it installed but I don't know what output you want to see.

Woodgypsy: e-mail me at lanz_1000@hotmail.com, we can compare our problems and see if we can make the RezNet staff help us out.

Thanks in advance.

Wireshark is a packet capture program. What I would look at is the exchange between your PC and the DHCP server.

You should see the Discover, offer, request, and the acknowledgment. http://gaia.cs.umass.edu/ethereal-la...ereal_DHCP.pdf

Cutting a bit...

Quote:

Originally Posted by WolfCub (Post 2892075)

route -n

Code:

debian:~# route -n

Kernel IP routing table

Destination    Gateway        Genmask        Flags Metric Ref    Use Iface

129.100.193.0  0.0.0.0        255.255.255.0  U    0      0        0 eth1

169.254.0.0    0.0.0.0        255.255.0.0    U    1000  0        0 eth1

debian:~#

ifconfig -a

Code:

debian:~# ifconfig -a

eth1      Link encap:Ethernet  HWaddr 00:1B:FC:B3:0C:6C

          inet addr:129.100.193.162  Bcast:129.100.193.255  Mask:255.255.255.0

          inet6 addr: fe80::21b:fcff:feb3:c6c/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2753 errors:0 dropped:0 overruns:0 frame:0

          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:247925 (242.1 KiB)  TX bytes:23175 (22.6 KiB)

          Interrupt:16



lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:16 errors:0 dropped:0 overruns:0 frame:0

          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:800 (800.0 b)  TX bytes:800 (800.0 b)



debian:~#

ping 127.0.0.1

Code:

debian:~# ping 127.0.0.1

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.

64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.022 ms

64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.016 ms

64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.015 ms



--- 127.0.0.1 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 1999ms

rtt min/avg/max/mdev = 0.015/0.017/0.022/0.005 ms

debian:~#

ping 129.100.0.1

Code:

debian:~# ping 129.100.0.1

connect: Network is unreachable

debian:~#

Thanks in advance.

Because you try to ping to 129.100.0.1, you should leave your local network. Your routetable shows no (correct) gateway, so your ping will never reach another network.