Clan x86

Technical (Development, Security, etc.) => Unix / Linux Discussion => Topic started by: rabbit on April 15, 2006, 06:46:03 PM

Title: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 15, 2006, 06:46:03 PM
root@Paradise#
spencer@Paradise$

Yet..
(http://www.liquid-server.org/images/networkname.png)
Where is it?
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Joe on April 15, 2006, 06:52:46 PM
Get samba.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 15, 2006, 08:03:46 PM
I'm asking for help, not useless comments.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 15, 2006, 08:37:17 PM
Quote from: rabbit on April 15, 2006, 08:03:46 PM
I'm asking for help, not useless comments.

Installing Samba actually might help ...
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 15, 2006, 08:44:36 PM
"Get samba" provides one piece of information: something is called 'samba'.  There is no description of what it is, where to get it, or what to do with it.  That was a useless post.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 15, 2006, 08:56:17 PM
Quote from: rabbit on April 15, 2006, 08:44:36 PM
"Get samba" provides one piece of information: something is called 'samba'.  There is no description of what it is, where to get it, or what to do with it.  That was a useless post.

It seems you're forcing me to state the obvious.  Useless implies that something has absolutely no use in said subject.  Joe's post suggested that you get Samba.  Given that you could type "Samba" into google and quickly learn its use, I don't think his post was useless at all.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: iago on April 16, 2006, 11:59:18 AM
Get Samba. 

Your router, I'm guessing, pulls the NetBIOS hostname.  NetBIOS is a Windows thing,which can be emulated by Samba.  If you'd installed Samba in the first place, like Joe said, your problem would be solved. 

Google is your friend :P
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 16, 2006, 12:09:21 PM
I have Samba.  But what now?  There is no "samba" program.  There is xfsamba4, but that's for xfce.  The info on Samba I can find is entirely about what it is, a run-down of the protocols, history of its existence, etc.., but not a "How to use it" guide.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 16, 2006, 12:19:40 PM
Quote from: rabbit on April 16, 2006, 12:09:21 PM
I have Samba.  But what now?  There is no "samba" program.  There is xfsamba4, but that's for xfce.  The info on Samba I can find is entirely about what it is, a run-down of the protocols, history of its existence, etc.., but not a "How to use it" guide.

http://www.google.com/search?client=opera&rls=en&q=samba&sourceid=opera&ie=utf-8&oe=utf-8

QuoteSamba -- Opening Windows to a Wider World
The official SAMBA site. Provides links to mirrors.
www.samba.org/ - 6k - Cached - Similar pages

http://us5.samba.org/samba/

QuoteSamba is an Open Source/Free Software suite that has, since 1992, provided file and print services to all manner of SMB/CIFS clients, including the numerous versions of Microsoft Windows operating systems. Samba is freely available under the GNU General Public License.

http://us5.samba.org/samba/ftp/samba-latest.tar.gz
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: iago on April 16, 2006, 12:47:01 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.
I was wondering the same thing.  The last time somebody wanted to know, I just said not to bother :)

There's probably a startup program to run Samba.  /etc/rc.d/rc.samba perhaps?  I don't use Samba myself, I try to avoid Windows hardware.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: iago on April 16, 2006, 01:04:31 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!

Your MAC address never gets past a router.  It changes on every pair of routers that a packet travels through.  The people at the end never know what the original MAC was. 

Just thought I'd point out your little flaw.. :P
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 16, 2006, 01:35:58 PM
Quote from: iago on April 16, 2006, 01:04:31 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!

Your MAC address never gets past a router.  It changes on every pair of routers that a packet travels through.  The people at the end never know what the original MAC was. 

Just thought I'd point out your little flaw.. :P

You could spoof the MAC on your router? That's kinda what I meant. =P

I actually just learned that while reading up on NAT in pf in Arizona. :)
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 16, 2006, 01:49:11 PM
Quote from: Newby on April 16, 2006, 01:35:58 PM
Quote from: iago on April 16, 2006, 01:04:31 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!

Your MAC address never gets past a router.  It changes on every pair of routers that a packet travels through.  The people at the end never know what the original MAC was. 

Just thought I'd point out your little flaw.. :P

You could spoof the MAC on your router?

