Linux DHCP Client

Hi,
I need to move my linux servers from VLAN A to VLAN B. I have a DHCP
server in both the VLAN's which has a IP-2-MAC mapping already
done.When i move the port from VLAN A to VLAN B,i see the ip address of
VLAN B range assigned to my linux box(i am on the console).However i
cannot remotely login to this box until i do a reboot. Question is
1) Is a reboot necessary?
2) Why does it work for a windows client and not a Linux Client.
Thanks
Z...

In comp.os.linux.networking (E-Mail Removed):
> Hi,
> I need to move my linux servers from VLAN A to VLAN B. I have a DHCP
> server in both the VLAN's which has a IP-2-MAC mapping already
> done.When i move the port from VLAN A to VLAN B,i see the ip address of
> VLAN B range assigned to my linux box(i am on the console).However i
> cannot remotely login to this box until i do a reboot. Question is
> 1) Is a reboot necessary?

No, just pull in an 'at' command that restarts network/dhcpclient
when ever you like.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 286: Telecommunications is downgrading.

What if i only have remote access to the box. I am able to login
remotely to the windows machine when i do the vlan switching but for
linux it takes effect only after reboot?

In comp.os.linux.networking (E-Mail Removed):
> What if i only have remote access to the box. I am able to login
> remotely to the windows machine when i do the vlan switching but for

So you have some kind of remote access board in addition to the
LAN connection or another nic? Else it's not possible to change
the VLAN, while you are logged over exactly this lan. You'll lose
the connection with a single nic anyway independent of the OS.

> linux it takes effect only after reboot?

No it doesn't, if you use the same remote access board, all you
do is 'service network restart', rh and alike, but since you have
no second connection you simply start up an 'at' ('man at')
command so the system executes the above command two/three minutes
after you change VLANs.

BTW
You are replying from google groups in its default way which does
not quote the text you are replying to. This makes it harder for
people not using google groups to help you, while at the same
time annoying regulars on a daily basis. IIRC there is an option
to show text and then you can use the reply button at the bottom.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 376: Budget cuts forced us to sell all the power
cords for the servers.

(E-Mail Removed) wrote:
> What if i only have remote access to the box. I am able to login
> remotely to the windows machine when i do the vlan switching but for
> linux it takes effect only after reboot?
>

login to linux box
su
ifdown ; ifup

that will bounce the network connection and cause it to grab a new ip
address. then you reconnect using the new address.

--
Respectfully,


CL Gilbert

CL (dnoyeB) Gilbert wrote:

> (E-Mail Removed) wrote:
>> What if i only have remote access to the box. I am able to login
>> remotely to the windows machine when i do the vlan switching but for
>> linux it takes effect only after reboot?
>>
>
> login to linux box
> su
> ifdown ; ifup
>
> that will bounce the network connection and cause it to grab a new ip
> address. then you reconnect using the new address.
>

Not necessarily. DHCP servers generally try to reassign the same address,
as previously used, at least for the duration of the lease time.