Re: modifying permissions in /dev
Perhaps this thread should be moved to -questions: it seems to be irrelevant for the -net discuissions. Thu, Feb 07, 2008 at 07:53:32PM +, lysergius2001 wrote: > Apologies for the top post? Looks like I need a lesson in etiquette as well > as devfs. ;)) http://www.caliburn.nl/topposting.html might be helpful. > The problem is this. I have two boxes running 6.3-stable. One is i386 and > the other is amd64. Identical setups as near as I can make it. the 386 box > allows mounting floppy from kde, but does not find cd0 in k3b. The amd64 > box finds cd0 in k3b but will not allow mounting floppy in kde? > > I have vfs.usermount= 1 in sysctl.conf on both boxes. > > I have identical devfs.conf and devfs.rules. hald is running on both > boxes. rc.conf is identical on both boxes. I am baffled, stumped and > getting confused... > > Can I go back to the basics somehow and work through the set up logically? Yes, just start with low-level stuff. 1. Verify that you have the devices: ls -l /dev/cd0 /dev/fd0. 2. Check the permissions for devices in an above output. 3. Check vfs.usermount once again: sysctl vfs.usermount. 4. Try to mount device as root via 'mount' utility. 5. Unmount it and try mounting as user via 'mount'. If all the above works, then the problem might be in GUI tools you're using. Maybe they can not locate the devices. Maybe something else. But if the above is not working, then probably GUI tools will not work either. For the k3b: seems like it is just frontend for the cdrecord/cdrdao. If so, then you probably should have /dev/xptX and /dev/passX and permissions must allow to read and write to them. This is surely true for cdrecord, don't know for cdrdao -- not using it. And vfs.usermount should not be relevant for CD recording, if I am not mistaken. -- Eygene ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: modifying permissions in /dev
Fri, Feb 08, 2008 at 11:37:17AM +0300, Eygene Ryabinkin wrote: > For the k3b: seems like it is just frontend for the cdrecord/cdrdao. > If so, then you probably should have /dev/xptX and /dev/passX and Hmm, to clarify: 'ls -l /dev/xpt* /dev/pass*' should show you something. 'cdrecord -scanbus' and 'cdrdao scanbus' should show you the list of devices. -- Eygene ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ospf cost and route selection (openospfd)
Josef, good day. Fri, Feb 08, 2008 at 11:53:57AM +0100, Josef Pojsl wrote: > I did try the patch. Unfortunately, the deamon complains about sending packets > over gre interfaces. I cannot see any OSPF traffic on them with tcpdump, > and no routes get added. Look at what ospfd -dv says: > > startup > if_del: interface gre31 > if_del: interface gre30 > orig_asext_lsa: 10.10.0.0/16 age 0 > orig_asext_lsa: 10.20.0.0/16 age 0 > orig_asext_lsa: 192.168.2.0/24 age 0 > orig_rtr_lsa: area 0.0.0.0 > orig_rtr_lsa: stub net, interface gre31 > if_fsm: event UP resulted in action START and changing state for interface > gre31 from DOWN to P2P > orig_rtr_lsa: area 0.0.0.0 > orig_rtr_lsa: stub net, interface gre31 > orig_rtr_lsa: stub net, interface gre30 > if_fsm: event UP resulted in action START and changing state for interface > gre30 from DOWN to P2P > send_packet: error sending packet on interface gre31: Invalid argument > send_packet: error sending packet on interface gre30: Invalid argument > spf_calc: area 0.0.0.0 calculated OK, I will try to look at the problem. Not today, probably the middle of the next week. Thanks for the testing! -- Eygene ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ospf cost and route selection (openospfd)
Hi Eygene, On Thu, Feb 07, 2008 at 07:57:47PM +0300, Eygene Ryabinkin wrote: > OK, the first patch version is ready. It compiles well and even > starts for the trivial configuration. I will try to test it for > other configurations, but you may test it as well: I will appreciate > it very much. > > One note: the provided patch if applied with the normal 'patch' > utility can fail to remove deleted patches from the 'files' directory. > The following files should not be present: > > files/patch-ospfctl_parser.c > files/patch-ospfctl_parser.h I did try the patch. Unfortunately, the deamon complains about sending packets over gre interfaces. I cannot see any OSPF traffic on them with tcpdump, and no routes get added. Look at what ospfd -dv says: startup if_del: interface gre31 if_del: interface gre30 orig_asext_lsa: 10.10.0.0/16 age 0 orig_asext_lsa: 10.20.0.0/16 age 0 orig_asext_lsa: 192.168.2.0/24 age 0 orig_rtr_lsa: area 0.0.0.0 orig_rtr_lsa: stub net, interface gre31 if_fsm: event UP resulted in action START and changing state for interface gre31 from DOWN to P2P orig_rtr_lsa: area 0.0.0.0 orig_rtr_lsa: stub net, interface gre31 orig_rtr_lsa: stub net, interface gre30 if_fsm: event UP resulted in action START and changing state for interface gre30 from DOWN to P2P send_packet: error sending packet on interface gre31: Invalid argument send_packet: error sending packet on interface gre30: Invalid argument spf_calc: area 0.0.0.0 calculated Thanks, -- Josef ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: modifying permissions in /dev
Hi, I have had some success. On the AMD 64 box I relaised that the /floppy directory I was trying to mount the floppy to was owned by root. I have fixed that and it is fine. I will work on the K3B issue and report back. Many thanks for the support! On 2/8/08, Eygene Ryabinkin <[EMAIL PROTECTED]> wrote: > > Fri, Feb 08, 2008 at 11:37:17AM +0300, Eygene Ryabinkin wrote: > > For the k3b: seems like it is just frontend for the cdrecord/cdrdao. > > If so, then you probably should have /dev/xptX and /dev/passX and > > Hmm, to clarify: 'ls -l /dev/xpt* /dev/pass*' should show you > something. 'cdrecord -scanbus' and 'cdrdao scanbus' should show > you the list of devices. > -- > Eygene > -- Lysergius says "Stay light and trust gravity" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Newb question
All, My company is getting a fractional DS3 in the near future, and I've acquired a Sangoma a301 card to handle the interface. We're retaining one of the T1s we currently have, from a different provider, and we're intent on using BGP to manage the two connections. Does anyone have good pointers to tutorials or howtos on setting up OpenBGP for a newb like me who has never done this before? I've got the ARIN web site open now, looking through the docs on getting our ASN, but it's all new to me, and I could use a little help. Thanks, Kurt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Stateless IPv6 address translation NAT-PT?
Hi All,
I have a very specific networking setup needs that I hope someone can
help me or give some suggestions.
To put it in the most simplest terms, I need to allow several scattered
private networks to talk to each other.
The network setup is like this: the border routers (machines) are running
FreeBSD 6.2
NetworkA IP is 192.168.1.x
NetworkB IP is 192.168.2.x
NetworkC IP is 192.168.3.x
How can I easily make the hosts in the 3 networks communicate? Two
solutions come to my mind already, but they aren't optimal.
A) set up a vpn that connects all three networks. The problem then is that
I need to setup a VPN server somewhere and thus creates a star topology.
This introduces a dependency, the VPN server, which is not really needed
(security on the network level is not a requirement)
B) set up tunnelling at the border FreeBSD machines. But then I need to
setup tunnels for each connecting networks, A<->B, B<->C, and C<->A. This
get complicated quickly as there are a few more networks I need to connect.
More importantly, some machines in the networks require IPv6 connectivity.
Network{A,B,C} each has an IPv6 /64 address already so those machines with
IPv6 can communicate already.
So now I am only concerned with the IPv4 only machines on the networks.
My idea is to piggy back the address space of the v6 /64 address space to
allow the v4 machines talk to each other, with the added benefit of
communicating with the v6 machines.
This seems to be solved easily by SIIT and stateless basic NAT-PT
(1:1 mapping), correct? Yes I know NAT-PT has been deprecated but this
seems to be the most straightforward solution.
For example, a host in netA 192.168.1.2 needs to talk to a host in netB
192.168.2.2 and assuming netA has an IPv6 block of beef:cafe:0001::/64 and
netB has beef:cafe:0002::/64
The tuple from 192.168.1.2 is { 192.168.1.2: 192.168.2.2: },
translated by the FreeBSD router at Network A to:
{ [beef:cafe:0001::c0a8:0102]: [beef:cafe:0002::c0a8:0202]: }
The translation can (and should) be stateless and done statically. The
connection then becomes a routable v6 connection between the networks.
When the IPv6 connection reaches border router at Network B it down
translates back to the correct IPv4 tuple. Within the network I use
a /96 prefix to differentiate whether a v6 address needs translation,
i.e. a v4 only host and v6 host will have different /96 prefixs.
In this setup, I will need to install the v4/v6 prefix mapping table on
each border routers so they can translate and route properly. Conceptually
this is no different than setting up tunnels for each and every connected
networks at the border routers but it seems it's more easy to manage and
more capable as it allows v4 and v6 communication.
The mapping will be like:
192.168.1.0/24 <=> beef:cafe:0001::c0a8:0100/120
192.168.2.0/24 <=> beef:cafe:0002::c0a8:0200/120
192.168.3.0/24 <=> beef:cafe:0003::c0a8:0300/120
I googl'ed to death and still can't find a way to set this up. I can't find
a NAT-PT implementation on FreeBSD that does 1:1 static mappings.
Is there any idea how this can be done, or if there is a better solution?
Thanks,
Leo
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