Then the next router that receives the Ethernet frame will replace your spoofed MAC address with its own.  WAN's don't generally even transmit data over Ethernet; it's most commonly done over ATM which uses a different form of physical addressing.  The information within an Ethernet frame (source and destination MACs, for example) are only of any use on the local network segment.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 16, 2006, 01:53:35 PM
Aww, lame. :(
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 16, 2006, 04:43:07 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!
Newby 1, Everyone else 0
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 16, 2006, 04:47:21 PM
Quote from: rabbit on April 16, 2006, 04:43:07 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!
Newby 1, Everyone else 0

Read the rest of the posts after that.  You'll see it'd be useless to spoof his MAC address as one of ours. ;)
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 16, 2006, 05:40:28 PM
I was stating scores in regard to OCD.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 16, 2006, 08:14:20 PM
Quote from: Sidoh on April 16, 2006, 04:47:21 PM
Quote from: rabbit on April 16, 2006, 04:43:07 PM
Quote from: Newby on April 16, 2006, 12:54:35 PM
I could see why. OCD.

Haha, now I have your MAC addressses. Time to spoof my MAC as yours and syn flood www.fbi.gov!
Newby 1, Everyone else 0

Read the rest of the posts after that.  You'll see it'd be useless to spoof his MAC address as one of ours. ;)

He means I got it right that he's OCD about it.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 16, 2006, 08:44:22 PM
Quote from: Newby on April 16, 2006, 08:14:20 PM
He means I got it right that he's OCD about it.

Corrupted, slanderous lies.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: deadly7 on April 16, 2006, 10:14:14 PM
Quote from: rabbit on April 16, 2006, 05:40:28 PM
I was stating scores in regard to OCD.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 16, 2006, 10:23:40 PM
Quote from: deadly7 on April 16, 2006, 10:14:14 PM
I was stating scores in regard to OCD.

Quote from: Sidoh on April 16, 2006, 08:44:22 PM
Corrupted, slanderous lies.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 17, 2006, 04:48:40 PM
Sidoh, you're just plain wrong...
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 17, 2006, 05:39:33 PM
Quote from: rabbit on April 17, 2006, 04:48:40 PM
Sidoh, you're just plain wrong...

QuoteDefinitions of humor on the Web:
wit: a message whose ingenuity or verbal skill or incongruity has the power to evoke laughter
the trait of appreciating (and being able to express) the humorous; "she didn't appreciate my humor"; "you can't survive in the army without a sense of humor"
temper: a characteristic (habitual or relatively temporary) state of feeling; "whether he praised or cursed me depended on his temper at the time"; "he was in a bad humor"
the quality of being funny; "I fail to see the humor in it"
(Middle Ages) one of the four fluids in the body whose balance was believed to determine your emotional and physical state; "the humors are blood and phlegm and yellow and black bile"
liquid body substance: the liquid parts of the body
put into a good mood
wordnet.princeton.edu/perl/webwn
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Joe on April 17, 2006, 09:15:25 PM
Quote from: Lord[nK] on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?

Are you saying I'm too stupid to have tried that? Please...
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 17, 2006, 10:59:42 PM
Samba works, partly.  Here's what's up:
Lili - sister's computer, can access just fine
Paradise - can't access from Samba (even though I'm on it); still doesn't show up as named in base station manager
Attic - could access it with old Samba, can't after update
Laptop - can't access at all from Samba
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 18, 2006, 09:18:47 AM
Quote from: Joe on April 17, 2006, 09:15:25 PM
Quote from: Lord[nK] on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?

Are you saying I'm too stupid to have tried that?

No.  Too "stupid" to have done it successfully, perhaps.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 18, 2006, 09:27:09 AM
Quote from: rabbit on April 17, 2006, 10:59:42 PM
Paradise - still doesn't show up as named in base station manager

smb.conf:

netbios name = <name>
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Joe on April 18, 2006, 05:23:51 PM
Quote from: Lord[nK] on April 18, 2006, 09:18:47 AM
Quote from: Joe on April 17, 2006, 09:15:25 PM
Quote from: Lord[nK] on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?

Are you saying I'm too stupid to have tried that?

No.  Too "stupid" to have done it successfully, perhaps.

When you finally get done messing with VB and realize Linux is better, write a guide on how to do this please. Otherwise, don't act like you're better than me just because your an adult.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 18, 2006, 05:58:39 PM
Quote from: Joe on April 18, 2006, 05:23:51 PM
When you finally get done messing with VB and realize Linux is better, write a guide on how to do this please. Otherwise, don't act like you're better than me just because your an adult.

You realize I'd wager that Lord knows more about BSD/Linux than you do? =P
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Warrior on April 18, 2006, 07:48:34 PM
Quote from: Joe on April 18, 2006, 05:23:51 PM
Quote from: Lord[nK] on April 18, 2006, 09:18:47 AM
Quote from: Joe on April 17, 2006, 09:15:25 PM
Quote from: Lord[nK] on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?

Are you saying I'm too stupid to have tried that?

No.  Too "stupid" to have done it successfully, perhaps.

When you finally get done messing with VB and realize Linux is better, write a guide on how to do this please. Otherwise, don't act like you're better than me just because your an adult.

