Fedora core 4 Release IP

[windowsdown]

How do you release the IP # tied to the physical address of users machine from the isp's machines?

I looked at http://forums.fedoraforum.org/regist...480&i=63668397
and none mentioned does such from the service provider and therefore another computer cannot utilize the isp since their machines are tied to the physical address of the linux machine/network card.

I figured out a way around such but it is a hassle so please tell me how to do it from within the operating system Fedora core 4. Thank you.

In windows this is no problem using ipconfig /release

One didn't use to have to do such but with all the internet problems it is now a requirement. What is interesting, some isp support personel have no idea how to release. I was talking to one such not that long ago when something went screwy. All he could do was read from his script manual and tell me to disable the firewall. I asked him how long he worked there expecting to hear 2 days but instead he said 3 years. I hung up, called back and the next guy knew his stuff without having to page thru his work script manual. I asked him how long he worked there and he told me it was his second day. O the power of a real education.

ps. it took overnight for the email to arrive so I could get this posted.

And if you could guide me to a FAQ on how to install such a thing as www.grisoft.com antivirus tho do I really need such on Linux? My windows firewall (ssssss) are constantly faultering. Norton has come up with a new excuse for their failings. Their accusing my siblings of changing my settings. That's a big joke, nobody knows or has access to the passwords but I--well and the internet hackers who walk right around windows sp2 security and every firewall I've used.

For example, from korea with spite or something
NetBus Trojan horse 221.146.164.43

if China has such a great firewall, why are they so frequently in my firewall log with Korea and others?

[viper8]

If you put in a different network card, you should be assigned a new IP. At least that has worked for me in the past. Good luck!

[madscientist]

You can do '/sbin/service network restart', and all of your networking services will be restart. Alternatively, you can do '/sbin/ifdown eth0' (or replace 'eth0' with your networking interface), and then '/sbin/ifup eth0' to bring the connection back up. You can check your IP address with '/sbin/ifconfig' to see if it's changed.

[kmont]

you can use this command to release and renew IP.

log as root
#service network stop
#service network start

[windowsdown]

none of those commands release the physical address from the isp machine so another machine can use the service

Viper8, if that was the case than other machines shouldn't have a problem connecting. This use to be the case before isp's did their mitigations. I have noticed with windows that not always is the command
ipconfig /release
needed. Perhaps it is a flaw within windows or perhaps a flaw on the server/their routers. In some cases I think it is windows vulnerability since a reformat with reinstall of sp2 brings back the requirement to release before can connect other machine.
So swaping the network cards isn't going to do the trick. What does the trick is putting a drive with windows installed into the same machine and it can connect since it is installed on the machine last connected with its network card's physical address still tied to the isp and do the release so other machines can connect. Surely Fedora can accomplish this task although perhaps it wasn't coded for such a requirement. It most certinatly needs to be able to accomplish this task on its own in order to do a full refresh of the ip numbers or else the OS is constantly running a static connection.

What would be nice is an emulator to alter the physical address of windows computers and others. What's the point of having a dynamic connection if the machines constantly use the same physical address. If they always know the physical address, makes hacking a breeze and I think this is why we constantly see windows machines hacked up as they play and refine the attack based on response of the user and microsofts/Cisco/Linksys, etc patches/fixes.

Cisco claims the VP6N vuln has been resolved back in April. I find this laughable as same I find that they should have FULLY patched this problem years ago. Linksys routers use VP4N, and are quite vulnerable as I'm sure all home firewall routers are based on problems with routers that I see users post about which I already have seen in the past and worked with Linksys to resolve/develop version 2 of paticular router. However, they are dragging their feet about developing version 3 which I first informed them about in the last quarter of last year.

Wonder why none of the updates to Fedora core4 have, don't know the right word, correct GPG signatures.
When I run one command to show what in windows 'ipconfig' shows, it comes back with the data and within it is 'TX packets errors 4'. Why?

Thank you for the assistance.