LMAO!!!!!!
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 18, 2006, 07:59:46 PM
Quote from: Joe on April 18, 2006, 05:23:51 PM
Quote from: Lord[nK] on April 18, 2006, 09:18:47 AM
Quote from: Joe on April 17, 2006, 09:15:25 PM
Quote from: Lord[nK] on April 17, 2006, 05:28:52 PM
Quote from: Joe on April 16, 2006, 06:50:08 PM
Quote from: Lord[nK] on April 16, 2006, 12:44:02 PM
I'm curious as to why you're willing to go to such lengths just to have your host name show up on a Windows-based router.

In my case, I have a dynamic internal IP address. Having "deadmeat" be accessable to my Windows box which is in the DMZ (I'm well aware of the security risks, but I don't have anything else to put there) and responsible for port forwarding (for httpd, mainly) is much, much easier than running upstairs and setting up the port forward information to send it to a new IP address.

Give yourself a static IP address?

Are you saying I'm too stupid to have tried that?

No.  Too "stupid" to have done it successfully, perhaps.

When you finally get done messing with VB and realize Linux is better

I wasn't aware that Linux was a programming language.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 18, 2006, 08:05:51 PM
Quote from: Lord[nK] on April 18, 2006, 07:59:46 PM
I wasn't aware that Linux was a programming language.

The fuck is wrong with you? I code Linux and BSD all day.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: iago on April 18, 2006, 08:17:32 PM
Quote from: Lord[nK] on April 18, 2006, 07:59:46 PM
Quote from: Joe on April 18, 2006, 05:23:51 PM
When you finally get done messing with VB and realize Linux is better

I wasn't aware that Linux was a programming language.

VB is a programming language and Linux is a platform that doesn't support it.  There isn't a problem there. 
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 18, 2006, 08:32:23 PM
Quote from: iago on April 18, 2006, 08:17:32 PM
Quote from: Lord[nK] on April 18, 2006, 07:59:46 PM
Quote from: Joe on April 18, 2006, 05:23:51 PM
When you finally get done messing with VB and realize Linux is better

I wasn't aware that Linux was a programming language.

VB is a programming language and Linux is a platform that doesn't support it.  There isn't a problem there. 

Perhaps not if he would have worded it that way, but he didn't.  You did.

Anyways, my current Linux skill level aside, setting your computer up to use a static IP address is no difficult task, definately not a task requiring a tutorial to be made.  IIRC, it's done through /etc/sysconfig/network/, but I may be mistaken.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Joe on April 18, 2006, 08:42:49 PM
But I'd say you're noone to judge which operating system I should be using.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: rabbit on April 18, 2006, 09:08:26 PM
I say everyone stfu and gtfo if you're not going to help.  This discussion does not belong in a REQUEST FOR HELP THREAD.

Thank you.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Sidoh on April 19, 2006, 12:01:28 AM
Please... LoRD transcended the mind of a simple Visual Basic programmer at the moment of conception.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 19, 2006, 12:12:02 AM
Quote from: Lord[nK] on April 18, 2006, 08:32:23 PM
Anyways, my current Linux skill level aside, setting your computer up to use a static IP address is no difficult task, definately not a task requiring a tutorial to be made.  IIRC, it's done through /etc/sysconfig/network/, but I may be mistaken.

The hell kind of distro are you using? Either Slackware isn't standard or that's not standard.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Eric on April 19, 2006, 12:24:57 AM
Quote from: Newby on April 19, 2006, 12:12:02 AM
Quote from: Lord[nK] on April 18, 2006, 08:32:23 PM
Anyways, my current Linux skill level aside, setting your computer up to use a static IP address is no difficult task, definately not a task requiring a tutorial to be made.  IIRC, it's done through /etc/sysconfig/network/, but I may be mistaken.

The hell kind of distro are you using? Either Slackware isn't standard or that's not standard.

Red Hat.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: Newby on April 19, 2006, 12:35:35 AM
Figured so. Weird.
Title: Re: Network Name...dun dun dun...DOESN'T EXIST!
Post by: iago on April 19, 2006, 08:18:32 AM
Quote from: Lord[nK] on April 18, 2006, 08:32:23 PM
Perhaps not if he would have worded it that way, but he didn't.  You did.

Anyways, my current Linux skill level aside, setting your computer up to use a static IP address is no difficult task, definately not a task requiring a tutorial to be made.  IIRC, it's done through /etc/sysconfig/network/, but I may be mistaken.

It's different on every distro.  Slackware's resides in /etc/rc.d/rc.inet1.conf. 

The only reasonably constant way across most Linuxes/Unixes is
ifconfig <address> netmask <netmask> broadcast <broadcast>